Integrations

A Microsoft integration connects a Microsoft 365 account to Mobius so agents can read and write what that account can reach, and so Mobius records an event when something there changes.

Read this page before you connect your first Microsoft provider. All of them sign in the same way, ask the same administrator for the same approval, and behave the same way when you disconnect. The provider pages cover what each one actually does.

Provider map

Connect the provider that owns the thing the agent needs. Mail and calendar are separate connections even for the same person, because they are separate Microsoft permissions and separate change subscriptions.

One app registration, one grant per person

Mobius reaches Microsoft through a single application registered in Microsoft Entra, the directory behind a Microsoft 365 tenant. Entra records consent once per person for that whole application, not once per Mobius provider. So the first Microsoft connect a person makes is the one that asks for permission, and their later ones ride on the same grant.

Two consequences are worth knowing before you connect anything:

• Connecting a second Microsoft provider often skips straight past the consent screen. Nothing is wrong; the grant already covers it.
• Disconnecting one Microsoft integration in Mobius does not revoke that grant. It removes the stored credential and takes down that connection's change subscription, and leaves the person's other Microsoft connections working. To withdraw the authorization itself, remove Mobius from My Account > Privacy in Microsoft, or have an administrator remove it in the Entra portal.

We would rather leave the grant in place than have a calendar disconnect silently break the same person's mailbox.

Your administrator may need to approve Mobius first

Mail and calendar access is not one of the permissions a Microsoft 365 tenant hands out on an individual's say-so. In a tenant configured the default way, the first person to connect sees a message telling them to ask an administrator, and nobody can connect until an administrator approves Mobius once for the whole tenant.

That approval is a one-time step per tenant, not per provider or per person. After it, everyone connects on their own and the consent screen stops appearing.

Which account you are connecting

Microsoft always shows the account chooser, even when the browser is already signed in to a work account. Pick deliberately: the account you choose is the one every action runs as.

A Microsoft connection belongs to the person who connected it, not to the whole organization. Connecting a second account adds a second connection rather than replacing the first, and reconnecting refreshes the connection that account already has. Mobius matches on the account's Entra object ID rather than its address, so someone who changes their name, their sign-in name, or their email domain keeps the connection they had.

Change subscriptions and delivery gaps

Microsoft pushes changes to Mobius rather than making us poll for them. On connect, each provider asks Microsoft Graph for a change subscription and records where things stood at that moment.

Graph expires a subscription on a schedule of its own, and a lapsed one cannot be extended, only replaced. Mobius therefore renews each subscription with hours to spare rather than at the last moment, and checks every five minutes.

When a subscription does have to be replaced, deliveries were missed in the meantime and Graph never resends them. Mobius replays the change history from the point it recorded instead, so the missed changes still arrive as events. One pass replays only so much, and each provider page says what happens when a gap is bigger than that.

Next

• Connect Outlook for mail actions and mail events.
• Connect Outlook Calendar for meetings and free/busy.
• See how connections are owned and shared in integrations.