Merge pull request #77548 from rwike77/portalupdates2

Portalupdates2

Author: rmca14

articles/active-directory/develop/quickstart-v1-android.md

@@ -13,7 +13,7 @@ ms.workload: identity
 ms.tgt_pltfrm: mobile-android
 ms.devlang: java
 ms.topic: quickstart
-ms.date: 09/24/2018
+ms.date: 05/21/2019
 ms.author: ryanwi
 ms.reviewer: brandwe, jmprieur, saeeda
 ms.custom: aaddev
@@ -84,18 +84,17 @@ You will need to have a native client application registered with Microsoft usin
     - Select ***Azure Active Directory*** > ***App Registrations***.
 
 2. Create the app
-    - Select **New application registration**.
+    - Select **New registration**.
     - Enter an app name in the **Name** field.
-    - In **Application type** select **Native**.
-    - In **Redirect URI**, enter `http://localhost`.
+    - Under **Supported account types**, select **Accounts in any organizational directory and personal Microsoft accounts**.
+    - In **Redirect URI**, select **Public client (mobile and desktop)** from the dropdown and enter `http://localhost`.
+    - Click **Register**.
 
 3. Configure Microsoft Graph
-    - Select **Settings > Required permissions**.
-    - Select **Add**, inside **Select an API** select ***Microsoft Graph***.
-    - Select the permission **Sign in and read user profile**, then hit **Select** to save.
-        - This permission maps to the `User.Read` scope.
-    - Optional: Inside **Required permissions > Windows Azure Active Directory**, remove the selected permission **Sign in and read user profile**. This will avoid the user consent page listing the permission twice.
-
+    - Select **API permissions**.
+    - Select **Add a permission**, inside **Select an API** select ***Microsoft Graph***.
+    - Under **Delegated permissions**, select the permission **User.Read**, then hit **Add** to save.        
+    
 4. Congrats! Your app is successfully configured. In the next section, you'll need:
     - `Application ID`
     - `Redirect URI`

articles/active-directory/develop/quickstart-v1-dotnet.md

@@ -14,7 +14,7 @@ ms.workload: identity
 ms.tgt_pltfrm: na
 ms.devlang: dotnet
 ms.topic: quickstart
-ms.date: 09/24/2018
+ms.date: 05/21/2019
 ms.author: ryanwi
 ms.reviewer: jmprieur
 ms.custom: aaddev
