Connecting your Microsoft 365 tenant
Consent, the Global Administrator sign-in and the Exchange connector, explained step by step.
8 minute readUpdated 6 November 2026
On this page (7)
Before you start
You need a Global Administrator of the tenant for about five minutes. If that is not you, invite them to the workspace from Access rights, or sit with them for the consent step; they do not need an account to grant consent, only to click the button while you are signed in.
The service reads directory data (names, titles, phone numbers, photos) and manages its own transport connector and mail flow rules. It never asks for permission to read mailboxes, and it never sees anyone’s password.
Step 1: Admin consent
From the Connect page press "Connect a tenant". Microsoft shows the permissions being requested; the Global Administrator accepts on behalf of the organisation. If the account signing in is not a Global Administrator, Microsoft refuses and you can try again with the right account.
Step 2: Prove you manage it
Straight after consent, Microsoft asks the same admin to sign in again. This confirms the person connecting the tenant is actually one of its Global Administrators, which is what stops someone attaching a tenant they do not control. The workspace then shows "Connected" with the tenant’s name and primary domain.
Common messages on this step: "wrong tenant" means the account signed in belongs to a different tenant than the one consented for; "not an admin" means the account is not a Global Administrator, or consent is still propagating, so wait a minute and try again.
Step 3: Sync the directory
On the Microsoft 365 page press "Sync users", then "Sync groups". The relay only signs mail from senders it knows, so until the first sync nothing is signed. Syncs run again on a schedule, and you can press the buttons any time after changing someone’s details in Microsoft 365.
Step 4: Connect Exchange
Press "Connect Exchange" and sign in once more as the Global Administrator. The service creates, in your tenant, an outbound connector to the relay, an inbound connector that accepts the mail back, and a transport rule that sends your users’ outgoing mail through them. Nothing else in your mail flow changes, and the rule is skipped for messages that have already been processed, so mail can never be signed twice.
If your organisation prefers to make Exchange changes itself, choose "Connect manually instead", which gives you a PowerShell script that does the same thing, plus a removal script for later.
Checking everything is healthy
The Exchange connection card runs a health check that confirms the connectors and rule exist and are enabled, and the "Signing readiness" list flags anything on the service side that would stop mail being signed: no users synced, no active rule, no seats bought. When both are green, send yourself a test from your own mailbox.
Disconnecting
Removing the Exchange connection from the Microsoft 365 page (or running the removal script) stops mail being routed through the relay immediately; mail flows as it did before. Revoking the app’s consent in the Microsoft 365 admin centre does the same for directory access. Deleting the workspace does both and removes all its data.