Email & CRMOAuth 2.0 — Application (client) ID + Client secretConfirm pricing before publishing
Microsoft 365 Calendar
Book demos and sales calls on Outlook calendars with Teams links and free/busy checks.
AProvider definition
- Provider
- Microsoft 365 Calendar
- What it does
- Book demos and sales calls on your team's Outlook calendars with Teams links and free/busy checks.
- Why we need it
- Book demos and sales calls on Outlook calendars with Teams links and free/busy checks.
- Used in
- CRM booking page · AI Calling appointments
BAccount requirements
- Account type
- Microsoft Entra ID app registration
- Prerequisites
- Microsoft 365 work account (Teams links need Teams licences)
- Verification
- Admin consent may be required by your tenant's policy.
CConnection method
- Authentication
- OAuth 2.0 — Application (client) ID + Client secret
- Where to enter it
- Your workspace: App → Integrations → Providers & API keysWorkspace owner or admin. Keys added here are used only by your workspace (AI keys here don't use plan credits).
- Each salesperson: App → CRM → CRM settings → Calendar & bookingEvery salesperson connects their own calendar.
Setup steps
- 1entra.microsoft.com → App registrations → New registration; supported account types as needed (tenant “common” allows any work account).
- 2Authentication → Add platform → Web: add the redirect URI below.
- 3Certificates & secrets → New client secret; copy the value.
- 4API permissions → Microsoft Graph delegated: Calendars.ReadWrite, User.Read, offline_access, openid, email.
- 5Enter the client ID, secret and tenant; each salesperson connects in CRM → CRM settings → Calendar & booking.
DPermissions & API scopes
| Scope / permission | Why it's needed | Requested by |
|---|---|---|
| offline_access | Stay connected (refresh token). | Calendar booking |
| openid | Sign in. | Calendar booking |
| Identify the account. | Calendar booking | |
| User.Read | Read the user's profile. | Calendar booking |
| Calendars.ReadWrite | Check availability and create/cancel booked meetings with Teams links. | Calendar booking |
This list is generated from the scopes the application's code requests.
EFree vs paid
- Free account / free API access
- Yes — no fee for Microsoft Graph calendar access.
- Card or billing account required?
- No.
- Paid plan / costs
- Microsoft 365 licences for the users.
- Quota and usage limits
- Microsoft Graph throttling limits.
Not yet verified. Confirm on the provider's official pricing page before publishing.
FSetup screenshots
Capture each step with real values masked. Save images as public/docs/integrations/microsoft/1.png … 10.png and they appear here automatically.
- Screenshot to add1. Account login / creationThe provider's sign-in or sign-up page.
- Screenshot to add2. Developer consoleThe developer console or dashboard home.
- Screenshot to add3. Project / app creationCreating the app or project used for this integration.
- Screenshot to add4. API enablementThe API or product enabled for the project.
- Screenshot to add5. OAuth configurationConsent screen / OAuth settings with the redirect URIs.
- Screenshot to add6. API key / credentials creationCreating the key, secret or token (mask the value).
- Screenshot to add7. Permissions / scopesThe scopes or permissions requested or approved.
- Screenshot to add8. Billing / quota settingsBilling, credits or quota page.
- Screenshot to add9. Application connectionThe provider card in our application with fields filled (secrets masked).
- Screenshot to add10. Successful connectionThe green Test result or the connected account listed.
GApplication configuration
Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.
| Field | Required | Example / default | Notes |
|---|---|---|---|
| Application (client) ID | Yes | — | |
| Client secret | Yes | •••••••• | Stored encrypted; shown masked after saving. |
| Tenant | Optional | common |
Paste these into the provider's console
- Redirect URI (Web)
https://api.socialmati.com/api/oauth/calendar/microsoft/callback
HTesting
- 1Connect a calendar and book a slot on the booking page — the event appears in Outlook with a Teams link.
ITroubleshooting
| Problem | What to do |
|---|---|
| Invalid credentials | Check the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure. |
| Missing permissions | Reconnect and accept every permission on the consent screen. If a permission is missing from the list, add it to the app (and get it approved). |
| OAuth failure | Sign-in was cancelled, the app is in development/testing mode, or the user isn't allowed to use it yet. Add the user as a tester or publish the app. |
| Redirect URI mismatch | Copy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings. |
| API not enabled | Enable the API/product for the project or app in the provider console and wait a few minutes. |
| Quota exceeded | Wait for the quota window to reset (see section E) or request a higher quota / add credits. |
| Account not eligible | Check the account requirements in section B (e.g. business/professional account, verified property, registered organisation). |
| App review required | Permissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions. |
| Billing required | Add a payment method or prepaid credits on the provider account (see section E). |
JDisconnect & security
- Revoke access at the provider
- Remove the app at myapps.microsoft.com, or delete the client secret in Entra.
- Disconnect in the application
- App → Integrations → Providers & API keys or App → CRM → CRM settings → Calendar & booking → open the card → Remove / Disconnect. Connected accounts can be disconnected per brand.
- Rotate credentials
- Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
- How credentials are stored
- Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
- What data the application can access
- Free/busy and the events the app creates.

