Identity & Productivity · 45 pre-built actions
Microsoft 365 integration with Nexus
Bring everyday productivity steps into the governed run. Many processes end with a meeting, a notification or a calendar change. Nexus includes those Microsoft 365 steps in the same workflow as the business logic, approval and audit.
Pre-built actions
What you can automate
45 pre-built Microsoft 365 actions, grouped by what they work on.
45
PRE-BUILT ACTIONS
- 01Microsoft Calendar appears in the Nexus actions library.
- 02Microsoft Teams is one of the 46 trigger sources.
Workflow
How it fits into a Nexus workflow
Microsoft Teams is a listed trigger source, so a Teams event can start a governed run. Calendar is used as an action inside the run.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Use the HTTP Request node against Microsoft APIs for operations outside the pre-built action groupss.
02
Use Rules + Code to decide timing, recipients or content before a step runs.
03
Pair with Azure trigger sources such as Azure Active Directory where the estate uses them.
Examples
Workflow examples
Onboarding follow-through
After an approved access change, a Microsoft Calendar action schedules the related session.
Chat-initiated request
A Teams event starts a run that validates the request and routes it for approval.
Change window coordination
An approved change produces calendar entries for the people involved, recorded in the run.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Multi-system workflows
Use cases that include Microsoft 365
Integration patterns
Microsoft 365 integration patterns
Dedicated patterns that pair Microsoft 365 with another system in one governed run.
Industry use cases
Processes that use Microsoft 365
Public sector
Citizen request to case resolution
Requests arriving by email become tracked cases, with technical work handed to engineering and updates sent back.
Public sector
Joiner, mover, leaver for public employees
Workforce changes become policy-checked identity changes, with collaboration set up and removed on time.
Public sector
Procurement exception handling
Procurement and invoice exceptions reach a named owner, and SAP changes happen only after approval.
Defense & national security
Privileged access change with approval
Privileged access is granted only after named approval, with every change recorded.
Defense & national security
Secure collaboration onboarding
New staff receive only the identity groups and collaboration spaces their role allows, after approval.
Financial services
Invoice approval and procurement
Invoices are checked against procurement records and approved before they are created.
Financial services
Identity changes for regulated staff
Access changes for regulated roles carry a case record, approval and full evidence.
Healthcare
Appointment administration and service follow-up
Appointment changes and service requests reach the right administrative staff and calendars.
Healthcare
Healthcare employee onboarding
New staff get the identity access and collaboration their role needs, after approval.
Healthcare
Patient service request escalation
Service requests that need operational support become tracked tickets with communication to staff.
Critical infrastructure
Operational data to analytics
Operational files load into Snowflake reliably, and teams are told when data is ready.
Enterprise
Employee lifecycle automation
Joiners, movers and leavers are handled end to end with a case record and approval.
Enterprise
Customer support escalation
Support issues reach engineering with context, and customers and account teams stay informed.
Enterprise
Marketing to sales handoff
Qualified leads reach the right salesperson fast, with duplicates caught.
Enterprise
Amazon fulfilment exception workflow
Fulfilment problems become owned ServiceNow tickets, with the owner told and the resolution recorded.
Financial services
Expense and budget governance
Budget changes are checked against policy, approved and followed up in SAP with notification.
Enterprise
Customer issue to engineering resolution
Support tickets that need engineering get a linked Jira issue and the status flows back.
Enterprise
High-priority customer escalation
Cases that meet your escalation criteria become owned incidents with approvals and updates.
Enterprise
BambooHR employee onboarding
New employees get approved access and collaboration setup from BambooHR records.
Enterprise
Personio onboarding and attendance workflow
Personio records drive approved access and attendance follow-up with exceptions recorded.
Enterprise
ADP recruitment to employee access
Accepted applicants and work assignments in ADP lead to approved access on day one.
Enterprise
ERP data to Snowflake
SAP finance and sales data lands in Snowflake on schedule, with load results reported.
Enterprise
CRMConnect ticket escalation
CRMConnect tickets that need IT or operations become owned ServiceNow cases.
Enterprise
CRMConnect warehouse coordination
CRMConnect stock and orders stay aligned with Odoo, with shortages raised to owners.
FAQ
Microsoft 365 connector questions
- Which Microsoft 365 actions are prebuilt?
- Nexus includes 45 Microsoft 365 actions across Teams (16), Emails (14) and Calendar (15).
- Can Microsoft Teams start a workflow?
- Yes. Microsoft Teams is a listed trigger source.
- Does this require Microsoft cloud connectivity?
- The workflow needs network reach to the Microsoft services it calls. Nexus itself runs in your chosen deployment boundary.
Related reading
Continue from here
- Okta connector
Identity steps that precede productivity setup.
- Azure connector
Azure storage and event trigger sources.
- Human-in-the-loop
Approval as a workflow step.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Microsoft 365 fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.