Microsoft 365 connector
Microsoft 365 + AI Autopilot
Microsoft 365 is the productivity and identity estate most MSP clients live in; the Graph API is the surface for users, groups, mail, licences and policy.
528 tools · by domain
Microsoft 365- Identity & Access203
- Automation, Patch & Remote80
- Documentation & Secrets44
- Clients & Contacts42
- Platform Admin & Integrations31
Modeled connector coverage, not completed executions.
StackJack connector catalogue
The operating model lists StackJack connector coverage. Tenant access is scoped and authorised per MSP; a catalogue entry does not establish a working launch workflow.
Modeled connector coverage
528 catalogued tools for Microsoft 365
Tenants, identities, licences, mailboxes and policies across the Microsoft 365 estate, through Graph or CIPP. 283 read · 245 write.
- Identity & Access203 tools
- Automation, Patch & Remote80 tools
- Documentation & Secrets44 tools
- Clients & Contacts42 tools
- Platform Admin & Integrations31 tools
- Contracts, Billing & Finance23 tools
- Projects, Time & Scheduling21 tools
- Analytics & Intelligence21 tools
Counts from The Agentic MSP Operating Model, version 4.361.0, transcribed from the connector's published catalogue on 2026-09-17. These describe the connector surface, not verified tenant permissions or completed workflows.
Operating-model roles
3 of the five service-desk agent roles map to this category
This is the model's category-level mapping. It does not establish that these agents have executed against your tenant.
- Stage 1AI Client ConciergeThe model defines a client-facing stage for password-reset guidance, ticket status, guided setup and collecting the detail the service desk needs. Pilot capabilities are agreed separately.
- Stage 4AI Autonomous Remediation AgentThe model defines a resolution plan, verification steps and closure notes for each ticket type. In the launch, Claudia runs the fix only after your technician approves it.
- Stage 5AI Service Desk WatchdogThe model defines a watchdog stage for SLA monitoring, client follow-up and breach-risk alerts. These responsibilities describe the broader model; pilot capabilities are agreed separately.
Also in this category
Also in Microsoft 365 management
CIPP
The whitepaper · 10 pages · PDF
Resolution readiness: a denominator for "our AI resolves X% of tickets"
Every vendor claims a resolution rate. This is what a denominator for one looks like.
Questions
Planning a Microsoft 365 connection
Does this listing confirm a working integration?
No. It describes Microsoft 365's connector surface in the operating model. Tenant access, the selected task, result retrieval and any PSA linkage must be reviewed and demonstrated separately.
What access does AI Autopilot need to Microsoft 365?
That depends on the task and tenant. Before a pilot, review the available StackJack connection, execution identity, permissions, authorised targets and how access will be withdrawn. This page does not prescribe a permission set or confirm your current configuration. The initial launch is supervised.
Does onboarding guarantee this connector or workflow is ready?
No. The published onboarding session describes the service offered, not proof that a particular tenant connection or workflow has passed validation. Agree the stack, prerequisites and intended task with the team before treating it as ready.
Request an integration
Running something else as well?
Tell us the rest of your stack and the task you want to explore so we can review scope and access with you.
Discuss your Microsoft 365 workflow
Claudia is invite-only for a limited supervised launch.