Meeting policy changes are not applying to new users

Hardison Dromgoole 0 Reputation points
2026-11-15T21:47:18.62+00:00

I've updated the meeting policies in Teams Admin Center to prevent anonymous users from starting meetings, but some newly onboarded employees can still do so. The policy settings look correct on my end, not sure why they're not being applied consistently.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Schedule meetings
0 comments No comments

2 answers

Sort by: Oldest
  1. AI answer

    2026-11-15T21:47:34.25+00:00

    A common cause is policy propagation and policy scope.

    1. Verify the correct policy is assigned to the affected new users.
      • In Teams, meeting policies are per-user policies.
      • Meeting scheduling and join/lobby settings are controlled through Meetings > Meeting policies.
      • If a new user was not assigned the intended custom policy, they can still inherit a policy that allows the behavior.
    2. Check the specific setting in the assigned meeting policy.
      • In Teams admin center > Meetings > Meeting policies > selected policy > Meeting join & lobby, confirm Anonymous users and dial-in callers can start a meeting is Off.
      • This setting is Off by default.
    3. Confirm the related anonymous join settings are aligned.
      • In the same meeting policy, confirm Anonymous users can join a meeting is set as intended.
      • Also check Teams admin center > Meetings > Meeting settings > Participants > Anonymous users can join a meeting.
      • If anonymous meeting access is allowed, the start-meeting behavior still depends on the meeting policy setting above.
    4. Allow time for policy changes to apply.
      • Changes to meeting policies can take up to 24 hours to take effect.
      • This can explain why newly onboarded employees appear inconsistent immediately after onboarding or policy assignment.
    5. If the goal is to stop anonymous participants from starting meetings, keep the setting off.
      • When Anonymous users and dial-in callers can start a meeting is Off, anonymous participants and dial-in callers wait in the lobby until a verified participant starts the meeting.
      • This is the recommended configuration.
    6. If the issue is only with newly onboarded users, focus on onboarding assignment timing.
      • Since meeting policies are per-user, confirm the intended meeting policy is applied as part of the user onboarding process.
      • If users are tested before the policy assignment has completed or before propagation finishes, behavior can differ temporarily.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Aetherin 4,095 Reputation points Independent Advisor
    2026-11-15T22:11:42.46+00:00

    Hi @Hardison Dromgoole,

    Could you confirm whether the affected users receive the meeting policy through the Global policy, a direct assignment, a group assignment, or a policy package?

    Also, under Teams admin center > Users > Manage users > affected user > Policies, which meeting policy is currently shown for them?

    If the policy is assigned through a group, newly added members may not receive it immediately because group policy assignments are processed as a background operation. Please also check whether the users have a direct assignment or inherit another group policy with a higher ranking, as this could determine their effective policy.

    An administrator can verify the user’s effective meeting policy in Teams PowerShell:

    Connect-MicrosoftTeams
    Get-CsUserPolicyAssignment `
        -Identity ******@contoso.com `
        -PolicyType TeamsMeetingPolicy
    

    For your reference, please see: Get-CsUserPolicyAssignment

    This command shows the user’s effective policy and whether it was assigned directly or inherited from a group.

    Then verify the relevant setting in the returned policy:

    Get-CsTeamsMeetingPolicy -Identity "PolicyName" |
        Select-Object Identity, AllowAnonymousUsersToStartMeeting
    

    Please also clarify how the behavior was tested. If a newly onboarded employee was signed in and started a meeting that they organized, they were not acting as an anonymous user. This setting specifically controls whether anonymous participants and dial-in callers can start the meeting before an authenticated participant is present. If there are any updates, please kindly post them in the comments section so I can receive a notification and continue supporting you.

    Thank you for taking the time.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.