Troubleshoot your deployment



This topic describes known issues with regionally hosted meeting deployments, guidelines, and possible solutions and workarounds.

Regionally hosted meetings is available for limited release only. For more information about the limited release, please contact your Microsoft representative.

For more information, see Plan for regionally hosted meetings in Skype for Business Online, Set up and configure regionally hosted meetings in Skype for Business Online, and Configure your ACP to support regionally hosted meetings.

The following are known issues you might encounter when deploying and managing regionally hosted meetings. Guidelines, solutions, and workarounds are provided if available.

  • Issue: When users are moved from on-premises to online non-default regions, their presence is not visible to users in regions other than the data location where the user is moved until on-premises attributes have replicated from the on-premises environment to Office 365.

    For example, has the allowed data locations NAM (Default), EUR, and APC. If a user is moved to APC by setting the preferred data location first, and then moving the user to online, users in NAM and EUR will not be able to see the user's presence until the AD attributes have synced from the on-premises environment to online. The sync replication, which depends on the sync interval for AAD Connect and the backlog of changes in Office 365 for Skype for Business tenants, can take up to 8 hours.

    Resolution: To avoid presence unknown issues, users should be moved online in the default location first, and then moved to the desired data location by updating the preferred data location after 24 hours.

  • Issue: For users configured with Cloud PSTN conferencing, they cannot be homed on a pool in India for regulatory reasons.

    Resolution: Set the user's preferred data location to APC to move them to Asia; you can then assign them a CPC license, even though they live in India.

  • Issue: The Meeting Migration Service cannot update the user's meetings.

    Resolution: If you have user mailboxes on premises, you need to configure OAuth between Exchange and Office 365 so that the Meeting Migration Service can update the user’s meetings. You must configure OAuth between Skype for Business Online and Exchange on premises.

  • Issue: Cross-forest delegation does not currently work with regionally hosted meetings.

    Resolution: You must move administrators and the managers they support at the same time and to the same region.

  • Issue: Creating and managing meeting rooms are not supported in remote regions.

  • Issue: Organizational Auto Attendant and Call Queues are not fully supported in remote regions. All Auto Attendants and Call Queues are automatically homed in the tenant's primary region by default. Administrators cannot change the default.

  • Issue: Using the Skype for Business admin center to manage regionally hosted meetings will produce inconsistent results and in some cases can actually cause data loss.

    Resolution: You must use Tenant Remote PowerShell for managing users (assigning policies, assigning licenses, changing phone numbers, and so on).

  • Issue: Once enabled, you cannot turn off regionally hosted meetings.

    Resolution: If you decide not to deploy regionally hosted meetings, you will need to move all users back to the home region where your tenant resides.

  • Guideline: When assigning policies, ensure the user has been successfully moved to the target region before running the cmdlets by running Get-CsUserlocationStatus -Identity

  • Guideline: If you use Microsoft Cloud PSTN conferencing for dial-in conferencing, make sure the UsageLocation attribute maps to the region the user will be moved to before you enable them for Cloud PSTN conferencing; otherwise, you’ll need to change the default number assignment using the following command: Set-CsOnlineDialInConferencingUser -Identity