Anywhere Workspace

Step-By-Step Guidance for Adding Microsoft 365 Applications from Okta to VMware Workspace ONE®

We’ve seen a myriad of customers across many different business verticals looking to better manage their digital workspace with convenient access to the Microsoft Office applications their users need to be productive. Okta is a valued partner and an industry leader in the Identity Provider space and can work in tandem with VMware Workspace ONE® Access™ to provide a truly comprehensive Unified Catalog to the end user. As well as providing a Unified Catalog we can also leverage the conditional access capabilities of Workspace ONE Access to secure corporate resources as seen fit. In this post we’ll address the steps to integrate Workspace ONE Access, Office 365, and Okta.

We will start by creating an Office 365 Developer tenant and with that we will get access to Azure Active Directory. We will then link the Azure Active Directory to our existing on-premises Active Directory. Afterward, we will leverage Okta as an identity provider for Office 365 and then federate with Okta to Workspace ONE Access to aggregate our unified catalog and provide conditional access to the applications imported from Okta.

Part 1: Signing up for Microsoft 365 Account

Prerequisite: Access to your domain vendor account (ex: GoDaddy).

  1.  Go to Join the Microsoft 365 Developer Program and sign in with your VMware account.
    • Say you’re using applications from internal use.
    • Choose which applications you’re interested in.
  2.  When you’re on the dashboard screen click “Go to Subscription.”
  3. You will be prompted to log in with your new admin account that you created and enable 2FA. This can be later disabled for testing reasons.
  4.  In the Office portal go to Admin.
  1. Go to … Show all > Settings > Domains.
  • Click “Add domain.”
  • Type in your domain.
  • Click “Use this domain”, then “Continue.”
  • Click “Add DNS records” and finish adding your domain.

Part 2: Setting Up Microsoft Azure AD with Traditional AD

Prerequisite: Traditional AD and domain joined 2016+ Win 10 Server with NO other Azure ADconnectors running on it.

  1. From within the newly provisioned server navigate to the same page.
  2. Click “Azure Active Directory” at the bottom left of the navigation or go to aad.portal.azure.com.
  1. Once in the Azure Active Directory admin center, click “Azure Active Directory.”
  2. Scroll down the menu to the left and click “Azure AD Connect.”
  3. Click “Manage Azure AD cloud sync”, then download the agent.
This image has an empty alt attribute; its file name is 1C2EEDAF-6832-48F1-B8D8-19834EC00044.png
  1. Run the agent.
  • Click next.
  • NOTE: If an Internet Explorer Trusted sites pop up appears, click add on the sites.
  1. On the Configure Service Account page, select “Create gMSA” and enter the credentials for a domain administrator account.
  1. Click “Confirm” on Agent configuration.
  2. After installation return to the Azure AD admin center.
  3. Click on “Azure AD Connect.”
  1. Click “Manage Azure AD cloud sync.”
  2. Go to “Review all agents” to see if your connector is there. If not, restart VM.
  3. Go back by clicking on “Azure AD Connect cloud Sync” at the top of the page. Click “New configuration”, then create.
  4. Make sure “Enable password hash sync” is checked.
  1. Click “Create.”
  1. Your parameters should look like the screenshot above.

Part 3: Creating a service account in Microsoft 365 for Okta

  1. Go to the Microsoft 365 Admin console.
  2. In the navigation pane go to Users > Active Users > Click “Add a user.”
  3. Fill in the required text fields.
  4. In the Product licenses section, check the box next to “Microsoft 365 E5 Developer (Without Windows and Audio Conferencing).”
  5. In Optional settings assign the user as a “Global Administrator.”
  6. Your Finish section should look like the picture below.
  1. Click “Finish adding.”

Part 4: Configuring Microsoft 365 in Okta

Prerequisite: Okta tenant with deployed Okta connector.

  1. After logging into Okta, go to Application > Applications > Browse App Catalog.
  1. Click on “Microsoft Office 365”, then click “Add Integration.”
  2. Enter the tenant’s name of your Office/Azure AD account under “Microsoft Tenant Name” (e.g., this will be the random string before onmicrosoft.com, such as y876z).
  3. Enter your domain name next to “Your Office 365 company domain.”
  1. Scroll to the bottom and enable “Automatically log in when user lands on login page.”
  2. Click “Next.”
  3. Click “WS-Federation” under Sign-on Methods and enable “Let Okta configure WS-Federation automatically for me.”
  1. Enter your Okta Service account credentials that were created in Part 3.
  1. Enable “Allow administrator to consent for Advanced API access” and click the “Authenticate with Microsoft Office 365” button to log in as an administrator and enable that integration.
  2. Click “Done.”
  3. Click on “Microsoft Office 365” in the Applications menu.
  4. Go to Provisioning.
  5. Under integration, click Enable “API Integration” if it is not already enabled.
  6. Enter your Okta service account credentials.
    • Note: When you enter the credentials, if you get an error message saying you must enable the integration in Microsoft Graph, look for a button that says, “Authenticate with Microsoft Office 365” and use that to log in with the service account instead.
This image has an empty alt attribute; its file name is 955C6CC0-16AD-4BA4-A90A-9CCC693F5D49-1024x719.png
  1. Click “Assignments.”
  2. Click Assign > Assign to People.
  3. Choose a user to assign Office applications to.
  4. Under licenses (of which there are many) click enable next to “Microsoft 365 E5 Developer (Without Windows and Audio Conferencing)” this will include most of the Office 365 applications.
  5. Under Roles click “User.”
  6. Click “Save and Go Back.”

Part 5: Connecting Okta and Workspace ONE Access

(Add Workspace ONE Access as IdP in Okta, add routing rules, get API key)

  1. In the Okta console, go to Security > Identity Providers > Add identity provider.
  1. Choose “SAML 2.0 IdP”, then click “Next.”
  2. Pause here and login to your Access console.
  3. Go to Catalog > Settings > SAML Metadata.
  4. Click “Identity Provider (IdP) metadata” hyperlink.
  5. Copy the following values: entityID & SingleSignOnService.
  6. Go back to the Access console and click “Download.”
  7. Return to the Okta console.
  8. Place your entityID under “IdP Issuer URI” and SingleSignOnService under “IdP Single Sign-On URL” and “Destination.”
  9. Before you can upload your certificate, the file extension needs to be changed from “.cer” to “. PEM” or “. DER”. Once you’re done, upload the certificate.
  10. The rest of your settings should look like the screenshots below.
  1. Click “Finish.”
  2. Go to Security > API > Tokens > Create Token.
  3. Enter name, then click “Create Token.”
  4. In your Workspace ONE Access console go to Identity & Access Management > Setup > Okta.
  5. Enter your information, then click “Save.”

Part 6: Testing

  1. Go to your Workspace ONE Access console. (Make sure you choose the right domain.)
  2. Login as a regular user.
  3. You should now see all the Microsoft 365 applications in the console.

Need Expert Assistance?

Contact your VMware sales representative to learn how VMware Professional Services can help you with your workforce transformation initiatives.

References:

Comments

Leave a Reply

Your email address will not be published.