Skip to main content
Microsoft Graph connects your organization’s Microsoft 365 data to Airia agents, covering mail, calendar, contacts, files, OneNote, tasks, Teams, and more.
Microsoft Graph shows up as two separate servers in the Airia catalogue: Microsoft Graph and Microsoft Graph (BYO). They’re not the same connection with two names. Each is added to a Gateway or Deployment on its own, and which one you pick changes both how setup works and which tools an agent can actually use. Read the comparison below before adding either one.

Two Ways to Connect

If you’re not sure which to pick, start with Microsoft Graph. You can add Microsoft Graph (BYO) later if you run into a tool that needs a permission Quick Connect doesn’t grant. Each tool’s required permission is called out in the tool reference below.

What It Can Do

Connecting

Microsoft Graph (Quick Connect)

This is the server that uses Airia’s own Microsoft app registration, so there’s no Azure setup on your end.
1

Add Microsoft Graph

Find Microsoft Graph in the server catalogue when building an MCP Deployment or MCP Gateway, or add it from Server Management.
2

Sign in

Click Connect and sign in with your Microsoft account when prompted. You’ll be asked to authorize the permissions listed under Quick Connect permissions below.
A few of the requested permissions, like reading SharePoint sites, require a Microsoft 365 administrator to approve them for the whole organization before any individual can authorize them. If sign in fails with an error mentioning “need admin approval,” ask your admin to consent on your organization’s behalf, or use Microsoft Graph (BYO) instead.
Quick Connect is always a personal connection, tied to the Microsoft account you sign in with. See Tenant vs. Personal Level App Credentials for what that means for your organization.

Microsoft Graph (BYO)

This is the server that uses your own Azure app registration. You decide exactly which permissions to grant. Pick this one if you want to restrict sign in to your own organization, limit which Microsoft 365 data agents can touch, or use tools that Quick Connect doesn’t cover.
1

Register an app

Go to Azure Entra ID app registrations and click New registration.
2

Choose account types and set the redirect URI

Give the app a name and choose which accounts can sign in (see Account Types below, single tenant is recommended for most organizations). Under Redirect URI, select Web and enter:
Then click Register.
3

Add API permissions

Go to API permissionsAdd a permissionMicrosoft GraphDelegated permissions and add the permissions you need. See Tools and Required Permissions below to decide which ones, or use the full coverage list to make every tool available at once.
4

Grant admin consent

Still on the API permissions page, click Grant admin consent for [your organization]. This is required for any permission ending in .All, or the connection will fail for anyone who isn’t an admin.
5

Create a client secret

Go to Certificates & secretsNew client secret and copy the Value immediately. Azure only shows it once.
6

Copy your IDs

From the app’s Overview page, copy the Application (client) ID and, if you chose single tenant, the Directory (tenant) ID.
7

Add it to Airia

Add Microsoft Graph (BYO) as a server on a Gateway or Deployment, then enter your Client ID, Client Secret, and Tenant value. Complete the sign in flow to finish connecting.
Because BYO uses an app registration you control, the Client ID and Client Secret can be shared at the Tenant level so this setup only happens once for your organization. Each person who connects still signs in with their own Microsoft account. See Tenant vs. Personal Level App Credentials for more on how that works.

Account Types

Azure offers four options when you register the app, and each one expects a different Tenant value in Airia: Single tenant is recommended if you want to restrict sign in to people in your own organization.

Tools and Required Permissions

Every tool below needs a specific Microsoft Graph permission before it will work. Tool names are what an agent actually calls, the same names you’d see in an agent’s tool call log. The Works with column tells you whether the required permission is already included in Quick Connect’s fixed set, or whether you need Microsoft Graph (BYO) with that permission added.
Most tools accept more than one permission, listed with or. Any one of them is enough, and broader permissions (ending in .All or .Shared) work just as well as the narrower one. A few tools, called out with and, need every listed permission granted at the same time. If a permission ends in .All, granting it through Bring Your Own also requires the admin consent step covered above.

Mail

Calendar

Contacts

Files (OneDrive)

SharePoint

Excel

OneNote

Tasks (To Do)

Reading tasks and lists works on both servers. Creating, updating, or deleting a task or list needs all three Tasks.ReadWrite permissions granted together, which currently only Microsoft Graph (BYO) can provide.

Teams and Chat

People and Directory

Rooms and Places

Identity and Presence

Quick Connect Permissions

Quick Connect always requests this fixed set of permissions:

Granting Every Permission

If you want Microsoft Graph (BYO) to have access to every tool listed above, add all of the following delegated permissions to your app registration, then grant admin consent:
Always include openid and offline_access. Without offline_access, Airia can’t refresh the connection once the access token expires (about an hour), and users will have to reconnect constantly.

Extending Beyond Your Own Data

By default, every tool acts on the signed-in user’s own mailbox, calendar, files, and so on. Several tools accept a parameter to act on another user’s data instead, for delegate, shared mailbox, or admin scenarios. That only works if you grant the broader version of the permission on your Bring Your Own app: Any permission ending in .All and many .Shared variants require tenant admin consent before individual users can grant them. Without it, the OAuth flow surfaces AADSTS65001 "need admin approval". Two ways to grant admin consent:
  1. From the app’s API permissions page, click Grant admin consent for [tenant] (one-time, organization-wide).
  2. Have a tenant admin navigate to this URL after replacing the placeholder values:

Troubleshooting

This means one of the requested permissions needs tenant admin consent. For Quick Connect, ask a Microsoft 365 admin to approve the connection for your organization, or switch to Bring Your Own. For BYO, go back to your app’s API permissions page and click Grant admin consent.
Some categories, like Teams chat, meeting transcripts, and room booking, aren’t included in Quick Connect’s fixed permission set. Check the tool reference above. If a tool is marked BYO only, switch to Microsoft Graph (BYO) and add the listed permission.
This happens when offline_access wasn’t included in the granted permissions, so Airia has no way to refresh the session. For BYO, add offline_access to your app’s permissions, grant consent again, and reconnect.
The signed in account is missing the underlying permission for that action. Check the tool reference above for the exact permission the tool needs. For BYO, add it to your app registration, grant admin consent if it’s a .All or .Shared permission, and have users reconnect.

Learn More