Microsoft Purview Troubleshooting: Error when you try to enable or disable an archive mailbox for an Exchange Online user or move a mailbox to an on-premises environment

By Ashwin Venugopal -




Problem

An error message that looks like one of the following appears when you attempt to migrate a mailbox from Exchange Online to an on-premises environment or activate or disable an archive mailbox for an existing Exchange Online user:
  • Error- UserAlreadyBeingMigratedException: The user '<User Email Address>' already has a pending request. Please remove the existing request and resume the current batch or start a new batch for this user. 

  • Mailbox '<User Display Name>' has a completed move request associated with it. Before you create a new move request for the mailbox, run the Remove-MoveRequest cmdlet to clear the completed move request.

  • Mailbox '<User Display Name>' has move status <move status>. You can't enable or disable an archive while the mailbox is being moved.  
When you run the Get-MoveRequest | fl  command to examine the move request, you verify that the request is a Microsoft 365 datacenter move request. This is indicated by the IntraOrg flag. 

Cause

The reason for this issue is because unsuccessful move requests have not yet been deleted from the system. 

Exchange Online frequently switches mailboxes across servers to ensure service health. Move requests for completed Microsoft 365 datacenters are promptly cleared up. Although they may persist for a little while longer, unsuccessful Microsoft 365 datacenter transfer requests are eventually resolved. Users are unaffected by these unsuccessful migration requests. If necessary, the service will attempt the relocation again in the future. 

Solution

Generally, you may safely disregard the error signals if moving the datacenter internally doesn't interfere with your capacity to carry out administrative duties. 

If management tasks are affected by the move requests, follow these steps:
  1. Connect to Exchange Online by using remote Windows PowerShell.
  2. Verify the mailbox is being moved.
  3. Examine the output and then do one of the following, as appropriate:
    1. If the status is Queued or InProgress, wait for the move to finish. This should occur in one or two days. If you can't wait, then remove the move request via-                                          Remove-MoveRequest -Identity IdentityOfFailedRequest
    2. If status is Failed, remove the move request via the same command written above.
This operation should not affect user access or cause any problem. Additionally, you don't have to notify Microsoft or the mailbox owner to take this action. 

Conclusion

The issue of error when you try to enable or disable an archive mailbox for an exchange online user or move a mailbox to an on-premises environment has been resolved with the help of above methods.

Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can...
Read more