Fix Teams Meeting Policy Is Missing in a New Tenant

When you create a new Microsoft 365 tenant and open the Teams admin center, the Meeting policies page may show no policies at all. This leaves you unable to assign a meeting policy to users, and meeting features like recording or lobby bypass cannot be controlled. The root cause is usually a delay in the automatic provisioning of the default Global policy, or the policy was accidentally deleted. This article explains why the policy can disappear and gives you a step-by-step method to restore it.

You will learn how to recreate the missing Global policy, how to assign it to users, and what to do if the policy still does not appear after you follow the main fix.

Why the Global Meeting Policy Is Missing in a New Tenant

In a new Microsoft 365 tenant, Teams is provisioned automatically when the first Teams license is assigned. This provisioning process creates the default meeting policy named Global. In most cases, the policy appears in the Teams admin center within a few hours. However, two common scenarios lead to a missing policy.

First, the provisioning service can be delayed. If you assign a Teams license and immediately open the Teams admin center, the Global policy may not yet be created. The admin center uses a cached list of policies, and that cache updates on a schedule. You might see an empty policy list even though the backend has already created the policy.

Second, a user with the Teams administrator role can delete the Global policy. Teams allows the Global policy to be deleted, but it does not warn that this removes the default policy for all users. After deletion, the meeting policies page shows no policies, and you cannot create a new one manually because Teams requires that a Global policy always exists.

What the Global Policy Controls

The Global policy is the default meeting policy that applies to all users who do not have a specific policy assigned. It controls settings like:

• Meeting recording
• Lobby bypass
• Who can present
• Meeting chat
• Screen sharing

Without a Global policy, Teams meetings still work with the built-in defaults, but you lose the ability to change these settings for all users. You must restore the policy to regain control.

Steps to Diagnose and Restore the Missing Meeting Policy

Follow these steps in order. The first step checks whether the policy actually exists behind the scenes. The second step recreates it if needed. The third step assigns it to users.

1. Check the policy list in the Teams admin center
   Go to the Teams admin center at admin.teams.microsoft.com. Sign in with an account that has the Teams administrator or Global administrator role. In the left navigation, select Meetings, then select Meeting policies. Look for a policy named Global in the list. If you see it, the policy was not missing, but the admin center was slow to display it. If the list is empty, continue to the next step.
2. Wait for automatic provisioning
   If you created the tenant or assigned the first Teams license less than 24 hours ago, wait up to 24 hours. The provisioning service runs periodically and creates the Global policy. After waiting, refresh the Meeting policies page. If the Global policy appears, the issue is resolved. If not, proceed to the next step.
3. Recreate the Global policy using PowerShell
   Open Windows PowerShell as an administrator. Install the Teams PowerShell module if you have not done so. Run the command Install-Module -Name MicrosoftTeams -Force. Then connect to Teams with Connect-MicrosoftTeams. After connecting, run the command New-CsTeamsMeetingPolicy -Identity Global. This recreates the default policy with the standard settings. To verify, run Get-CsTeamsMeetingPolicy -Identity Global. You should see the policy details.
4. Confirm the policy appears in the admin center
   Go back to the Teams admin center and refresh the Meeting policies page. The Global policy should now appear. If it does not, sign out and sign back in to the admin center, or use a private browser window. The admin center sometimes caches the old list.
5. Assign the Global policy to users
   In the Teams admin center, go to Users, then select Manage users. Select the users who need this policy. Click Edit, then under Policies, select the Meeting policy dropdown and choose Global. Click Apply. Alternatively, you can assign the policy using PowerShell with the command Grant-CsTeamsMeetingPolicy -Identity user@domain.com -PolicyName Global.

Using PowerShell to Verify All Meeting Policies

The admin center may hide a policy if it is corrupted or has a naming conflict. Use PowerShell to list all policies. Run Get-CsTeamsMeetingPolicy. This shows every policy, including those not visible in the admin center. If you see a policy named Global here, but not in the admin center, the policy exists and the issue is a display problem. In that case, restart the admin center or use a different browser.

If Teams Still Has Issues After the Main Fix

Teams Shows No Meeting Policies Even After Recreating Global

If you recreated the Global policy but the Meeting policies page is still empty, the Teams admin center may be syncing slowly. Wait 30 minutes and refresh. If the problem persists, check that your account has the correct admin role. You need the Teams administrator role or the Global administrator role. A user with only the Teams communication administrator role cannot see meeting policies.

Users Cannot Join Meetings After You Assign the Policy

If you assigned the Global policy and users still cannot join meetings, the issue is not the policy. Check the user’s license. Go to the Microsoft 365 admin center, select Users, then Active users. Select the affected user and check the Licenses and apps tab. The user must have a Teams license assigned. Without a license, the policy has no effect.

The Global Policy Disappears Again After a Few Hours

If the Global policy keeps disappearing, a script or an automated process is deleting it. Check the audit log in the compliance center. Go to compliance.microsoft.com, select Audit, and search for the operation Delete-CsTeamsMeetingPolicy. This shows which admin deleted the policy. If you find a scheduled script, remove it.

New Tenant Provisioning vs Manual Policy Creation: Key Differences

Item	Automatic Provisioning	Manual Creation via PowerShell
Timing	Happens within 24 hours of first license assignment	Immediate when you run the command
Settings	Uses Microsoft’s default meeting settings	Uses the same default settings unless you specify others
Visibility	Appears in admin center after provisioning completes	Appears in admin center immediately after creation
Reliability	Can be delayed or fail silently	Always works if the command runs successfully
Recovery	No manual action needed if you wait	Required if provisioning fails or policy is deleted

The table shows that manual creation is the faster and more reliable way to restore a missing Global policy. Use it when automatic provisioning does not complete.

After you restore the Global policy, you can also create custom meeting policies for different user groups. Go to Teams admin center > Meetings > Meeting policies, then select Add to create a new policy. Name it, adjust the settings, and assign it to specific users. This gives you granular control over meeting features like recording and lobby bypass.

To prevent this issue in the future, avoid deleting the Global policy. If you must customize settings, create a new policy instead of modifying Global. Also, check the audit log regularly to catch any accidental deletions.

Your next action is to run the PowerShell command Get-CsTeamsMeetingPolicy to confirm the Global policy exists. If it does not, use New-CsTeamsMeetingPolicy -Identity Global to recreate it. Then assign the policy to your users with Grant-CsTeamsMeetingPolicy. This restores full control over your Teams meeting settings.