Windows 10 Azure OOBE, Okta as IdP
Enrolling into Workspace One UEM using Okta as the IdP is a great way to leverage your existing identity solution, whilst adding Workspace One to check device trust and add management.
1 -This article presumes the following:
- You’ve connected Workspace One UEM to vIDM. If not, follow this guide.
- You’ve added Okta as a IdP within vIDM. If not, follow this guide.
- Azure has been configured, users have synced, the AirWatch application added and federated to either Okta or vIDM. If not, follow this guide.
The flow for this type of enrollment is as follows:
- User types Azure username
- Azure sends user to organisation sign-in page. In this example, this is Workspace One (vIDM) with Okta added as a 3rd paty IdP
- User logins in with AD username and password that’s synced into Okta
- This then SSO’s into Workspace One UEM (AirWatch) for the enrollment
- User is then prompted with the standard Windows privacy and terms options
- User is then prompted to verify user account, this is done through text message in this example.
- User is then prompted for a PIN
- Workspace One Agent is then pushed to device
- The device is automatically enrolled into Workspace One UEM
- Scripts, applications, Bitlocker and certificates are installed on the machine
Bear in mind, some aspects of this video have been sped up for demoing purposes.