Revogent connects to Microsoft 365 to send and sync email from your reps' own work mailboxes, keep calendars in two-way sync, and attach Teams meeting links to meetings booked through the platform. This page is written for the IT administrators and security teams who review that access.
The short version: Revogent is a multi-tenant Microsoft Entra application using delegated permissions only. It can only ever act as the individual user who signed in, you do not register anything in your tenant, and you can restrict exactly which users are able to grant it access.
How the connection works
Each user connects their own account through the standard OAuth 2.0 authorization code flow against Microsoft Entra ID: they click Connect in Revogent, sign in with Microsoft, review the requested permissions, and consent.
- No app registration is required in your tenant. Revogent is registered once as a multi-tenant application. After the first user connects, a service principal for Revogent appears under Enterprise applications in your Entra admin center, where you can manage it like any other application.
- Authorization codes are exchanged server-side with CSRF-protected state validation. Tokens are never exposed to the browser.
- All Microsoft Graph calls are made server-side. There is no client-side or add-in access to mailboxes.
Permissions requested (all delegated)
Revogent requests the following Microsoft Graph delegated scopes. Delegated means the application can only act as the specific signed-in user who granted consent, never tenant-wide. The standard integration requests no application permissions.
| Scope | What it allows | Why Revogent needs it |
|---|---|---|
| offline_access | Refresh tokens for a persistent connection | Keeps mail and calendar sync running without repeated sign-ins |
| openid | Verify the Microsoft Entra tenant that issued the credential | Binds the connection to the correct work-account tenant without requesting profile or email claims |
| User.Read | Read the signed-in user's basic profile | Identifies the connected account and displays it in settings |
| Mail.Read | Read the user's own mailbox | Syncs the user's inbox for CRM threading and reply detection |
| Mail.Send | Send mail as the signed-in user | Sends messages the user approved, from their own mailbox, into their own Sent Items |
| Calendars.ReadWrite | Read and write the user's calendar | Two-way calendar sync, scheduling, and reschedule updates |
User consent vs. admin consent
- Default: individual user consent. If your tenant allows users to consent to applications, each user grants access for their own mailbox only, at the moment they connect.
- Restricted tenants: admin consent. If your tenant restricts user consent (common in security-mature organizations), Revogent detects this during the connection attempt and presents a Microsoft v2 administrator approval link restricted to the six scopes listed above.
- What admin consent does: it authorizes the permission set for your tenant. It does not by itself connect any mailboxes. Each user must still sign in and connect their own account before Revogent can access anything of theirs.
Scoping access to specific users
If only a pilot group should be able to use Revogent, Microsoft Entra supports that natively, and we recommend configuring it during evaluations:
- Step 1: in the Microsoft Entra admin center, open Enterprise applications and select Revogent.
- Step 2: under Properties, set "Assignment required?" to Yes.
- Step 3: under Users and groups, assign the specific users or a security group who should be able to use the integration.
With assignment required, Entra refuses token issuance for anyone outside the assigned group, even if admin consent has been granted for the tenant. Conditional Access policies also apply to Revogent sign-ins the same way they apply to any other enterprise application.
Token handling
- OAuth access and refresh tokens are encrypted with AES-256-GCM before storage and decrypted only in memory at the moment of a Microsoft Graph call.
- Token access is audit-logged, refresh happens automatically, and if a refresh is rejected (for example, after revocation) the integration is marked disconnected and the user must re-authorize.
- Disconnecting an account inside Revogent deletes its stored tokens immediately.
How to revoke access
- Per user, in Revogent: Settings → Integrations → Disconnect. Stored tokens are deleted immediately and sync stops.
- Per user, in Entra: revoke the user's sessions and refresh tokens. Access ends when the current short-lived access token expires, typically within one hour.
- Tenant-wide: disable or delete the Revogent service principal under Enterprise applications. All token issuance for your tenant stops.
Teams meeting links
Revogent can attach a Teams link while creating an Outlook calendar event using Calendars.ReadWrite. The integration does not join calls or read Teams call records, recordings, or transcripts, and it requests no tenant-wide application permissions.
About Outlook add-ins
There is no Outlook or Office add-in. Nothing is deployed to your users' Outlook clients and there is nothing to manage through centralized deployment. Reps work in the Revogent web app; messages they send appear in their normal Sent Items, and replies arrive in their normal inbox.