Microsoft Purview Troubleshooting: Archive Mailbox can't be Provisioned or Deprovisioned after a Mailbox is Migrated to Office 365 Dedicated/ITAR vNext

By Ashwin Venugopal -

 







Symptom

You are unable to add an archive to a mailbox that has not yet been migrated to Microsoft Office 365 Dedicated/ITAR vNext. Additionally, mailbox that was moved from Dedicated cannot be used to deprovision an archive. 

Cause

The system anticipates that an on-premises Exchange installation will handle all management when Exchange Online is set up in a hybrid architecture. This keeps the web directory and the on-premises directory up to date. 

Exchange Server is frequently not installed on-premises by dedicated users. However, the objects behave as though they are a part of a hybrid deployment as a result of the migration from Dedicated. Installing Exchange on-premises for the vNext transition is not necessary, although management is advised to have Exchange deployment on-premises to make the move smoother and reduce total expenses. Due to this, some users might not be able to control the archives for mailboxes that were moved from Dedicated. 

Resolution

Following a migration, scripts that mimic the features of an on-premises Exchange setup can be used to manage archives for mailboxes that were moved from Dedicated.

Prerequisites

  • The Active Directory Module for Windows PowerShell must be installed on the management computer.
  • The management computer must have .NET 4.0 or a later version installed.
  • The management computer must be domain-joined to the on-premises AD forest of the users who will be managed.
  • The operator must have Account Operator permissions or equivalent rights. 
  • The enable-remotearchive.ps1 and disable-remotearchive.ps1 scripts must be on the management computer. 

Provisioning an Archive

  1. Determine the value for the 'name' property of the user being managed. This step will be passed as the value for the -Identity parameter of the script.
  2. Start PowerShell with the Active Directory Module for Windows PowerShell enabled.
  3. Run the following script:

Enable-remotearchive.ps1 -Identity 'X'

      4. Wait for Microsoft Entra Connect to synchronize the changes.

Deprovisioning an Archive

  1. Determine the value for the 'name' property of the user being managed. This step will be passed as the value for the -Identity parameter of the script.
  2. Start PowerShell with the Active Directory Module for Windows PowerShell enabled.
  3. Run the following script:

    4. disable-remotearchive.ps1 -Identity 'X'

      4. Wait for Microsoft Entra Connect to synchronize the changes. 

Conclusion

The issue of that the Archive Mailbox can't be provisioned or deprovisioned after a mailbox is migrated to Office 365 Dedicated/ITAR vNext is resolved with the help of above steps.










































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