@@ -54,13 +54,15 @@ To enable your app to get tokens, register your app in your Azure AD tenant and
 1. Sign in to the [Azure portal](https://portal.azure.com).
 2. On the top bar, select your account and under the **Directory** list, choose the Active Directory tenant where you wish to register your application.
 3. Select on **All services** in the left-hand nav, and choose **Azure Active Directory**.
-4. On **App registrations**, choose **Add**.
-5. Follow the prompts and create a new **Native** client application.
-    * The **Name** of the application will describe your application to end users
-    * The **Redirect Uri** is a scheme and string combination that Azure AD will use to return token responses. Enter a value specific to your application, for example, `http://DirectorySearcher`.
+4. On **App registrations**, choose **New registration**.
+5. Follow the prompts to create a new client application.
+    * **Name** is the application name and describes your application to end users.
+    * Under **Supported account types**, select **Accounts in any organizational directory and personal Microsoft accounts**.
+    * **Redirect URI** is a scheme and string combination that Azure AD uses to return token responses. Enter a value that is specific to your application (for example, `http://DirectorySearcher`) and is based on the previous redirect URI information. Also select **Public client (mobile and desktop)** from the dropdown. 
 
 6. Once you've completed registration, AAD will assign your app a unique Application ID. You'll need this value in the next sections, so copy it from the application page.
-7. From the **Settings** page, choose **Required permissions** and choose **Add**. Select **Microsoft Graph** as the API, and under **Delegated permissions** add the **Read directory data** permission. Setting this permission enables your application to query the Graph API for users.
+7. From the **API permissions** page, select **Add a permission**. Inside **Select an API** select ***Microsoft Graph***.
+8. Under **Delegated permissions**, select the permission **User.Read**, then hit **Add** to save. This permission sets up your application to query the Azure AD Graph API for users.
 
 ## Step 2: Install and configure ADAL
 

articles/active-directory/develop/quickstart-v1-ios.md

@@ -14,7 +14,7 @@ ms.workload: identity
 ms.tgt_pltfrm: mobile-ios
 ms.devlang: objective-c
 ms.topic: quickstart
-ms.date: 09/24/2018
+ms.date: 05/21/2019
 ms.author: ryanwi
 ms.custom: aaddev
 ms.reviewer: brandwe
@@ -73,12 +73,13 @@ To set up your app to get tokens, you need to register the app in your Azure AD
 1. Sign in to the [Azure portal](https://portal.azure.com).
 2. On the top bar, select your account. Under the **Directory** list, choose the Active Directory tenant where you want to register your application.
 3. Select **All services** in the leftmost navigation pane, and then select **Azure Active Directory**.
-4. Select **App registrations**, and then select **Add**.
-5. Follow the prompts to create a new **Native** client application.
+4. Select **App registrations**, and then select **New registration**.
+5. Follow the prompts to create a new client application.
     * **Name** is the application name and describes your application to end users.
-    * **Redirect URI** is a scheme and string combination that Azure AD uses to return token responses. Enter a value that is specific to your application and is based on the previous redirect URI information.
+    * **Redirect URI** is a scheme and string combination that Azure AD uses to return token responses. Enter a value that is specific to your application and is based on the previous redirect URI information. Also select **Public client (mobile and desktop)** from the dropdown.
 6. After you've completed the registration, Azure AD assigns your app a unique application ID. You'll need this value in the next sections, so copy it from the application tab.
-7. From the **Settings** page, select **Required permissions > Add > Microsoft Graph**, and then under **Delegated permissions** add the **Read directory data** permission. This permission sets up your application to query the Azure AD Graph API for users.
+7. From the **API permissions** page, select **Add a permission**. Inside **Select an API** select ***Microsoft Graph***.
+8. Under **Delegated permissions**, select the permission **User.Read**, then hit **Add** to save. This permission sets up your application to query the Azure AD Graph API for users.
 
 ## Step 3: Install and configure ADAL
 

articles/active-directory/develop/quickstart-v1-xamarin.md

@@ -14,7 +14,7 @@ ms.workload: identity
 ms.tgt_pltfrm: mobile-xamarin
 ms.devlang: dotnet
 ms.topic: quickstart
-ms.date: 09/24/2018
+ms.date: 05/22/2019
 ms.author: ryanwi
 ms.reviewer: jmprieur
 ms.custom: aaddev
@@ -53,14 +53,14 @@ To enable the app to get tokens, you first need to register it in your Azure AD
 1. Sign in to the [Azure portal](https://portal.azure.com).
 2. On the top bar, click your account. Then, under the **Directory** list, select the Active Directory tenant where you want to register the app.
 3. Click **All services** in the left pane, and then select **Azure Active Directory**.
-4. Click **App registrations**, and then select **Add**.
-5. To create a new **Native Client Application**, follow the prompts.
+4. Click **App registrations**, and then select **New registration**.
+5. To create a new client application, follow the prompts.
    * **Name** describes the app to users.
+   * Under **Supported account types**, select **Accounts in any organizational directory and personal Microsoft accounts**.
    * **Redirect URI** is a scheme and string combination that Azure AD uses to return token responses. Enter a value (for example, `http://DirectorySearcher`).
 6. After you’ve completed registration, Azure AD assigns the app a unique application ID. Copy the value from the **Application** tab, because you'll need it later.
-7. On the **Settings** page, select **Required Permissions**, and then select **Add**.
-8. Select **Microsoft Graph** as the API. Under **Delegated Permissions**, add the **Read Directory Data** permission. 
-   This action enables the app to query the Graph API for users.
+7. From the **API permissions** page, select **Add a permission**. Inside **Select an API** select ***Microsoft Graph***.
+8. Under **Delegated permissions**, select the permission **User.Read**, then hit **Add** to save. This permission sets up your application to query the Azure AD Graph API for users.
 
 ## Step 3: Install and configure ADAL
 

articles/active-directory/develop/v1-protocols-openid-connect-code.md

@@ -14,7 +14,7 @@ ms.workload: identity
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 03/04/2019
+ms.date: 05/22/2019
 ms.author: ryanwi
 ms.reviewer: hirsin
 ms.custom: aaddev

includes/active-directory-protocols-getting-started.md

@@ -12,7 +12,7 @@ ms.workload: identity
 ms.tgt_pltfrm: na
 ms.devlang: dotnet
 ms.topic: article
-ms.date: 04/18/2018
+ms.date: 05/22/2019
 ms.author: priyamo
 ---
 ## Register your application with your AD tenant
@@ -22,10 +22,11 @@ First, you need to register your application with your Azure Active Directory (A
 * Choose your Azure AD tenant by clicking on your account in the top right corner of the page, followed by clicking on the **Switch Directory** navigation and then select the appropriate tenant. 
   * Skip this step, if you've only one Azure AD tenant under your account or if you've already selected the appropriate Azure AD tenant.
 * In the left hand navigation pane, click on **Azure Active Directory**.
-* Click on **App Registrations** and click on **New application registration**.
-* Follow the prompts and create a new application. It doesn't matter if it is a web application or a native application for this tutorial, but if you'd like specific examples for web applications or native applications, check out our [quickstarts](../articles/active-directory/develop/v1-overview.md).
-  * For Web Applications, provide the **Sign-On URL**, which is the base URL of your app, where users can sign in e.g `http://localhost:12345`.
-    <!--TODO: add once App ID URI is configurable: The **App ID URI** is a unique identifier for your application. The convention is to use `https://<tenant-domain>/<app-name>`, e.g. `https://contoso.onmicrosoft.com/my-first-aad-app`-->
-  * For Native Applications provide a **Redirect URI**, which Azure AD will use to return token responses. Enter a value specific to your application, .e.g `http://MyFirstAADApp`
-* Once you've completed registration, Azure AD will assign your application a unique client identifier, the **Application ID**. You need this value in the next sections, so copy it from the application page.
+* Click on **App Registrations** and click on **New registration**.
+* Follow the prompts and create a new application. It doesn't matter if it is a web application or a public client (mobile & desktop) application for this tutorial, but if you'd like specific examples for web applications or public client applications, check out our [quickstarts](../articles/active-directory/develop/v1-overview.md).
+  * **Name** is the application name and describes your application to end users.
+  * Under **Supported account types**, select **Accounts in any organizational directory and personal Microsoft accounts**.
+  * Provide the **Redirect URI**. For Web Applications, this is the base URL of your app where users can sign in.  For example, `http://localhost:12345`. For public client (mobile & desktop), Azure AD uses it to return token responses. Enter a value specific to your application.  For example, `http://MyFirstAADApp`.
+    <!--TODO: add once App ID URI is configurable: The **App ID URI** is a unique identifier for your application. The convention is to use `https://<tenant-domain>/<app-name>`, e.g. `https://contoso.onmicrosoft.com/my-first-aad-app`-->  
+* Once you've completed registration, Azure AD will assign your application a unique client identifier (the **Application ID**). You need this value in the next sections, so copy it from the application page.
 * To find your application in the Azure portal, click **App registrations**, and then click **View all applications**.