-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SCRetentionCompliancePolicy TeamsChatLocation not enabled in the Tenant after creating Microsoft Teams Chat Standard Retention Policy/Rule via DSC #2472
Comments
|
I am trying to better understand the issue at hand. Let's say I am using the following config:
The policy gets created properly, but is disabled, because its Enabled parameter is set to $false. What is the issue exactly? |
Changed it Enabled = $True; for Microsoft Teams Chat Standard Retention Policy
It dosen't enable the TeamsChatLocation on the GUI.
|
Here is the Power-Shell Skript how should it work in the DSC -DistributionDetail should be provieded if not the TeamsChatLocation: {All} would not be shown in the Power-Shell if Get command is executed but only like this TeamsChatLocation: {}
|
The resource is already using the -DistributionDetail switch. This was fixed in a release 2 weeks ago. I am investigating why switching Enabled from False to True on a policy doesn't kick in. |
Details of the scenario you tried and the problem that is occurring
SCRetentionCompliancePolicy -Name 'Microsoft Teams Chat Standard Retention Policy' can be created with the following PS Code but the settings weren't applied correctly on the tenant:
SCRetentionCompliancePolicy -Name 'Microsoft Teams Chat Standard Retention Policy' can be crated with -TeamsChatLocation 'All' attribute but it was not enabled on the Tenant via Microsoft365DSC.
In PowerShell when I run the following commands everything seems to be working fine for SCRetentionCompliancePolicy and i can see the changes in the Tenant and TeamsChatLocation its enabled:
The DSC configuration that is used to reproduce the issue (as detailed as possible)
MOF file extract:
The text was updated successfully, but these errors were encountered: