Merge pull request #184005 from MicrosoftDocs/master

1/03 PM Publish

Author: huypub

.openpublishing.publish.config.json

@@ -820,6 +820,7 @@
     ".openpublishing.redirection.azure-web-pubsub.json",
     ".openpublishing.redirection.azure-monitor.json",
     ".openpublishing.redirection.azure-percept.json",
+    ".openpublishing.redirection.azure-productivity.json",
     "articles/azure-fluid-relay/.openpublishing.redirection.fluid-relay.json",
     "articles/azure-netapp-files/.openpublishing.redirection.azure-netapp-files.json",   
     "articles/azure-relay/.openpublishing.redirection.relay.json",

.openpublishing.redirection.json

@@ -17939,8 +17939,8 @@
     },
     {
       "source_path_from_root": "/articles/lab-services/classroom-labs/classroom-labs-overview.md",
-      "redirect_url": "/azure/lab-services/classroom-labs-overview",
-      "redirect_document_id": true
+      "redirect_url": "/azure/lab-services/get-started-manage-labs",
+      "redirect_document_id": false
     },
     {
       "source_path_from_root": "/articles/lab-services/classroom-labs/classroom-labs-scenarios.md",
@@ -45169,4 +45169,4 @@
       "redirect_document_id": false
     }
   ]
-}
+}

articles/active-directory-b2c/session-behavior.md

@@ -275,7 +275,7 @@ During the sign-out, Azure AD B2C simultaneously sends an HTTP request to the re
 To support single sign-out, the token issuer technical profiles for both JWT and SAML must specify:
 
 - The protocol name, such as `<Protocol Name="OpenIdConnect" />`
-- The reference  to the session technical profile, such as `UseTechnicalProfileForSessionManagement ReferenceId="SM-OAuth-issuer" />`.
+- The reference  to the session technical profile, such as `UseTechnicalProfileForSessionManagement ReferenceId="SM-jwt-issuer" />`.
 
 The following example illustrates the JWT and SAML token issuers with single sign-out:
 
@@ -289,11 +289,11 @@ The following example illustrates the JWT and SAML token issuers with single sig
       <Protocol Name="OpenIdConnect" />
       <OutputTokenFormat>JWT</OutputTokenFormat>
       ...    
-      <UseTechnicalProfileForSessionManagement ReferenceId="SM-OAuth-issuer" />
+      <UseTechnicalProfileForSessionManagement ReferenceId="SM-jwt-issuer" />
     </TechnicalProfile>
 
     <!-- Session management technical profile for OIDC based tokens -->
-    <TechnicalProfile Id="SM-OAuth-issuer">
+    <TechnicalProfile Id="SM-jwt-issuer">
       <DisplayName>Session Management Provider</DisplayName>
       <Protocol Name="Proprietary" Handler="Web.TPEngine.SSO.OAuthSSOSessionProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
     </TechnicalProfile>

articles/active-directory/app-proxy/what-is-application-proxy.md

@@ -436,8 +436,8 @@ The `acquireTokenSilent` method handles token acquisition and renewal without an
 
    ```JavaScript
       const graphConfig = {
-        graphMeEndpoint: "Enter_the_Graph_Endpoint_Herev1.0/me",
-        graphMailEndpoint: "Enter_the_Graph_Endpoint_Herev1.0/me/messages"
+        graphMeEndpoint: "Enter_the_Graph_Endpoint_Here/v1.0/me",
+        graphMailEndpoint: "Enter_the_Graph_Endpoint_Here/v1.0/me/messages"
       };
    ```
 
@@ -481,6 +481,10 @@ In the sample application created by this guide, the `callMSGraph()` method is u
    ```
 1. In your browser, enter **http://localhost:3000** or **http://localhost:{port}**, where *port* is the port that your web server is listening to. You should see the contents of your *index.html* file and the **Sign In** button.
 
+
+> [!Important]
+> Enable popups and redirects for your site in your browser settings.
+
 After the browser loads your *index.html* file, select **Sign In**. You're prompted to sign in with the Microsoft identity platform:
 
 ![The JavaScript SPA account sign-in window](media/active-directory-develop-guidedsetup-javascriptspa-test/javascriptspascreenshot1.png)

articles/active-directory/develop/tutorial-v2-javascript-spa.md

@@ -347,7 +347,7 @@ az vmss identity assign --name myVMSS --resource-group AzureADLinuxVM
 2. Install the Azure AD extension on your virtual machine scale set.
 
 ```azurecli
-az vmss extension set --publisher Microsoft.Azure.ActiveDirectory --name Azure ADSSHLoginForLinux --resource-group AzureADLinuxVM --vmss-name myVMSS
+az vmss extension set --publisher Microsoft.Azure.ActiveDirectory --name AADSSHLoginForLinux --resource-group AzureADLinuxVM --vmss-name myVMSS
 ```
 
 Virtual machine scale sets usually don't have public IP addresses, so you must have connectivity to them from another machine that can reach their Azure virtual network. This example shows how to use the private IP of a virtual machine scale set VM to connect from a machine in the same virtual network.