MeetSwift LogoMeetSwift

Help / Microsoft Teams

Set up Microsoft Teams for MeetSwift

MeetSwift joins Microsoft Teams meetings as a participant named MeetSwift. Teams treats it as an anonymous participant: it has no account in your company and needs no password from you. Your Teams admin decides whether anonymous participants can join and how they are admitted. This guide lists the settings to check.

Contact us at info@meetswift.com

What MeetSwift can access

  • MeetSwift joins as a guest participant named MeetSwift. It records and transcribes only a meeting it is admitted to and that your workspace has consented to capture.
  • MeetSwift never asks for a customer Microsoft password or a Teams account. The bot does not get general access to your inbox, files or chat history.
  • Connecting a Microsoft calendar is separate: that sign-in reads metadata from the calendar you selected and authorized, such as meeting times and join links, so MeetSwift knows which meetings to join.
  • Recording consent and meeting access are separate. Admitting the bot does not replace telling attendees that the meeting is recorded and obtaining any consent the law requires.

Plain-language note: people often call any outside participant a guest. Microsoft uses two different words. A Microsoft guest is someone signed in with an account added to your organization. An anonymous participant joins without signing in. MeetSwift joins as an anonymous participant, so the settings below are about anonymous users, not Microsoft guest access.

Settings for your Teams admin

  1. 01

    Allow anonymous users in organization meeting settings, if this control is shown

    Teams admin center (admin.teams.microsoft.com) > Meetings > Meeting settings > Participants

    • Set Anonymous users can join a meeting to On, then select Save.
    • This is a legacy organization-wide control that Microsoft is retiring. If your tenant no longer shows it, continue to the next step.
  2. 02

    Allow anonymous join in meeting policies

    Teams admin center > Meetings > Meeting policies

    • Open Global (Org-wide default) and every custom policy assigned to people who organize meetings MeetSwift should join.
    • Under Meeting join & lobby, set Anonymous users can join a meeting unverified to On. Older versions of the admin center may label it Anonymous users can join a meeting.
    • Select Save on each policy you change.

    Prefer a targeted custom policy assigned to the organizers who use MeetSwift instead of loosening settings for everyone.

  3. 03

    Keep unverified participants able to join

    • In the meeting options of each meeting, keep Require unverified participants to verify their info before joining set to Off.
    • If your organization uses premium email-code verification for anonymous participants, the admin must allow unverified access for these meetings, because the bot cannot receive an email code.
    • Legacy, if present: some older tenant admin centers show Require a verification check from. If you see it, set it to Not required. This may not appear in current Teams; Microsoft's former join verification check page now redirects to Manage external bots.
    • Microsoft's current PowerShell reference still documents CaptchaVerificationForMeetingJoin with the value NotRequired (CAPTCHA not required to join). If the UI control is absent, ask your Teams admin to review that setting for the applicable organizer policy.
  4. 04

    Decide how the bot gets through the lobby

    Meeting policy > Meeting join & lobby > Who can bypass the lobby

    • People in my org and guests: anonymous participants, including MeetSwift, wait in the lobby. Someone in the meeting admits MeetSwift manually. This is the controlled option and works well.
    • Everyone: anonymous participants can bypass the lobby once a verified participant has started the meeting.
    • For MeetSwift to join when no verified person is in the meeting yet, Anonymous users and dial-in callers can start a meeting must also be On.

    Everyone and anonymous start widen anonymous access to your meetings. Your admin must approve this deliberately. It is not a harmless change; if you use it, apply it through a targeted organizer policy rather than tenant-wide.

  5. 05

    Check external bot handling, if this setting is shown

    Meeting policy > Meeting join & lobby > Manage external bots and their access to meetings

    • Choosing Do not detect bots for unattended use turns off detection and approval for bots covered by that policy.
    • Alternative: keep detection on and have a meeting participant explicitly admit MeetSwift each time.
  6. 06

    Guest access is not required

    Teams admin center > Users > Guest access

    • Guest access On applies only to signed-in Microsoft guests. MeetSwift joins anonymously without a customer account, so Guest access is not a prerequisite, and neither are External collaboration settings.

Before you test

  • Policy changes can take up to 24 hours to apply.
  • Per-meeting options, meeting templates and sensitivity labels can override policy settings.
  • The policy that matters belongs to the meeting organizer, not to the attendee who connected their calendar to MeetSwift.
  • No setting guarantees lobby bypass or that MeetSwift can join every meeting.

Test it

  1. Create a new Teams meeting that you organize.
  2. In MeetSwift, connect your own Microsoft calendar.
  3. Turn on consented capture or auto-join for that meeting.
  4. Join the meeting yourself first and admit MeetSwift from the lobby if it waits there.
  5. After the meeting, confirm you can see the recording and notes in MeetSwift, not just a completed status.
  6. Once setup works, if an eligible meeting fails to capture, use Send bot again. It reuses your workspace's current consent.

Stuck on a setting? Email info@meetswift.com.