Microsoft 365
Microsoft 365 (via Graph) integration
Use Microsoft 365 (via Graph)? Connect it to MSProspector to find upsell revenue in your clients. Built for MSPs who want more leads, marketing and sales.
Reads each client's Microsoft 365 licenses — bought versus assigned — and, where allowed, who has set up MFA. Account addresses are checked against public breach data (Have I Been Pwned) and never stored; only counts are kept. Never mail or files, and nothing that can make changes.
Setup steps are for connected customers — sign in to read them.
What we find in Microsoft 365 (via Graph)
License waste (purchased vs assigned).
Every finding lands on your Client Upsell board as a named client with a number beside it — not a report you have to read.
What the Microsoft 365 (via Graph) connection does
Read — powers Client Upsell
Read your clients' stack
Licenses purchased versus assigned, and MFA registration where consented.
Permissions to prepare with your administrator
Required permissions and account access
- Application permissions: Organization.Read.All, AuditLog.Read.All and Policy.Read.All.
- Optional Microsoft 365 usage/adoption reports: Reports.Read.All.
- CSP/GDAP discovery: DelegatedAdminRelationship.Read.All.
- Device findings: DeviceManagementManagedDevices.Read.All (Microsoft Graph) and Machine.Read.All under WindowsDefenderATP, not under Graph.
- AI application and outside-administrator findings: Directory.Read.All. All listed permissions read data; no Mail, Files, Send, user-write or device-action rights are needed.
Which accounts and records: Use a multitenant application and grant admin consent in every client tenant. Adding a permission requires consent again in each tenant. Enter the intended tenant IDs or use the partner relationship. MFA assessment also requires Entra ID P1/P2; Defender/Intune assessment requires the corresponding service/license. A tenant that has not consented remains unassessed, not healthy. Record secret expiry.
A green credential check proves access to the records tested. Confirm the expected data after the first pull; missing permissions or tenant consent must remain visible.
Read-only
We only ever read — we never change anything in Microsoft 365 (via Graph)
You make a view-only key using our setup steps. Our connection has no code that can write to Microsoft 365 (via Graph), and your key is encrypted and only used to read.
Microsoft 365 (via Graph) integration — common questions
- How does the Microsoft 365 (via Graph) integration help my MSP get more leads and sales?
- Client Upsell reads Microsoft 365 (via Graph) view-only and turns what it finds into upsell opportunities: each one a named client with a number beside it, ready for your account managers to sell.
- What does the Microsoft 365 (via Graph) integration read?
- Reads each client's Microsoft 365 licenses — bought versus assigned — and, where allowed, who has set up MFA. Account addresses are checked against public breach data (Have I Been Pwned) and never stored; only counts are kept. Never mail or files, and nothing that can make changes.
- What does MSProspector find in Microsoft 365 (via Graph)?
- License waste (purchased vs assigned).
- Is the Microsoft 365 (via Graph) connection read-only?
- Yes. We only ever read from Microsoft 365 (via Graph) — our Microsoft 365 (via Graph) connection has no code that can change anything, and an automated check on every change to our code blocks any that could. Please create a view-only key using the setup steps, so the key itself can't make changes either.
