Fix Teams Meeting Policy Is Missing for a Security Group

You assigned a Teams meeting policy to a security group, but the policy does not appear in the group’s settings. The policy may be missing from the Teams admin center or from the group’s policy assignments. This issue often occurs when the policy is not created correctly or when the group is not properly linked to the policy. This article explains why the policy goes missing and provides step-by-step fixes to restore it.

Why the Teams Meeting Policy Disappears for a Security Group

A Teams meeting policy controls features like who can record, who can share, and who can bypass lobby. When you assign a policy to a security group, Teams applies the policy to all users in that group. The policy can appear missing for several technical reasons.

The most common cause is that the policy was never fully created. If you created the policy but did not click Save or Apply, the policy may not be visible. Another cause is that the policy was deleted after assignment. Deleting a policy that is assigned to a group removes the assignment, so the policy no longer appears.

A third cause is a delay in propagation. Teams policies can take up to 24 hours to apply to all users and groups. If you check immediately after assignment, the policy may not show yet.

Policy assignment hierarchy and group precedence

Teams applies policies in a specific order. The user’s direct policy assignment takes precedence over a group policy. If a user has a direct policy assignment, the group policy may appear missing for that user. Also, if multiple groups assign different policies to the same user, the policy from the group with the highest precedence wins. If the group is not the highest precedence, the policy may not be effective.

Security group type and licensing

Only security groups and Microsoft 365 groups with security enabled can receive Teams policies. Distribution groups and mail-enabled security groups are not supported. Also, each user must have a valid Teams license. Without a license, the policy assignment may not appear.

Steps to Restore the Missing Teams Meeting Policy

Follow these steps in order to diagnose and fix the missing policy. You need Teams admin permissions to perform these steps.

Step 1: Verify the policy exists in the Teams admin center

1. Open the Teams admin center
   Go to Teams admin center > Meetings > Meeting policies. Check if your policy name appears in the list.
2. Check for deleted policies
   If the policy is not listed, click Add to create it again. Use the same name and settings as before. Then assign it to the group again.
3. Confirm the policy is not a global policy
   If you used the Global policy, it is always present. But if you expect a custom policy, it must be created first.

Step 2: Verify the policy assignment to the security group

1. Go to group settings
   In the Teams admin center, go to Teams > Groups > Security group. Select your group.
2. Check the Policies tab
   Click Policies to see all assigned policies. Look for your meeting policy under Meeting policy.
3. Assign the policy if missing
   Click Edit, then select your meeting policy from the dropdown. Click Apply.

Step 3: Use PowerShell to confirm the assignment

1. Install the Teams PowerShell module
   Open Windows PowerShell as administrator and run Install-Module -Name MicrosoftTeams.
2. Connect to Teams
   Run Connect-MicrosoftTeams and sign in with your admin account.
3. Get the policy assignment
   Run Get-CsGroupPolicyAssignment -GroupId "your-group-id" to list all policies assigned to the group. Look for your meeting policy.
4. Assign the policy if needed
   If the policy is missing, run New-CsGroupPolicyAssignment -GroupId "your-group-id" -PolicyType "Meeting" -PolicyName "Your Policy Name".

Step 4: Wait for propagation and check user-level assignments

1. Wait up to 24 hours
   After assigning the policy, wait at least 24 hours before checking again. Teams policies propagate slowly.
2. Check a user’s effective policy
   Go to Teams admin center > Users > Manage users. Select a user in the group. Under Policies, check the effective meeting policy.
3. Remove direct assignments if they override
   If a user has a direct policy assignment, remove it so the group policy can apply. Use the Edit option in the user’s policy tab.

If the Teams Meeting Policy Still Does Not Appear

Teams shows “Policy not found” when assigning to a group

This error occurs when the policy name is typed incorrectly or the policy was deleted. Recreate the policy with the exact name and then assign it again.

Users in the group do not get the policy settings

Check if the users have a direct policy assignment that overrides the group policy. Also verify that the users have a Teams license. Without a license, the group policy is not applied.

The security group is not listed in the policy assignment dropdown

Only security groups and Microsoft 365 groups with security enabled appear in the dropdown. If your group is a distribution group, convert it to a security group first in the Microsoft 365 admin center.

Policy propagation takes longer than 24 hours

In rare cases, propagation can take up to 48 hours. If the policy still does not appear after 48 hours, contact Microsoft Support with the group ID and policy name.

Teams Meeting Policy Missing: Group vs Direct Assignment

Item	Group Policy Assignment	Direct Policy Assignment
Scope	Applies to all users in the security group	Applies to one specific user
Precedence	Lower than direct assignment	Higher than group assignment
Management	Teams admin center > Groups > Security group	Teams admin center > Users > Manage users
Propagation time	Up to 24 hours	Up to 24 hours
Best for	Large groups with uniform needs	Individual exceptions

Now you can restore a missing Teams meeting policy for a security group. First check that the policy exists in the Teams admin center. Then verify the group assignment and use PowerShell to confirm. Wait up to 24 hours for propagation to complete. If the policy still does not appear, check for direct assignments or licensing issues. Use the Get-CsGroupPolicyAssignment cmdlet to troubleshoot any remaining problems.