Integrate Office 365 in Okta
Get started by deploying Office 365 in your Okta orgThe Okta container that represents a real-world organization.. Then enhance the capabilities of the integration by using other topics on this page.
Deploy Office 365 in your Okta org
Use this guide if you are just getting started.
Jump to a specific part of the deployment guide from the following list:
- Add Office 365 to Okta
- Provision users to Office 365
- Configure Single Sign on for Office 365
- Assign Office 365 to users and groups
- Secure Office 365 using app sign-on policies
Harden the security for Office 365 by adding extra sign-on policies.
Configure enhanced provisioning and deprovisioning options or map custom attributes in the user profile.
For Office 365 apps such as Yammer or Dynamics CRM, Okta needs your consent to authenticate and authorize the end usersEnd users are people in your org without administrative control. They can authenticate into apps from the icons on their My Applications home page, but they are provisioned, deprovisioned, assigned, and managed by admins. on your behalf.
Import groups later while federating Office 365. Focus on provisioning first and group assignments later.
Add new Office 365 apps to the end user dashboard.
Push groups from non-AD directory services and third party apps to Office 365.
Change Office 365 single sign on method from SWA to WS-federation.
Create custom WS-Federation-enabled applications.
Enable silent activation for shared workstation or VDI environments.
Let Okta handle the MFA requirements for Azure AD MFA.
Early Access features
Early access (EA) features are opt-in features available either upon request to Okta Support or in the Feature Manager. See Manage Early Access and Beta features to learn how to enable these features. The following list contains EA features related to Office 365.
Configure the iOS mail app to prevent users with unmanaged devices from accessing Microsoft Office 365 Exchange ActiveSync.Top