Connect Microsoft 365 with Statisfy
The Microsoft 365 integration links your Outlook mail and calendar to Statisfy through a single OAuth connection. You choose exactly which permissions to grant at connect time, and can change them later. Once connected, Statisfy can:- Sync your email threads in near real-time (when Read email is granted)
- Pull historical and ongoing Outlook calendar events (when Read calendar is granted)
- Send emails from your Outlook account via Workbench or Agent Studio components (when Send email on your behalf is granted)
Microsoft 365 is a per-user integration — each user who wants Statisfy to act on their behalf must connect their own Microsoft account. Connecting yours does not give Statisfy access to your teammates’ mail or calendar.
Permissions You Choose
When you click Connect, the dialog shows three checkboxes. Tick only what you need — at least one must be selected.Prerequisites
- A Microsoft 365 work or school account
- The Statisfy admin must have enabled the Microsoft 365 integration in your org
- A connected CRM (Salesforce or HubSpot) — non-CRM integrations are gated until at least one CRM sync has completed
- Pop-ups allowed for Statisfy in your browser (the Microsoft sign-in opens in a new window)
Steps to Connect
- Log in to Statisfy.
- Navigate to Integrations → User Apps → Microsoft 365.
- Click the Microsoft 365 card. The connect dialog appears with the three permission checkboxes.
- Tick or untick the boxes to match what you want Statisfy to do.
- Click Connect your account.
- A Microsoft sign-in window pops up. Sign in if needed, then review the requested permissions — they’ll match exactly what you checked. Click Accept.
- The pop-up closes automatically. The Microsoft 365 card will show Connected within a few seconds.
Seeing an “Approval required” screen?
If your Microsoft admin has restricted user consent for third-party apps (a common default in Microsoft 365 tenants), you’ll see a screen titled “Approval required” instead of the normal permissions prompt. It lists the permissions you selected in the connect dialog and shows a Request approval button instead of letting you accept. This is a Microsoft-side policy — not a Statisfy issue. Individual users cannot self-consent to the requested scopes; only your Microsoft 365 admin can grant them, and it needs to be done just once for the whole organization. Ask your Microsoft 365 admin to grant tenant-wide admin consent for Statisfy. Once they do, every user in your org can connect without seeing the approval prompt.Guide for the Microsoft 365 Admin (One-Time Setup)
Send this section to whoever manages your Microsoft 365 tenant.- Open the Microsoft Entra admin center and sign in with an account that has the Global Administrator, Privileged Role Administrator, or Cloud Application Administrator role.
- In the left navigation, go to Applications → Enterprise applications → All applications.
-
Search for Statisfy and open the entry whose Application ID is
0c6941a3-d913-4963-8cae-67a7e25a345f. You may see more than one result (older test apps, legacy proxy apps, etc.) — pick this specific one; grants on any other entry will not fix the approval prompt.If Statisfy does not appear in the list yet, at least one user in your org must have started the connect flow (which auto-provisions the Statisfy service principal in your tenant). If none of your users has attempted to connect, ask one to do so and refresh this page. - In the app’s left navigation, click Security → Permissions.
- Click Grant admin consent for [your organization].
-
A Microsoft sign-in window opens. Sign in with your admin account and review the permissions Statisfy is requesting:
- Mail.Read — read the signed-in user’s mail
- Mail.Send — send mail as the signed-in user
- Calendars.Read, Calendars.ReadWrite — read and write the signed-in user’s calendar
- User.Read — sign in and read the user’s basic profile
- openid, profile, email, offline_access — standard sign-in scopes
- Click Accept.
This grant is a one-time, org-wide operation. Statisfy still acts strictly on behalf of each individual user who chooses to connect — it does not read anyone’s mail or calendar until that user completes their own connect flow and picks the permissions they want.