Microsoft Teams : Group Policy Assignment Issue and Resolutions:

 Hello All

Hope everyone is doing great, today i would like to share the experience which i faced  for the one the issue described below in Microsoft Teams.

Background Scenario.

Recently in my tenant recording consent has been enabled globally from meeting policy. Few users reported that, recording consent is not working as expected. 

Upon the checking the end users meeting policies, the global meeting policy was not assigned instead , custom policy was assigned 

As we all know that,there is limitation in  recording consent, which   wont work if attendee report is set to off in any of the meeting policies

Tried via Powershell

So i decided to move the users from custom policy to Global meeting policy,  When i set the policy to global for the users , its not working as expected, and the users are reverted  back to custom policy .

Reason :  Yes your guess is correct. The custom policy was assigned via group Policy assignment along with Dynamic Distribution Groups created in Microsoft entra.

I have deleted the group policy from teams admin center, however the behaviour is same , and am unable to change the meetings policy from custom to global as it still inherited from group policy.

Resolution : Login to  Microsoft Entra -- >Groups -->Choose the Dynamic Distribution Groups --->Broke the rule 

 

After Few Minutes, Am able to change the meetings policy from custom to global for the users and finally recording consents started working for them .

Its still surprise, why i cannot change the policy from custom policy to global one, even i deleted the group policy assignment in Teams Admin Center. May be this is bug for me?

Scenario : What is the best method to mitigate the issue? if you are using Dynamic distribution Groups  for group policy assignment and you don't want to use the custom policy.

1. Break the dynamic Distribution Group rules

2. Delete the Groups from Microsoft Entra 

3. Remove the group Policy Assignment from Teams Admin Center,

4. Change the user policy from custom to global from TAC or Powershell

I believe, this wold helpful if anyone come across the above situation. Happy Learning 😃