Retention: Resolve Errors in Microsoft 365 Retention and Retention Label Policies

By Ashwin Venugopal -

 






Error: Settings Not Found

Symptoms

While checking the details pane for a retention policy in the Microsoft Purview portal, an error message appear, "Settings not found." 

Cause

The retention policy has no retention rules.

Resolution

To resolve this issue, use either of the following methods.

Method 1: Use the Microsoft Purview Portal
  • In the Microsoft Purview portal, search for the policy on the following tabs- 

  1. Data Lifecycle Management > Microsoft 365 > Retention policies
  2. Data Lifecycle Management > Microsoft 365 > Label policies
  3. Records Management > Label policies 

  • Select the policy, and then select Edit.
  • In Retention settings, add rules to the retention policy.

Method 2: Use PowerShell

  • Connect to Security & Compliance PowerShell.
  • Use the applicable cmdlet for the workload to add rules to the retention policy.  

Use the New-RetentionComplianceRule cmdlet for policies that target-

  1. Microsoft Exchange Online email
  2. Microsoft SharePoint sites
  3. Microsoft OneDrive accounts
  4. Microsoft 365 Groups
  5. Microsoft Skype for Business conversations
  6. Exchange Online public folders
  7. Microsoft Teams chat messages
  8. Teams channel messages

Error: Something Went Wrong

Symptoms

When the details pane is checked for a policy in the Microsoft Purview portal, the error message, "Something went wrong" appears. 

Run the following command, PolicyNotifyError can be seen in the value returned by the DistributionResults property:

Get -RetentionCompliancePolicy -Identity "<policy name>" -DistrbutionDetail | Select  -ExpandProperty DistributionResults

Cause

An unspecified error occurred in the notification pipeline of the policy sync and distribution process. 

Resolution

Use any of the following methods to resolve this issue:

Method 1: Use the Microsoft Purview portal

  • In the Microsoft Purview portal, search for the policy on the following tabs- 

      1. Data Lifecycle Management > Microsoft 365 > Retention policies
      2. Data Lifecycle Management > Microsoft 365 > Label policies
      3. Records Management > Label policies

    •  To open the policy details pane, select the policy. Make sure to select the policy name and the corresponding checkbox. Otherwise, the details pane will not open.

    • In the policy details pane, select Retry. The policy enters a pending state until policy sync and distribution finishes. 

    Method 2: Use PowerShell

    • Connect to Security & Compliance PowerShell.
    • Retry policy sync and distribution. Use the Set-RetentionCompliancePolicy cmdlet along with the RetryDistribution switch to redeploy the policy-

    Set -RetentionCompliancePolicy -Identity "<policy name>" -RetryDistribution

    Error: Your Policy is Stuck in PendingDeletion

    Symptoms

    While trying to delete a policy, the operation fails.

    Cause

    An unspecified error occurred while trying to delete a policy.

    Resolution
    • Connect to Security & Compliance PowerShell.
    • Remove the policy. Use the Remove-RetentionCompliancePolicy cmdlet along with the ForceDeletion switch-

    Remove -RetentionCompliancePolicy -Identity "<policy name>" -ForceDeletion


    Conclusion

    Some errors in Microsoft 365 Retention and Retention Label Policies are resolved. 















    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