Retention Policy Visible in Microsoft Purview but Not Returned by Get-RetentionCompliancePolicy PowerShell

Amrish Patel 0 Reputation points
2026-08-14T13:02:44.36+00:00

Hello,

We have a Microsoft Teams retention policy that is visible and enabled in Microsoft Purview, but we are unable to retrieve it using Compliance PowerShell.

Policy Details

Policy Name:

Microsoft Teams Data Retention Policy - 3 Year

Workloads:

  • Teams chats
  • Teams channel messages

Status in Purview:

Enabled (Success)

Issue

When running the following command:

PowerShell

Get-RetentionCompliancePolicy -Identity "Microsoft Teams Data Retention Policy - 3 Year"

Show more lines

we receive the error:

Plain Text

The operation couldn't be performed because object

'Microsoft Teams Data Retention Policy - 3 Year'

couldn't be found on 'FfoConfigurationSession'.

Show more lines

Additional Information

Connected successfully using:

PowerShell

Connect-IPPSSession

Show more lines

When running:

PowerShell

Get-RetentionCompliancePolicy | Select Name, Guid

Show more lines

the output does not include the Teams 3-Year policy. It only shows:

Plain Text

Microsoft Teams Data Retention Policy - 1 Year

Show more lines

Similarly, the following command does not show any rule associated with the Teams 3-Year policy:

PowerShell

Get-RetentionComplianceRule | Select Name, Policy

Show more lines

What We Need

  1. Is there a known issue where a retention policy is visible in the Purview portal but not returned through PowerShell?
  2. Is there an alternative PowerShell cmdlet to retrieve the policy details and assigned users?
  3. Does this indicate a backend synchronization issue between Purview and Compliance PowerShell?
  4. How can we export the users covered by this retention policy?

Any guidance would be greatly appreciated.

Thank you.Question:

Hello,

We have a Microsoft Teams retention policy that is visible and enabled in Microsoft Purview, but we are unable to retrieve it using Compliance PowerShell.

Policy Details

Policy Name:

Microsoft Teams Data Retention Policy - 3 Year

Workloads:

  • Teams chats
  • Teams channel messages

Status in Purview:

Enabled (Success)

Issue

When running the following command:

PowerShell

Get-RetentionCompliancePolicy -Identity "Microsoft Teams Data Retention Policy - 3 Year"

Show more lines

we receive the error:

Plain Text

The operation couldn't be performed because object

'Microsoft Teams Data Retention Policy - 3 Year'

couldn't be found on 'FfoConfigurationSession'.

Show more lines

Additional Information

Connected successfully using:

PowerShell

Connect-IPPSSession

Show more lines

When running:

PowerShell

Get-RetentionCompliancePolicy | Select Name, Guid

Show more lines

the output does not include the Teams 3-Year policy. It only shows:

Plain Text

Microsoft Teams Data Retention Policy - 1 Year

Show more lines

Similarly, the following command does not show any rule associated with the Teams 3-Year policy:

PowerShell

Get-RetentionComplianceRule | Select Name, Policy

Show more lines

What We Need

  1. Is there a known issue where a retention policy is visible in the Purview portal but not returned through PowerShell?
  2. Is there an alternative PowerShell cmdlet to retrieve the policy details and assigned users?
  3. Does this indicate a backend synchronization issue between Purview and Compliance PowerShell?
  4. How can we export the users covered by this retention policy?

Any guidance would be greatly appreciated.

Thank you.

Microsoft Security | Microsoft Purview

1 answer

Sort by: Most helpful
  1. Himaja Y 280 Reputation points Microsoft External Staff Moderator
    2026-08-19T08:38:06.2066667+00:00

    Hi Amrish Patel

    Thank you for providing the details.

    Since the policy is showing as Enabled (Success) in Microsoft Purview but is not appearing in PowerShell, please first try the Teams-specific command:

    PowerShell

    Get-RetentionCompliancePolicy
    Select
    

    Also check whether a retention rule exists:

    Get-RetentionComplianceRule
    

    Please also verify whether the policy is assigned to specific users/groups or uses an adaptive scope.

    If the policy is still missing from both PowerShell commands while it is showing as Enabled (Success) in Purview, it may require Microsoft backend/service-side investigation.

    We recommend raising a Microsoft Support request with the policy name/GUID and the PowerShell command outputs.

    At this stage, we cannot confirm that it is definitely a synchronization issue, but the difference between the Purview portal and PowerShell should be investigated further.

    If this information answers your question, please consider marking the answer as Accepted so it can help other community members with similar questions. 

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.