OCC - Microsoft Office 365 Playbook Skip to main content
https://support.okta.com/help/oktaarticledetailpage?childcateg=&id=ka0f0000000xzkgka4&source=documentation&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fdocumentation%2fknowledge_article%2focc-microsoft-office-365-playbook
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Average Rating:
OCC - Microsoft Office 365 Playbook
Published: Sep 8, 2015   -   Updated: Mar 18, 2016

Note: The following article was designed for users of our free, one app edition -- Okta Cloud Connect. The steps below will guide you through the basic configuration between your directory, app of choice, and Okta. Paid Okta customers should also review the Exploring the Okta Application Network article.

The following steps need to be completed before you can configure Office 365 with Okta
  1. Register your domain with your Office 365 tenant
  2. Change your default domain
  3. Prepare your Active Directory
  4. Decide if you are going to using Dirsync
The following steps will be completed with Okta to implementing Office365 with OCC
  1. Deploy the Okta AD Agent
  2. Configure the Office365 application in Okta
  3. Deploy the Desktop SSO Agent

Step 1: Deploy the Okta AD Agent

Note: If you are using the LDAP Agent - Please click here for more Information
 
There are five basic steps to deploying the Okta AD agent.  Please refer to Okta AD Agent  article for these steps.  For a detailed Deployment Guide that explains everything there is to know please refer to Installing and Configuring the Active Directory Agent
 
Step 2: Configure the Office 365 application in Okta
This video shows the steps for configuring Office 365 with Okta
 


Here is the full deployment guide for Office 365: Setting Up Office 365 in Okta

To search for other Knowledge Base Articles about Office 365 and Okta - Click Here

Step 3: Deploy the Desktop SSO Agent (Optional)

Configuring the Desktop SSO agent is an optional step, that end users love.  It allows them to not to re-enter their AD credentials when accessing the application.  Okta uses Microsoft Integrated Web Authentication to check their kerboros ticket, if the ticket is valid and authenticate, then access to granted to the application and the user never sees the log in page.

To deploy the Desktop SSO agent refer to the following guide: Configuring Desktop SSO
 
While the Okta configuration is generally straightforward, the Okta team is here to help:

 

Post a Comment