Do I need to create an Azure app registration?

No. Scopable uses a shared Microsoft-verified multi-tenant app. A Microsoft 365 Global Administrator approves consent, and Scopable stores the authorization.

What Microsoft 365 data does Scopable pull?

Scopable discovers managed customer tenants through Partner Center, syncs users, reads MFA status where permissions allow, and syncs license assignments.

Why does tenant mapping matter?

Tenant mapping tells Scopable which Microsoft 365 tenant belongs to which client. Unmapped tenants can still sync, but the data cannot land cleanly under the client record until it is mapped.

Why can MFA status show as unavailable?

MFA detail depends on delegated permissions, consent, and Microsoft licensing. Check GDAP roles such as User Administrator and Reports Reader before trusting the signal.

Is this the same as the Azure / Partner Center integration?

No. This page covers Microsoft 365 customer tenants, users, MFA status, and licenses. Azure / Partner Center setup is separate and focuses on CSP customers, subscriptions, spend, and resources.

Live Microsoft integration

Microsoft 365 integration for MSP tenant data.

Scopable connects to Microsoft 365 so managed customer tenants, users, MFA status, and license assignments can support assessments, QBRs, GRC evidence, and quote planning.

Built for MSP owners, vCIOs, compliance leads, and technical reviewers who need to know which Microsoft signals Scopable reads before using tenant data in client-facing work.

Start free trial See pricing

Exact supported scope

What the Microsoft 365 integration actually does.

This is the commercial view of the tenant-level Microsoft 365 sync. The setup guide remains the source for consent, GDAP, tenant mapping, sync controls, and troubleshooting.

Records Scopable reads

Managed customer tenants, users, MFA status where permissions allow, and license assignments from Microsoft 365.

Tenant mapping

Admins map discovered Microsoft 365 tenants to Scopable clients so user and license data lands under the right account.

No app registration

A Global Administrator grants consent to Scopable's shared Microsoft-verified multi-tenant application.

Sync behavior

Admins can trigger sync, refresh status, review connected customers, and use tenant mapping to clean up unmapped data.

Product state checked 2026-07-22. Knowledge Base source last updated 2026-06-22. Anything broader should be treated as unverified until it appears in the setup guide or product release notes.

Data-flow proof

From delegated tenant access to client-ready evidence.

The flow below uses the public setup guide and product source as its source. It shows the data movement without inventing a customer tenant or screenshot.

Step 1

Confirm permissions

Use a Scopable admin and a Microsoft 365 Global Administrator with the right GDAP relationships.

Step 2

Grant consent

Click Connect M365, approve the Microsoft consent screen, and return to Scopable.

Step 3

Discover customers

Scopable uses Partner Center relationships to discover managed customer tenants.

Step 4

Map tenants

Map each Microsoft 365 tenant to the matching Scopable client, using suggested matches or bulk mapping.

Step 5

Sync and inspect

Trigger sync, review customer status, and check users, MFA status, and license data before using it in client work.

Limits

Microsoft data is useful only when the permissions are real.

The Microsoft 365 tab is rollout-gated. If it is not visible, the account has not been enabled yet.

A non-admin cannot approve the Microsoft consent screen. A Global Administrator is required.

MFA status depends on GDAP, consent, and Microsoft licensing. Some customer tenants can show unavailable data.

Unmapped tenants still sync, but they cannot support clean client-level workflows until they are mapped.

Azure / Partner Center cost and resource data is a separate setup path from this Microsoft 365 tenant sync.

Personal mailbox, calendar, and Teams meeting sync is a separate user-level feature, not this tenant-level integration.

Security review

What the technical validator should check.

The integration depends on Microsoft consent, delegated relationships, and tenant mapping. The right question is not whether the logo connects. It is whether the exact customer data is readable.

Confirm the consenting Microsoft account is the intended Global Administrator.
Check GDAP roles, especially Global Reader, User Administrator, and Reports Reader.
Map customer tenants before relying on client-level evidence or license reports.
Review sync errors before using MFA or license data in a client-facing assessment.
Understand that disconnecting removes synced users, licenses, mappings, and stored authorization.

Buying path

Keep Microsoft scope separate from setup work.

Use this page to decide whether Microsoft 365 data belongs in the buyer workflow. Use the Knowledge Base when the admin is ready to grant consent and map tenants.

Microsoft 365 setup guide

Use this for consent, GDAP requirements, tenant mapping, sync controls, and troubleshooting.

Read the setup guide

Azure / Partner Center setup

Use this when the buyer needs CSP customers, subscriptions, spend, and Azure resource context.

Read the Azure guide

MSP assessment software

Use this when Microsoft 365 evidence needs to support gap review and project scope.

See assessment workflow

MSP GRC software

Use this when Microsoft 365 signals need to support framework evidence and compliance review.

See GRC workflow

Microsoft 365 questions

Test Microsoft 365 with one mapped customer.

The trial should prove whether user, MFA, and license data help the MSP make better assessment, roadmap, compliance, and quoting decisions.

Start free trial See pricing