StackOSWork, organized
LibraryWorkflowsAgentsOrchestratorsIntegrationsArticles

Microsoft Graph mail send and calendar event provider contract.

2 listed actions1 capability groups

Connection facts

What the Microsoft 365 connector actually exposes.

These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.

Connection method
OAuth connection
Setup
Register a confidential web app in Microsoft Entra ID with the fixed StackOS callback and delegated Mail.Send, Calendars.ReadWrite, and offline_access permissions, then use Connect with Microsoft.
Capability groups
Outbound Operations
Action boundaries
2 write actions

Action catalog

Actions listed for Microsoft 365.

Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.

2 matching actions

Outbound OperationsCan make changes

Create Microsoft Graph Calendar Event

Create an approved Microsoft Graph calendar event from explicit event input and safe refs.

Outbound OperationsCan make changes

Send Microsoft Graph Mail

Submit an approved Microsoft Graph mail send from explicit mail input and safe refs.

Direct answer

How does the Microsoft 365 integration work?

People continue using Microsoft 365 as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

  1. 01Your requestStart in your AI
  2. 02StackOS planExpands the steps
  3. 03Microsoft 365Does its bounded part
  4. 04Checked resultKeeps the proof

More from GTM And RevOps

Related integrations.

See the plugin →

Common questions

Microsoft 365 and StackOS.

What can the Microsoft 365 integration do in StackOS?

The current catalog includes 2 Microsoft 365 actions across Outbound Operations. The exact actions used depend on the workflow and approval rules.

Does StackOS replace Microsoft 365?

No. Microsoft 365 remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.