Microsoft Teams Integration

Prerequisites

• A Microsoft Azure app configured with OUTLOOK_CLIENT_ID and OUTLOOK_CLIENT_SECRET (see the Microsoft Azure App Setup guide)
• The Microsoft Graph permissions Tymeslot requests when you connect Teams, all delegated: Calendars.ReadWrite and User.Read , plus offline_access so the connection keeps working without you signing in again. The only other scopes are the standard sign-in ones, openid, profile and email
• A Microsoft account that can host a Teams meeting. Tymeslot asks Microsoft to attach a Teams meeting to every booking; an account that cannot host meetings still takes bookings, but without a join link

How It Works

When a booking is confirmed, Tymeslot creates a calendar event on the connected Microsoft account (POST /me/events) with isOnlineMeeting turned on. Microsoft attaches a Teams meeting to that event and returns its join URL, which Tymeslot stores and includes in the booking confirmation email and in the meeting detail view. For a work or school account, Tymeslot names teamsForBusiness as the meeting provider; for a personal Microsoft account it leaves the provider unset and takes whatever Microsoft attaches.

The Teams meeting is that calendar event, so the meeting also appears in the connected account's own calendar. If your bookings go to an Outlook calendar on the same Microsoft account, Tymeslot turns the Teams meeting on for the booking's own event instead, so your calendar holds one entry per booking rather than two. If Microsoft creates an event but attaches no Teams meeting, which is what happens when the account cannot host one, Tymeslot deletes that event again rather than leaving an empty placeholder behind. The booking itself is unaffected: it stays confirmed, and the confirmation email goes out without a join link.

1 Check Whether Your Tenant Requires Admin Consent

Every permission Tymeslot requests can be granted by the person signing in, so in most tenants no administrator is involved: you approve them on Microsoft's consent screen in step 2. Consent becomes an administrator's job only where the organisation has turned off user consent for third-party apps, and you will know because sign-in stops on a "Need admin approval" screen.

If that happens, your IT administrator grants consent once, for everyone:

1. Sign into the Azure portal as an administrator
2. Go to App registrations → your Tymeslot app
3. Click API permissions in the left sidebar
4. Confirm Calendars.ReadWrite and User.Read are listed as Delegated permissions
5. Click Grant admin consent for [your organisation] at the top of the permissions list. A green tick appears next to each permission

2 Connect Microsoft Teams in Tymeslot

Microsoft Teams is connected as a video integration of its own, separate from any Outlook Calendar connection:

1. Go to Dashboard → Integrations → Video.
2. Click Connect a video provider and choose Microsoft Teams under Hosted services.
3. Sign in with the Microsoft account that should host the meetings.
4. Review and approve the permissions Microsoft lists: access to your calendars, your basic profile, and staying signed in.

Expected result: Microsoft Teams appears in your list of video integrations, showing your Microsoft account.

3 Enable Teams on a Meeting Type

Microsoft Teams is enabled per meeting type. Repeat for each meeting type where you want automatic Teams meetings:

1. Go to Dashboard → Meeting Types and pick a meeting type.
2. On the Location & Calendar tab, click Add location, or Edit on an existing one, and set Type to Video call.
3. Under Video providers, tick your Microsoft Teams integration.
4. Click Save location.

Expected result: new bookings that use this location have a Teams meeting created automatically on confirmation.

You can tick several providers on the same location, for example Microsoft Teams alongside Google Meet or Zoom. The person booking then chooses which one the room is created on. See Meeting Locations for everything a meeting type's locations can do.

Attendee Experience

The booking confirmation email sent to attendees contains:

• A Teams join link, which opens the Teams meeting lobby in the browser or the Teams desktop app

Tymeslot keeps the join link Microsoft returns for the event and nothing else, so the email carries no dial-in number and no conference ID. Anyone who needs to dial in can open the meeting in Teams, which shows whatever dial-in details the hosting account has.

Troubleshooting

❓ Frequently Asked Questions

Verification Checklist

• On Dashboard → Meetings, the booking shows a Join meeting button that links to the Teams meeting
• The booking confirmation email contains the same Teams join link
• Opening the join URL in a browser loads the Teams meeting lobby