You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/migrate-applications-from-okta.md
+15-9Lines changed: 15 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,14 @@ ms.custom: not-enterprise-apps
18
18
19
19
In this tutorial, you'll learn how to migrate your applications from Okta to Azure Active Directory (Azure AD).
20
20
21
+
## Prerequisites
22
+
23
+
To manage the application in Azure AD, you need:
24
+
25
+
- An Azure AD user account. If you don't already have one, you can [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
26
+
- One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.
27
+
28
+
21
29
## Create an inventory of current Okta applications
22
30
23
31
Before migration, document the current environment and application settings. You can use the Okta API to collect this information. Use an API explorer tool such as [Postman](https://www.postman.com/).
@@ -84,11 +92,8 @@ We recommend you copy and convert this JSON list to a CSV format:
84
92
85
93
To migrate a SAML 2.0 application to Azure AD, configure the application in your Azure AD tenant for application access. In this example, we convert a Salesforce instance.
86
94
87
-
1. To configure the applications, follow the tutorial [Azure Active Directory single sign-on (SSO) integration with Salesforce](../saas-apps/salesforce-tutorial.md).
88
-
89
-
To complete the migration, repeat the configuration for all applications in the Okta tenant.
90
-
91
-
2. In the [Azure portal](https://portal.azure.com), select **Azure Active Directory** > **Enterprise applications** > **+ New application**.
95
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
96
+
2. Browse to **Identity** > **Applications** > **Enterprise applications** > **All applications**, then select **New application**.
92
97
93
98

94
99
@@ -108,7 +113,7 @@ To complete the migration, repeat the configuration for all applications in the
108
113
109
114

110
115
111
-
7. Upload the XML file you downloaded from the Azure portal. Then select **Create**.
116
+
7. Upload the XML file you downloaded from the Microsoft Entra admin center. Then select **Create**.
112
117
8. Upload the certificate you downloaded from Azure. Select **Save**.
113
118
114
119

@@ -123,7 +128,7 @@ To complete the migration, repeat the configuration for all applications in the
123
128
124
129

125
130
126
-
11. To upload the file to the Azure portal, in the Azure AD **Enterprise applications** page, in the SAML SSO settings, select **Upload metadata file**.
131
+
11. To upload the file to the Microsoft Entra admin center, in the Azure AD **Enterprise applications** page, in the SAML SSO settings, select **Upload metadata file**.
127
132
12. Ensure the imported values match the recorded values. Select **Save**.
128
133
129
134

@@ -170,8 +175,9 @@ To migrate an OpenID Connect (OIDC) or OAuth 2.0 application to Azure AD, in you
170
175
171
176
To complete the migration, repeat configuration for all applications in the Okta tenant.
172
177
173
-
1. Sign in to the [Azure portal](https://portal.azure.com), then select **Azure Active Directory** > **Enterprise applications**.
174
-
2. Under **All applications**, select **New application**.
178
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
0 commit comments