Steps for all ACPs for regionally hosted meetings



After you have configured specifics for your audio conferencing provider (ACP), read this topic to learn how to complete the steps common to all ACPs to support regionally hosted meetings.

For more information, see Configure your ACP to support regionally hosted meetings.

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

After you have modified the AcpInfo XML settings with vendor-specific values for the target region, complete the following steps. These steps apply to all ACP vendors:

Rick: The following note was incomplete in your source doc:

Ito prev, it is recommended that Cloud PSTN conferencing license assignment happens after the cross region move completes to prev

The Set-CsUserAcp cmdlet will automatically trigger the meeting migration service if the tenant-level setting ACPMeetingMigrationTriggerEnabled is set to $True. In general, moving the user to the target region 30 minutes after the meeting migration service runs ensures that migration has completed successfully, but you can also confirm success by running the following cmdlet:

Get-CsMeetingMigrationStatus -Identity <SipAddress> | fl State, LastMessage

You will see confirmation, such as:

State       : Succeeded
LastMessage       : Meeting migration completed.

If the meeting migration service didn’t complete for some reason, you can trigger it manually by using the following cmdlet:

Start-CsExMeetingMigration -Identity <SipAddress>
If the meeting migration service doesn’t complete after multiple attempts, confirm that the user's mailbox is homed in Exchange Online. If the mailbox is stored in Exchange on premises, ensure that OAuth is configured between Exchange on premises and Office 365.

In the on-premises Active Directory, locate the user being moved cross region, populate the unused attribute you’ve selected for storing the 3-digit PDL code (APC, AUS, CAN, EUR, JPN or NAM), and use Azure AD Connect to trigger a delta sync to push the value to the corresponding PreferredDataLocation attribute in Azure AD.

The Cloud PSTN conferencing provisioning service will notice the change in the PreferredDataLocation value on the next cycle (within approximately 20 minutes) and begin the cross-region move.

If you haven’t set up preferred data location synchronization, go to Enable synchronization of PreferredDataLocation and follow the instructions.

This step applies only to customers who are performing an ACP to Cloud PSTN conferencing migration as part of a cross-region move.

Assigning the Cloud PSTN conferencing license after the user is in the target may prevent an extra email from being sent to meeting Organizers and Attendees, but it is not a requirement.

To confirm the cross-region move is complete, run the Get-CsUserLocationStatus cmdlet as follows:

Get-CsUserLocationStatus -Identity <SipAddress>

If you do not know the account Sku ID, run the following cmdlet:


Next, assign a Cloud PSTN conferencing license to the user, as shown in the following example:

Set-MsolUserLicense -UserPrincipalName <SipAddress> -AddLicenses <AccountSkuId>:MCOMEETADV

To confirm that the user was moved successfully, run the following cmdlet:

Get-CsUserLocationStatus -Identity <SipAddress>

After the user signs in from the target region, they should confirm that Attendees can dial in to any unexpired and new meetings. If the Attendees end up listening to Music on Hold, it is usually an indication that the dial-in conferencing setting are inaccurate or not configured properly with the ACP vendor.

If you run the following cmdlet and the dial-in coordinates match what was provided by your ACP vendor, follow up with your vendor to confirm that licensing and SIP Address mapping completed successfully, and to help with further troubleshooting.

Get-CsUserAcp -Identity <SipAddress>