What's New in UCC Site Creator v8.4.1.8

This article describes the changes introduced in UCC A Unified Contact Center, or UCC, is a queue of interactions (voice, email, IM, etc.) that are handled by Agents. Each UCC has its own settings, IVR menus and Agents. Agents can belong to one or several UCCs and can have multiple skills (competencies). A UCC can be visualized as a contact center “micro service”. Customers can utilize one UCC (e.g. a global helpdesk), a few UCC’s (e.g. for each department or regional office) or hundreds of UCC’s (e.g. for each bed at a hospital). They are interconnected and can all be managed from one central location. Site Creator v8.4.1.8 compared to v8.4.0.1.

Both versions are MC1117115 Linking the Microsoft 365 Message Center Archive on Merrill.net (maintained by a Principal Product Manager at Microsoft) for easier public reference of the Microsoft announcement. The official Message Center is accessible only to Microsoft 365 administrator accounts. compliant. The changes in v8.4.1.8 focus on subsite deployment reliability, site collection App Catalog support, and reduced-permission deployment scenarios.

UCC Dashboard SPFx Package (ucc-dashboard-spfx.sppkg)

v8.4.1.8 includes an updated SPFx package.

In v8.4.0.1, lists and libraries displayed within the UCC Dashboard were limited to the first 100 items, regardless of actual list size. Items beyond that threshold were not visible in the dashboard views.

v8.4.1.8 raises this limit to 5,000 items — the maximum supported by SharePoint list views. Sites with larger Agents, Skills, Endpoints, or other lists will now display all items correctly without truncation.

Subsite Provisioning

Subsite provisioning was not available in v8.4.0.1. v8.4.1.8 introduces full subsite provisioning support via the -UseSubSites parameter in UCC.Site.Creator.ps1. The script processes pending requests from the A365_UCC_Creator list and creates each UCC subsite at its correct location within the site collection hierarchy (e.g. /sites/ucc/emea/sub-7-emea-a), including full list provisioning and dashboard page setup.

New subsites are created using the STS#0 (Team Site) template. The BLANKINTERNET#0 template used by earlier versions of the UCC Site Creator is no longer supported — Microsoft states that new sites using classic publishing templates, including BLANKINTERNET#0, cannot be created after March 15th 2026 as outlined in MC1117115.

Alternatively, subsite mode can be enabled persistently via configuration.xml by setting the <UseSubSites> element to true, removing the need to pass the parameter on every run:

...
<UseSubSites>true</UseSubSites>
...

Site Collection App Catalog Support

v8.4.0.1 supported only the tenant-wide App Catalog for deploying the UCC Dashboard SPFx package. This requires Sites.FullControl.All permissions and tenant administrator access.

v8.4.1.8 adds full support for site collection App Catalogs as an alternative deployment target. This enables deployments in environments where tenant-wide permissions cannot be granted.

Deploy-UccDashboard.ps1

The new -SiteCollectionAppCatalogUrl parameter targets a specific site collection catalog instead of the tenant catalog. When used, the script also automatically installs the app on all already-provisioned UCC subsites found in the A365_UCC_Creator list.

UCC.Site.Creator.ps1

The new -UseSiteCollectionAppCatalog parameter installs the UCC Dashboard app from the site collection catalog on each newly provisioned subsite immediately after creation, before the dashboard page is configured. This eliminates the SPFx component propagation delay that previously caused dashboard pages to render blank on first load.

Modernize-UccSite.ps1 / Batch-ModernizeUccSites.ps1

The new -UseSiteCollectionAppCatalog parameter ensures the app is installed (or updated) on each site as part of the modernization run, rather than relying on a prior tenant-wide deployment.

Sites.Selected Permission Model

v8.4.1.8 introduces support for deployments using an Entra ID Formerly known as Azure Active Directory (or Azure AD, or AAD) application with Sites.Selected permissions only, without requiring Sites.FullControl.All.

The new -SiteCollectionPreCreated switch in UCC.Site.Creator.ps1 tells the script that the root site collection has been pre-created by a SharePoint Administrator, bypassing the site creation step that requires tenant admin permissions. Without this switch, the script attempts to create the site collection, which will fail under Sites.Selected.

See UCC Site Collection Deployment — Sites.Selected Permission Model for the full setup procedure for this model.

Dashboard Page Reliability

Full-Width Layout on BLANKINTERNET Sites

Sites created from the classic BLANKINTERNET template lock the Home.aspx page as the current welcome page, preventing it from being deleted and recreated with a clean full-width layout. v8.4.0.1 did not handle this case and could leave the dashboard page in an incorrect layout.

v8.4.1.8 detects this condition and falls back to clearing and updating the existing page in place rather than attempting to delete and recreate it. The UCC Dashboard web part is added successfully in all cases. However on BLANKINTERNET sites still maximum One Column Width.

Component Availability at Page Creation Time

In v8.4.0.1, dashboard pages were created immediately after subsite provisioning, before the SPFx component had propagated to the subsite. This caused the web part to sometimes fail to resolve, resulting in a blank dashboard and a 120-second timeout wait.

In v8.4.1.8, if the app is installed directly on the subsite via the site collection catalog before the dashboard page is created. The component is available immediately, eliminating the propagation wait entirely. But also on tenant-side dashboard app deployment the wait is minimal

AnywhereNow Branding

v8.4.1.8 sets the AnywhereNow logo as the site logo on all provisioned and modernized UCC sites and parent sites. This applies to both new provisioning via UCC.Site.Creator.ps1 and modernization via Modernize-UccSite.ps1.

Intermediate Site Handling

In subsite deployments, sites that sit between the root and the UCC subsites (e.g. regional grouping sites like /emea, /apac, /amer) do not contain UCC lists and are skipped during modernization. v8.4.1.8 ensures that navigation is still hidden on these intermediate sites, preventing inherited navigation from appearing on child UCC sites.

Summary of New Parameters