You can't move a mailbox to a different region in Office 365 dedicated/ITAR


When you try to move a mailbox to a different region in Microsoft Office 365 dedicated/ITAR, you experience the following issues:
  • After you update the mailbox provisioning attribute to move a mailbox to a different region, you can't move the mailbox.
  • After you update the MailboxProvisioningConstraint attribute on a mailbox to move the mailbox to a different region, you can't move the mailbox.


A mailbox may not be moved to the appropriate region for many reasons. Common reasons are as follows: 
  • A different method is necessary because of the environment in which the mailbox is located.
  • A move request already exists for that mailbox.
  • The move request isn't discovered and initiated by the server.


To move a mailbox between regions, use one of the following methods, depending on your Microsoft Exchange Server environment. 

For Exchange Server 2010

To move a mailbox between regions in an Exchange Server 2010 environment, see the O365D-ITAR Provisioning Tools Handbook.

In Exchange Server 2010, the mailbox provisioning attribute is an Active Directory extension attribute (also known as an Exchange custom attribute) that is associated with an Active Directory user object. This value sets some options that are related to the mailbox. These options include the geographic region where the mailbox will reside. In Exchange Server 2010, the datacenter region value is REG=. The region code options are as follows. 

O365D datacenterValue
North AmericaREG=NA;
You must set the appropriate region code on the Active Directory object in the target environment for the mailbox to move to the correct region. 

For Exchange Server 2013

To move a mailbox between regions in an Exchange Server 2013 environment, see the Self Service Mailbox Migration Guide.

The mailbox provisioning attribute may be used for the initial provisioning of the mailbox (as in Exchange Server 2010). However, this value is no longer used after this initial provisioning. 

For Exchange Server 2013, updating the MailboxProvisioningConstraint attribute of the mailbox lets you indicate the region in which the mailbox should reside. The system will move the mailbox to the appropriate region if the mailbox isn't in a datacenter in the correct region.

Note Unlike the mailbox provisioning attribute, the MailboxProvisioningConstraint attribute has the following characteristics: 
  • The MailboxProvisioningConstraint attribute isn't set in the customer environment or in Active Directory.
  • The MailboxProvisioningConstraint attribute doesn't sync through Microsoft Managed Solutions Services Provisioning Provider (MMSSPP).
  • The MailboxProvisioningConstraint attribute is set directly on the mailbox in the managed environment.
To set the MailboxProvisioningConstraint attribute, run the following cmdlet:
Set-Mailbox –Identity <MailboxIdParameter> -MailboxProvisioningConstraint "{Region -eq '<RegionCode>'}" 
The RegionCode values are as follows:

O365D datacenterThe Mailbox provisioning constraint RegionCode value
North AmericaNAM
It's recommended that the REG= value in the mailbox provisioning attribute should be removed when the MailboxProvisioningContraint attribute is set.

Move requests

An existing move request may slow down or stop a regional move request. To determine whether a move request exists, run the following cmdlet if you have appropriate permissions: 
Get-MoveRequest -Identity '<MaiboxIDParameter>’ | fl 
The Status parameter displays a value of InProgress if a mailbox move is in progress. If the move request is associated with the regional move, the TargetDatabase parameter displays a database in the appropriate region. If this mailbox move isn't associated with the regional move request, this move request has to complete before the regional move occurs. 

If a move request doesn't show a status of InProgress within 24 hours of the appropriate parameter being set, or if the status reads any other value, contact Microsoft Support for help.


ID d'article : 3107809 - Dernière mise à jour : 11 août 2016 - Révision : 1