Share via

Enable Mailbox Archive Problem

Anonymous
2023-06-15T16:43:53+00:00

When I try to enable Archive on Exchange Online administrator am getting the error: Error executing cmdlet. When I run the command (Enable-Mailbox <EMAIL> -Archive) on PowerShell I get the error enable-Mailbox: |Microsoft.Exchange.Data.Directory.MissingDisconnectReceiptsException|AD modification is not allowed - disconnect of shard with ExchangeGuid <GUID> is not authorized.

The user is licensed with Office 365 E3 license and archiving is working for all other mailboxes.

No litigation hold on the mailbox.

Does anyone have a working solution?

Microsoft 365 and Office | Install, redeem, activate | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-07-06T05:06:56+00:00

    Dear De Paul N. Kwizera MSFT,

    Below is the PowerShell error

    And below is the error on the Exchange Admin portal

    The account was migrated to Exchange Online and had an on-premise archive enabled before migration.

    After a long back and forth with Microsoft support, I was able to resolve the issue using the following procedure.

    1. Disable the Archive on the on-premise Exchange admin
    2. Did AD Sync.
    3. Removed Office license on https://admin.microsoft.com/
    4. Did AD Sync again
    5. Enabled Archiving on Exchange Online
    6. Started Managed Folder Assistant: Start-ManagedFolderAssistant -Identity <email>
    7. Archiving was restarted.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2023-06-15T18:40:23+00:00

    Dear Wambua O Thyaka,

    Good day! Thank you for posting to Microsoft Community. We are happy to help you.

    Based on your description, I understand that you have a query "Enable Mailbox Archive Problem." Before we proceed, we need more detailed information about the situation you are experiencing. Did the use have been migrated currently? If so, does the mailbox had an on-premises Archive? Please provide the detailed PowerShell error screenshot for further investigation.

    We look forward to hearing from you; Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution. Thank you for your cooperation.

    Sincerely,

    De Paul | Microsoft Community Moderator

    Was this answer helpful?

    0 comments