Skip to content

Commit ab4c3d6

Browse files
Merge pull request #250004 from davidmu1/updatesteps26
updated sign-in steps for admin center
2 parents 98fe5cf + cbaca97 commit ab4c3d6

File tree

1 file changed

+11
-13
lines changed

1 file changed

+11
-13
lines changed

articles/active-directory/develop/scenario-mobile-app-registration.md

Lines changed: 11 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -40,25 +40,23 @@ For more information, see [Scenarios and supported authentication flows](authent
4040

4141
### Interactive authentication
4242

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.
4444

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-
![The Authentication blade, where you choose a new experience](https://user-images.githubusercontent.com/13203188/60799285-2d031b00-a173-11e9-9d28-ac07a7ae894a.png)
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**.
5452

5553
![Add a platform](https://user-images.githubusercontent.com/13203188/60799366-4c01ad00-a173-11e9-934f-f02e26c9429e.png)
5654

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

5957
![Choose a mobile application](https://user-images.githubusercontent.com/13203188/60799411-60de4080-a173-11e9-9dcc-d39a45826d42.png)
6058

61-
4. Enter your bundle ID, and then select **Register**.
59+
1. Enter your bundle ID, and then select **Configure**.
6260

6361
![Enter your bundle ID](https://user-images.githubusercontent.com/13203188/60799477-7eaba580-a173-11e9-9f8b-431f5b09344e.png)
6462

@@ -81,7 +79,7 @@ If your app uses only username-password authentication, you don't need to regist
8179

8280
However, identify your application as a public client application. To do so:
8381

84-
1. Still in the <a href="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**.
8583
1. In **Advanced settings** > **Allow public client flows** > **Enable the following mobile and desktop flows:**, select **Yes**.
8684

8785
:::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

Comments
 (0)