Microsoft 365 · Graph

Microsoft 365 integration in your own system

Microsoft 365 integration means your app talks to your customers’ tenant via Microsoft Graph: identity, Outlook, OneDrive, SharePoint, Teams — with the scopes you actually need. It is the right door when the company already lives in 365. Then you should not build a new file archive and a new calendar. You should build the case, and let 365 be file and meeting. Scopes are the product. User.Read is not the same as Mail.ReadWrite and Files.ReadWrite.All. Each permission must be explainable to an IT owner. “We took tenant-wide admin consent to be safe” is how projects die in security review. In B2B products, admin onboarding is the integration for many customers.

11 min read · Updated 28 August 2026

Sub-pages when you only need one piece: Outlook, Teams, SharePoint, OneDrive. If you live in Google instead, that is Google Workspace. Automation on top of what you already pay for.

Scopes are the product

Each permission is a sentence you must be able to say out loud in a security meeting. If you cannot, the scope does not belong in version 1.

Graph · scopes
User.Readok
Calendars.ReadWriteok
Files.ReadWrite.Allforklar
Files.ReadWrite.All is not a default. It is an argument.

Scopes that typically hold

  • User.Read for “who are you”
  • Calendars.ReadWrite when you book on behalf of the user
  • Sites.Selected instead of the whole tenant

Scopes that kill review

  • Mail.ReadWrite “because we might need it”
  • Files.ReadWrite.All on the whole tenant
  • Tenant-wide admin consent without onboarding
Least possible. Explainable.

Admin consent is onboarding

1

App registration

Single-tenant if the app is only for you. Multi if the product must enter customers’ 365.

2

Consent

A tenant admin approves the scopes you wrote down.

3

First case

Create a meeting, put a file, post in Teams — one flow, not every Graph endpoint.

For many B2B customers this is the integration

What to do now

Write the three actions the case should trigger in 365 — meeting, file, message. Not “full Graph”. Then we can price the scopes. Packages.

FAQ about Microsoft 365 integration

Single tenant or multi-tenant app?
Single if the app is only for you. Multi if your product must enter customers’ 365. That choice must be made before the first login screen.
Must IT approve the app?
In B2B typically yes. Build that onboarding. It is the integration for many customers — not the API call.
Can we take Files.ReadWrite.All “to be safe”?
No. That is how projects die in security review. Sites.Selected or one library.
Is Graph one project or five?
One hub, several sub-pages. Outlook, Teams, SharePoint and OneDrive are each their own scope conversation.
What if the customer is on Google?
Then you build Workspace, not 365. Two stacks in the same SME is a project you should talk them out of.

Also read

Outlook · calendar and mail

Outlook integration: calendar and mail in your app

→

Teams · notifications

Microsoft Teams integration

→

SharePoint · files

SharePoint integration: files and steering groups

→

Want us to build it for you?

You get a fixed-price proposal within 24 hours.

Graph with the scopes you can explain
Dennis Nielsen

Dennis Nielsen

Head of Operations, Ceptiv

Free consultation

One free hour of advice before you start.

Describe your project and I will contact you as soon as possible, so we can schedule a no-obligation meeting. You leave with practical advice on how to get your project off to a good start.

  • Free
  • 1 hour
  • No obligation
Describe your project

Or call us on +45 81 98 32 71