SharePoint Template FAQ

A: Go to the settings page of the 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. (e.g. http://sitecollection.com/anywhere/ucc_name/Lists/Settings/AllItems.aspx) and replace "Settings" for "Version".

The Url will become: http://sitecollection.com/anywhere/ucc_name/Lists/Version/AllItems.aspx and it will now show the SharePoint Template version.
Or navigate to the Anwhere365 UCC template menu Version Management in the UCC General table.

A: Run a SharePoint Online managed shell command to enable authentication of the new tenant

1. Check if your SharePoint Online managed shell is updated to the latest version

2. Run the PowerShell command for the affected tenant:

Set-SPOTenant -DisableCustomAppAuthentication $false

A: Run a SharePoint Online managed shell command to enable custom scripts on the site

1. Check if your SharePoint Online managed shell is updated to the latest version

2. Run the PowerShell command for the affected site (may take several minutes to get fully processed in Microsoft 365):

Set-SPOSite <SiteURL> -DenyAddAndCustomizePages $False

or use the following easy to use Powershell script:

#Config Parameters
$AdminSiteURL="https://<your-tenant>-admin.sharepoint.com"
$SiteURL="https://<your-tenant>.sharepoint.com/sites/<uccsite>" 
  
#Connect to SharePoint Online Tenant Admin portal
Connect-SPOService -URL $AdminSiteURL
   
#sharepoint online enable custom scripts powershell - Disable DenyAddAndCustomizePages Flag
Set-SPOSite $SiteURL -DenyAddAndCustomizePages $False

ALTERNATIVELY Using PnP.PowerShell the command would be:

Set-PnPSite -Identity https://<tenant-name>.sharepoint.com/sites/<ucc-name> -NoScriptSite $false

More PnP.PowerShell prerequisites involved in creating and editing UCC sites can be found on Learn More

A: To solve this

1. Deactivate SharePoint Server Publishing feature on the root site of your site collection

2. Deactivate SharePoint Server Publishing Infrastructure feature on sitecollection level

3. Activate SharePoint Server Publishing Infrastructure feature on sitecollectie level

https://support.office.com/en-us/article/enable-publishing-features-479677a6-8b33-4ac7-907d-071c1c7e4518

A: There is a specific permission on a list that can cause this error. There is a hidden list titled "TaxonomyHiddenList" at the root of the site collection. (http://sitecollectionURL/List/TaxonomyHiddenList). The ClientID & ClientSecret should have permissions on this list in order to run our UCC.Creator script.

https://support.office.com/en-us/article/enable-publishing-features-479677a6-8b33-4ac7-907d-071c1c7e4518

A: New Microsoft security enhancements (September 2023) cause site collection admin is not able to register add-in with Azure ACS in AppRegNew.aspx by default, or update app permissions on the AppInv.aspx page unless explicitly allowed by the SharePoint tenant admin. For more information, see Set-SPOTenant.
This can be overcome by running the following SPO-ManagementShell command:

Set-SPOTenant -SiteOwnerManageLegacyServicePrincipalEnabled $true

For more information, Learn More - Microsoft

A: Even though Microsoft advises customers to abandon the usage of subsites, for the short term this is not a feasible way to go, mainly due to the lack of a smooth migration.

For new customers we recommend you to deploy a single UCC site per Site Collection. This is possible using the latest UCC Creator that is available as part of bundle 2022.06 or later. Furthermore, it is advised to start using the latest SharePoint connectivity model (Microsoft Entra ID Formerly known as Azure Active Directory (or Azure AD, or AAD) App-only certificate based authentication), to prevent the need to create a Client ID and Client Secret per UCC site and renew this on a yearly basis. For more details, Learn More.

For existing customers, it is possible to continue working with subsites until the migration path is clear and automated as much as possible.

A: Our current understanding is that a subsite is also considered a separate site, so it's still possible to create a maximum of 2000 UCC subsites (per Site Collection) each of which can contain a maximum of 2000 lists and libraries. A default UCC site has 48 lists, some functionalities require one or more additional lists or libraries, and we may want to reserve some room for future use, but Anywhere365 Ucc.Creator will not supercede the limit of 2000 lists and libraries. Please note that the limitation is not on the amount of items in a list or library. For more information please see Microsoft Message Center (Administrators only): Microsoft Online AdminPortal: Message center MC405984
Microsoft's latest known text from Message Center reads (but is subject to change by Microsoft):
Message Summary

Updated October 11, 2022: We are providing updates to provide you with additional information. Thank you for your patience.

We would like to provide clarification on the enforcement of maximum count of lists and libraries per site. As described in the SharePoint limits - Service Descriptions, the service limit is 2,000 lists and libraries combined per site collection (including the main site and any subsites). Beginning February 2023, we will enforce the limit of 2,000 lists and libraries independently at the main (root) site and the subsite level. For instance, a site collection can have 2,000 subsites (including the main site) and each subsite (including the main site) could have 2,000 lists and libraries (including the hidden and default out of the box libraries).

These limits may get further re-aligned based on the service description in the future, but the timeline is TBD. In the meantime, we still recommend customers to follow the limits defined in the service description to achieve the best performance and service reliability.

SharePoint recommends a maximum of 2,000 lists and libraries per site, and 2,000 subsites per site. These have been long standing limits for SharePoint but have not been formally enforced.

There have been cases where some sites exceeded these limits, resulting in poor site performance and low-quality viewing experience. One of the most impacted areas is the API performance that degrades significantly when users access data on the sites that exceed their recommended limits. The API calls may time out or get throttled, blocking the users from opening the site or resulting in unexpected failures. In some extreme cases, the issue can impact functionalities beyond these sites.

To ensure site performance and help customers have the best possible experience, Microsoft will implement a safeguard to prevent customers from exceeding these limits.

When will this happen:

The change will only impact the creation of new lists, libraries or subsites outside the approved limits starting in February 2023 (previously early November) and will be completely enforced by late April (previously late December).

How this will affect your organization:

Once these limits are enforced, sites that exceed the limit of 2,000 lists and libraries will no longer be able to have new libraries or lists added to the site. Similarly, any site that exceeds the limit of 2,000 subsites will no longer be able to have new subsites added to the site.

When a site reaches these limits, users will see the following message on SharePoint web:

View image in new tab

On the API request to create a new list or document library, SharePoint will return the error code, ERROR_SHARING_BUFFER_EXCEEDED on the API request.

Libraries, lists, and subsites that have been created before the enforcement rollout and exceed the corresponding limit, will continue to function and their access will not be blocked. The change will only impact the creation of new lists, libraries or subsites outside the approved limits starting in November. These new additions will get blocked at the time of creation once the site reaches the corresponding limit.

What you need to do to prepare:

Share these limits with people who manage SharePoint sites in your organization. If the sites in your tenant are below the limits, this change will not impact you.

It is uncommon for the organic growth of site to reach these limits. However, there is a possibility that custom solutions can generate a high volume of lists and libraries. In that situation, our recommendation is to work with their solution providers to prepare an alternative solution in order to stay compliant with these limits.

A: There is no definition of “best”. Microsoft's recommendation is for now only that, a recommendation which is not being actively enforced. The Anywhere365 Ucc.Creator (as of Bundle DC2022.06) is ready for use with both the subsites allowed model (Legacy model) and the subsites disabled model (OneUCC Available since UCC.Creator v8.2.0.7. The model (preferred by Microsoft) in SharePoint on Microsoft 365 where no subsites are allowed. In this model each Anywhere365 UCC will need its own separate SharePoint site (formerly known as site collection). This does allows for more granular user access and template updates per UCC. model). So for now subsites can still be used by Ucc.Creator (albeit with the use of an extra parameter, -UseSubsites, in the PowerShell scripts). But it is equally possible to use Ucc.Creator to create a single Site Collection per UCC, if your organization wants or needs to adhere to the Microsoft recommendation. PLEASE NOTE: This is not an Anywhere365 “verdict” but a consequence of Microsoft’s decisions on usage of SharePoint. Anywhere365 is always committed to finding a suitable solution and enhancements so we may be migrating to a more fitting solution in the future.

A: Each UCC creates its own connection to SharePoint, and can be configured with its own connection details. So it is possible to connect individual UCCs from a single dialogue cloud server to different SharePoint sites, using different authentication methods. There is no relation between a dialogue cloud server and a SharePoint site collection.

A: Start using SharePoint certificate based authentication as an alternative for Client ID and Client Secret authentication. For more details, Learn More.