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, you will have an Azure app registration configured for Microsoft Login, Outlook Calendar sync, and Teams meeting creation.

1 Register an App in Azure

1. Go to portal.azure.com and sign in.
2. Type App registrations in the top search bar and select it from the results. (Alternatively: [Microsoft Entra ID] → [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 allows both personal Outlook.com accounts and work or school Microsoft 365 accounts to sign in.
   • — Redirect URI: choose Web from the platform dropdown, then enter https://yourdomain.com/auth/microsoft/callback
5. Click [Register]. You land on the app's Overview page.

2 Note Your Application ID

On the Overview page immediately after registration, locate and copy two values:

• Application (client) ID — this becomes your MICROSOFT_CLIENT_ID.
• Directory (tenant) ID — when supporting both personal and organizational accounts, set MICROSOFT_TENANT_ID=common in your environment. You only use the actual tenant ID if you are restricting login to a single Azure AD 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" (helps identify it later)
2. Expires: 24 months is a reasonable choice — set a calendar reminder to rotate it before it expires
3. Click [Add]. A new row appears in the secrets list.
4. Copy the value from the Value column immediately. This is your MICROSOFT_CLIENT_SECRET.

4 Add API Permissions

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

• User.Read

  Required for Microsoft Login — reads the signed-in user's name, email, and profile photo.

• Calendars.ReadWrite

  Required for Outlook Calendar sync — reads existing events to check availability and creates events for new bookings.

• OnlineMeetings.ReadWrite

  Required for Teams meeting creation. Only add this if you plan to use Teams rooms — skip it if you only need login or calendar sync.

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

5 Configure Environment Variables

Add the following to your Tymeslot environment configuration and restart the server.

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

# Use "common" to support both personal and organizational accounts
MICROSOFT_TENANT_ID=common

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

Generate a secure state secret with:

openssl rand -hex 32

Common Errors

❓ Frequently Asked Questions

Verification Checklist

• A Sign in with Microsoft button appears on the login page.
• Clicking it redirects to Microsoft's login, then back to Tymeslot without error.
• An Outlook Calendar connection option is visible under Dashboard → Settings → Integrations.
• If using Teams: a Microsoft Teams option is visible under the Video integrations section, and creating a test booking produces a Teams link.