Identity & Collaboration integration
Coordinate Okta identity changes with Microsoft 365 collaboration.
Okta user, group and role operations run under access policy, then Microsoft 365 Teams, email and calendar steps notify, schedule and confirm, all in one recorded run.
The problem
Why Microsoft 365 + Okta needs a governed process
Access is granted in one place and people are told in another. New starters wait, managers chase confirmations, and nothing links the access decision to the message that followed.
Responsibility
How the systems divide responsibility
Identity authority
Okta
Users, groups, roles and identity events.
Collaboration layer
Microsoft 365
Teams messages, email and calendar.
Capabilities
What Nexus orchestrates
Pre-built action groups used in this pattern. Anything else runs through an API, protocol or database step, or Rules + Code, in the same workflow.
Microsoft 365
45 ACTIONS
- Teams16
- Emails14
- Calendar15
Okta
42 ACTIONS
- User Management14
- Groups12
- Roles11
- Events5
Architecture
One governed run across both systems
How work starts
Microsoft Teams, webhook or schedule
Microsoft Teams is a trigger source. Identity changes can also start from a webhook, a schedule or another system's event.
When a pre-built action does not cover it
Workflow patterns
What teams run across Microsoft 365 + Okta
01
Onboarding with welcome and schedule
An Okta user is created and grouped, then a Teams message and calendar invites go to the new starter and manager.
02
Access request approved in Teams
A request posted in Teams routes to the access owner. Approval continues to the Okta group change.
03
Role change notification
A role assignment in Okta triggers an email to the user and their manager with what changed.
04
Offboarding confirmation
Okta deactivation is followed by a confirmation to the manager and removal of future calendar holds.
Direction and ownership
Which way each change moves
Identity decisions are made against Okta. Microsoft 365 steps communicate and schedule around them. Microsoft 365 app actions do not replace identity operations.
Okta Microsoft 365
Outcome of a user, group or role change for notification and scheduling.
Microsoft 365 Okta
An approval response in Teams that allows an identity step to continue.
Control
Approvals and exception handling
Human approval
Group and role changes outside baseline policy pause for the access owner, who can respond in Teams.
Exceptions
- Unknown users or groups stop the run before any change.
- Notification failures do not undo identity changes and are retried separately.
- Okta errors are captured with the response.
Security, audit and deployment
Every run leaves a reviewable record
- The request or event that started the run.
- Policy result and approver decision.
- Each Okta operation and response.
- Messages and invites sent.
Credentials for Microsoft 365 and Okta are held in the vault and used only by the steps that need them. Role-based permissions decide who can edit, approve and run the workflow. Nexus runs on premises, in private cloud or air-gapped, so the execution record stays inside your deployment boundary. Governance and audit
Participating connectors
The connectors behind this pattern
Related
Continue from here
- Governed employee access changes with ServiceNow, Okta and Microsoft 365
Approval, identity and collaboration steps in one run.
- Governed self-service
Requests with policy and approval built in.
- Enterprise integration
Connectors, interfaces and code in one platform.
- Integration explorer
Add more systems to this combination.
FAQ
Microsoft 365 + Okta questions
- Does Microsoft 365 manage identities here?
- No. Identity operations run against Okta. Microsoft 365 actions cover Teams, email and calendar.
- Can approvers respond in Teams?
- Yes. Microsoft Teams is a trigger source and can carry approval responses back into the run.
- What about Azure identity?
- Azure has its own pre-built actions, including identity-related groups, and can be added to the same workflow.
Integration review
Discuss this integration
Bring your Microsoft 365 and Okta process. We will map ownership, approval and the steps each system needs.