Holds: Retention Policy No Longer Works After a Mailbox is Moved From the On-Premises Environment to Exchange Online

By Ashwin Venugopal -

 





Symptoms

When you transfer a mailbox from an on-premises Exchange setup to Exchange Online within a hybrid deployment, the retention policy associated with that mailbox ceases to function. You may encounter this problem despite having completed one or both of the actions listed below:
  1. You recreated the retention policy and assigned it to the mailbox.
  2. You recreated the retention tag and included it in the retention policy.

Cause

Retention hold has been activated on the mailbox. Typically, retention hold is automatically activated when a mailbox transitions from the on-premises environment to Exchange Online. When a mailbox is under retention hold, the application of the retention policy for that mailbox is halted. To verify that retention hold is enabled on a mailbox, follow these steps:
  • Connect to Exchange Online by using remote PowerShell.

  • Run the command-

Get-mailbox user@contoso.com |fl

  • Examine the output. If the RetentionHoldEnabled parameter is set to True, retention hold is enabled. 

Resolution

Disable retention hold on the mailbox via these steps:
  • Connect to Exchange Online by using remote PowerShell.

  • Run the command:

Set-Mailbox user@contoso.com -RetentionHoldEnabled $false

Conclusion

The issue regarding this particular hold is resolved via above method.


































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