Microsoft Azure App Setup

Before you begin

• A Microsoft account or an Azure account (a free account at azure.microsoft.com is sufficient)
• A domain with HTTPS configured
• Tymeslot installed and running at your domain

By the end of this guide, one Azure app registration serves both Outlook Calendar sync and Teams meeting creation.

1 Register an App in Azure

1. Go to entra.microsoft.com and sign in. (You can also reach the same app registrations from portal.azure.com through [Microsoft Entra ID] in the left sidebar.)
2. Go to [Applications] → [App registrations] in the left sidebar.
3. Click [+ New registration].
4. Fill in the registration form:
   • • Name: "Tymeslot"
   • • Supported account types: select Accounts in any organizational directory and personal Microsoft accounts. This lets both personal Outlook.com accounts and work or school Microsoft 365 accounts connect.
   • • Redirect URI: choose Web from the platform dropdown, then enter https://yourdomain.com/auth/outlook/calendar/callback For Teams meeting creation, add a second Web redirect URI after registration (under [Authentication]): https://yourdomain.com/auth/teams/video/callback
5. Click [Register]. You land on the app's Overview page.

2 Note Your Application ID

The Overview page opens straight after registration. Find these two values:

• Application (client) ID: copy it; this is your OUTLOOK_CLIENT_ID.
• Directory (tenant) ID: you do not set it anywhere. Tymeslot always uses Microsoft's common endpoint so both personal and organisational accounts can connect, and you cannot restrict it to a single directory.

3 Create a Client Secret

In the left sidebar of your app registration, go to [Certificates & secrets] → [New client secret].

1. Description: "Tymeslot production", so you can identify it later
2. Expires: 24 months is a reasonable choice. Set a reminder to replace it before it expires: once it does, every Outlook and Teams connection stops working
3. Click [Add]. A new row appears in the secrets list.
4. Copy the value from the Value column immediately. This is your OUTLOOK_CLIENT_SECRET.

4 Add API Permissions

Go to [API permissions] → [Add a permission] → [Microsoft Graph] → [Delegated permissions]. Search for and add each of these:

• User.Read

  Identifies the connected account during the calendar and Teams OAuth flow: Tymeslot reads the account's name and email to label the integration.

• Calendars.ReadWrite

  Required for Outlook Calendar sync: reads existing events to check availability and creates events for new bookings. It also covers Microsoft Teams, because Tymeslot creates a Teams meeting as a calendar event with online meeting turned on.

After adding all permissions, click [Grant admin consent for (your org name)] if you have admin rights. A green tick next to each permission confirms consent.

5 Configure Environment Variables

Add the following to your Tymeslot environment and restart it.

# OAuth credentials (from Steps 2 and 3)
OUTLOOK_CLIENT_ID=your-application-client-id
OUTLOOK_CLIENT_SECRET=your-client-secret-value

# Random secret used to sign the OAuth state parameter
OUTLOOK_STATE_SECRET=your-random-32-char-secret

Generate a secure state secret with:

openssl rand -hex 32

Common Errors

❓ Frequently Asked Questions

Verification Checklist

• An Outlook Calendar connection option is visible under Dashboard → Integrations.
• Clicking Connect on it opens Microsoft's sign-in page, then returns to Tymeslot without an error.
• If using Teams: a Microsoft Teams option is visible in the video section of the same page, and a test booking produces a Teams link.