Deploy and manage a Microsoft 365 tenant →hardMultiple Choice

MS-102 Deploy and manage a Microsoft 365 tenant Practice Question

You are a Microsoft 365 administrator. Users report that they cannot create Microsoft Teams meetings using the Teams desktop client. They receive an error: 'Meeting creation is disabled by your IT administrator.' You need to enable meeting creation. You check the Teams admin center and find that meeting policies are set to 'Off' for 'Allow private meeting scheduling'. However, after changing it to 'On', users still get the error. What is the most likely cause?

⚠ Common exam trap

A common mix-up: candidates assume changing the meeting policy in the Teams admin center is sufficient, overlooking the critical dependency on Exchange Online for Teams calendar features, which is a common misconfiguration in hybrid environments.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The user's mailbox is still on-premises and not migrated to Exchange Online.

The error persists because the user's mailbox is still on-premises and not migrated to Exchange Online. Microsoft Teams relies on Exchange Online for scheduling features, including private meeting creation. Even with the meeting policy set to 'On', if the mailbox is on-premises, the Teams client cannot communicate with Exchange Online to create the meeting, resulting in the error.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The user does not have an OAuth 2.0 token.
Why it's wrong here
OAuth 2.0 tokens are used only to authenticate and authorize API calls and client requests to Microsoft 365 services. Team meeting policies—such as recording or meeting creation settings—are applied server-side based on the user's policy assignment in Teams, not via token claims. A missing token would prevent the Teams client from connecting, but it would not cause a correctly assigned user-level meeting policy to be ignored.
✗
The global meeting policy is overriding the user-level policy.
Why it's wrong here
In Microsoft Teams, policy precedence gives the user's directly assigned custom policy priority over the global (Org-wide) default policy. If a user is explicitly assigned a meeting policy, the global policy does not override it. Since the error persists even after assigning a user-level policy, the root cause is not precedence, but rather the absence of an Exchange Online mailbox where the policy enforcement can actually take effect.
✓
The user's mailbox is still on-premises and not migrated to Exchange Online.
Why this is correct
Teams meeting schedules are stored in the user's Exchange calendar. When the user mailbox remains on-premises in a hybrid deployment, the Teams meeting policy is ineffective because the online meeting workspace is controlled by Exchange on-premises, not by Exchange Online. Only after the mailbox is migrated to Exchange Online will Teams be able to provision the meeting workspace and enforce the assigned meeting policy.
✗
The user does not have a Microsoft Teams license assigned.
Why it's wrong here
A Microsoft Teams license is required to use the Teams client and to have a Teams service instance, but meeting policy assignments are independent of licensing. Administered policies are stored in the Teams admin database and apply to any user with a policy assignment, even if the license is temporarily missing. Therefore, a licensing gap would block service access, but it does not explain why a correctly assigned meeting policy fails to take effect.

Go deeper

MS-102 Deploy and manage a Microsoft 365 tenant Practice Question

Why each option matters

Option-by-option breakdown

Related to this question