Merge pull request #176254 from MicrosoftDocs/master

10/18 PM Publish

Author: huypub

.openpublishing.redirection.json

@@ -23653,6 +23653,11 @@
       "redirect_url": "https://notebooks.azure.com",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/notebooks/quickstart-export-jupyter-notebook-project.md",
+      "redirect_url": "https://notebooks.azure.com",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/notification-hubs/configure-android-device-messaging.md",
       "redirect_url": "/azure/notification-hubs/configure-google-firebase-cloud-messaging",

articles/active-directory-b2c/tutorial-create-user-flows.md

@@ -225,10 +225,9 @@ Now, grant permissions to the API scope you exposed earlier in the *IdentityExpe
 1. Select the **My APIs** tab, then select the **IdentityExperienceFramework** application.
 1. Under **Permission**, select the **user_impersonation** scope that you defined earlier.
 1. Select **Add permissions**. As directed, wait a few minutes before proceeding to the next step.
-1. Select **Grant admin consent for (your tenant name)**.
-1. Select your currently signed-in administrator account, or sign in with an account in your Azure AD B2C tenant that's been assigned at least the *Cloud application administrator* role.
-1. Select **Accept**.
-1. Select **Refresh**, and then verify that "Granted for ..." appears under **Status** for the scopes - offline_access, openid and user_impersonation. It might take a few minutes for the permissions to propagate.
+1. Select **Grant admin consent for *<your tenant name)>***.
+1. Select **Yes**.
+1. Select **Refresh**, and then verify that "Granted for ..." appears under **Status** for the scope.
 
 * * *
 

articles/active-directory/app-proxy/application-proxy-configure-single-sign-on-with-headers.md

@@ -45,7 +45,7 @@ The following table lists common capabilities required for header-based authenti
 
 ## How it works
 
-:::image type="content" source="./media/application-proxy-configure-single-sign-on-with-headers/how-it-works.png" alt-text="How header-based single sign-on works with Application Proxy." lightbox="./media/application-proxy-configure-single-sign-on-with-headers/how-it-works.png":::
+:::image type="content" source="./media/application-proxy-configure-single-sign-on-with-headers/how-it-works-updated.png" alt-text="How header-based single sign-on works with Application Proxy." lightbox="./media/application-proxy-configure-single-sign-on-with-headers/how-it-works-updated.png":::
 
 1. The Admin customizes the attribute mappings required by the application in the Azure AD portal. 
 2. When a user accesses the app, Application Proxy ensures the user is authenticated by Azure AD 

articles/active-directory/app-proxy/media/application-proxy-configure-single-sign-on-with-headers/how-it-works-updated.png

@@ -3,15 +3,15 @@ title: "Migrate your JavaScript application from ADAL.js to MSAL.js | Azure"
 titleSuffix: Microsoft identity platform
 description: How to update your existing JavaScript application to use the Microsoft Authentication Library (MSAL) for authentication and authorization instead of the Active Directory Authentication Library (ADAL).
 services: active-directory
-author: derisen
+author: KarenH444
 manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
 ms.topic: how-to
 ms.workload: identity
 ms.date: 07/06/2021
-ms.author: v-doeris
+ms.author: karenhoran
 ms.custom: has-adal-ref
 #Customer intent: As an application developer, I want to learn how to change the code in my JavaScript application from using ADAL.js as its authentication library to MSAL.js.
 ---

articles/active-directory/app-proxy/media/application-proxy-configure-single-sign-on-with-headers/how-it-works.png

@@ -3,15 +3,15 @@ title: "Migrate your Node.js application from ADAL to MSAL | Azure"
 titleSuffix: Microsoft identity platform
 description: How to update your existing Node.js application to use the Microsoft Authentication Library (MSAL) for authentication and authorization instead of the Active Directory Authentication Library (ADAL).
 services: active-directory
-author: derisen
+author: KarenH444
 manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
 ms.topic: how-to
 ms.workload: identity
 ms.date: 04/26/2021
-ms.author: v-doeris
+ms.author: karenhoran
 ms.custom: has-adal-ref
 #Customer intent: As an application developer, I want to learn how to change the code in my Node.js application from using ADAL as its authentication library to MSAL.
 ---

articles/active-directory/develop/msal-compare-msal-js-and-adal-js.md

@@ -3,14 +3,14 @@ title: "Quickstart: Call Microsoft Graph from a Node.js console app | Azure"
 titleSuffix: Microsoft identity platform
 description: In this quickstart, you download and run a code sample that shows how a Node.js console application can get an access token and call an API protected by a Microsoft identity platform endpoint, using the app's own identity
 services: active-directory
-author: derisen
+author: KarenH444
 manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
 ms.topic: quickstart
 ms.date: 02/17/2021
-ms.author: v-doeris
+ms.author: karenhoran
 #Customer intent: As an application developer, I want to learn how my Node.js app can get an access token and call an API that is protected by an Microsoft identity platform endpoint using client credentials flow.
 ---
 

articles/active-directory/develop/msal-node-migration.md

@@ -3,14 +3,14 @@ title: "Quickstart: Call Microsoft Graph from a Node.js desktop app | Azure"
 titleSuffix: Microsoft identity platform
 description: In this quickstart, you learn how a Node.js Electron desktop application can sign-in users and get an access token to call an API protected by a Microsoft identity platform endpoint
 services: active-directory
-author: derisen
+author: KarenH444
 manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
 ms.topic: quickstart
 ms.date: 02/17/2021
-ms.author: v-doeris
+ms.author: karenhoran
 #Customer intent: As an application developer, I want to learn how my Node.js Electron desktop application can get an access token and call an API that's protected by a Microsoft identity platform endpoint.
 ---
 

articles/active-directory/develop/quickstart-v2-nodejs-console.md

@@ -3,14 +3,14 @@ title: "Tutorial: Call Microsoft Graph in a Node.js console app | Azure"
 titleSuffix: Microsoft identity platform
 description: In this tutorial, you build a console app for calling Microsoft Graph to a Node.js console app.
 services: active-directory
-author: derisen
+author: KarenH444
 manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
 ms.topic: tutorial
 ms.date: 02/17/2021
-ms.author: v-doeris
+ms.author: karenhoran
 ---
 
 # Tutorial: Call the Microsoft Graph API in a Node.js console app