Strategy for migrating applications from Okta to Azure AD
To find success while migrating applications from Okta to Azure AD requires an excellent strategy. It is very important to consider the various organizational leaders, departments, app owners, and end-users who will be impacted via this integration. Making sure each party is aligned every step of the way is crucial to a seamless production roll-out.
With this solution, Edgile professionals will lead customers through five major phases to an app migration strategy.
Discovery and Scoping: Work with the client to understand what applications they use in their organization today (potentially leverage AD FS by deploying Azure AD Connect to gather an inventory of corporate apps). Check current Okta tools to export app inventory information. Scope out apps which will need to be migrated, apps that will not be migrated, and apps that are approaching end of life within the organization.
Prioritize and Planning: Categorize apps based on criticality, usage, and lifespan. Classify apps which are known to deal with highly sensitive business data and processes. Take into account app team availability into creating an app migration roadmap.
Design and Testing: Design a method to integrate the app into Azure AD with SSO (SAML, OAuth, OIDC, legacy methods etc.). Register the apps within the company’s test tenant and connect to their test app environment (if one exists). Lead and assist with user acceptance testing. Illustrate the single-sign on process and the ability to centrally manage the app within Azure (show the MyApps portal experience and customization options).
Perform Migration and Verify Deployment: Begin migrations and verify that the applications are properly handling SSO and check sign-in logs.
Management and Insight: Manage the end-user and admin logon experience. Enable Azure AD to centrally perform app auditing and reporting. Gain insight into app usage and user behaviors.