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/develop/scenario-mobile-app-registration.md
+11-13Lines changed: 11 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,25 +40,23 @@ For more information, see [Scenarios and supported authentication flows](authent
40
40
41
41
### Interactive authentication
42
42
43
-
When you build a mobile app that uses interactive authentication, the most critical registration step is the redirect URI. You can set interactive authentication through the [platform configuration on the **Authentication** blade](https://aka.ms/MobileAppReg).
43
+
When you build a mobile app that uses interactive authentication, the most critical registration step is the redirect URI. This experience enables your app to get single sign-on (SSO) through Microsoft Authenticator (and Intune Company Portal on Android). It also supports device management policies.
44
44
45
-
This experience will enable your app to get single sign-on (SSO) through Microsoft Authenticator (and Intune Company Portal on Android). It will also support device management policies.
46
-
47
-
The app registration portal provides a preview experience to help you compute the brokered reply URI for iOS and Android applications:
48
-
49
-
1. In the app registration portal, select **Authentication** > **Try out the new experience**.
50
-
51
-

52
-
53
-
2. Select **Add a platform**.
45
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Developer](../roles/permissions-reference.md#application-developer).
46
+
1. Browse to **Identity** > **Applications** > **App registrations**.
47
+
1. Select **New registration**.
48
+
1. Enter a **Name** for the application.
49
+
1. For **Supported account types**, select **Accounts in this organizational directory only**.
50
+
1. Select **Register**.
51
+
1. Select **Authentication** and then select **Add a platform**.
54
52
55
53

56
54
57
-
3. When the list of platforms is supported, select **iOS**.
55
+
1. When the list of platforms is supported, select **iOS / macOS**.
58
56
59
57

60
58
61
-
4. Enter your bundle ID, and then select **Register**.
59
+
1. Enter your bundle ID, and then select **Configure**.
62
60
63
61

64
62
@@ -81,7 +79,7 @@ If your app uses only username-password authentication, you don't need to regist
81
79
82
80
However, identify your application as a public client application. To do so:
83
81
84
-
1. Still in the <ahref="https://portal.azure.com/"target="_blank">Azure portal</a>, select your app in **App registrations**, and then select **Authentication**.
82
+
1. Still in the Microsoft Entra admin center, select your app in **App registrations**, and then select **Authentication**.
85
83
1. In **Advanced settings** > **Allow public client flows** > **Enable the following mobile and desktop flows:**, select **Yes**.
86
84
87
85
:::image type="content" source="media/scenarios/default-client-type.png" alt-text="Enable public client setting on Authentication pane in Azure portal":::
0 commit comments