Setting up future meetings with participants using Teams calendar or Outlook integration
A common cause is policy propagation and policy scope.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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: