Merge pull request #252424 from MicrosoftDocs/main

Release arcscvmm pup2 ---scheduled release at 7:45am of 9/21

Author: Saisang

articles/active-directory/conditional-access/concept-conditional-access-grant.md

@@ -136,7 +136,7 @@ See [Require approved client apps for cloud app access with Conditional Access](
 
 In Conditional Access policy, you can require that an [Intune app protection policy](/intune/app-protection-policy) is present on the client app before access is available to the selected applications. These mobile application management (MAM) app protection policies allow you to manage and protect your organization's data within specific applications.
 
-To apply this grant control, Conditional Access requires that the device is registered in Microsoft Entra ID, which requires using a broker app. The broker app can be either Microsoft Authenticator for iOS or Microsoft Company Portal for Android devices. If a broker app isn't installed on the device when the user attempts to authenticate, the user is redirected to the app store to install the broker app. App protection policies are generally available for iOS and Android, and in public preview for Microsoft Edge on Windows. [Windows devices support no more than 3 Microsoft Entra user accounts in the same session](../devices/faq.yml#i-can-t-add-more-than-3-azure-ad-user-accounts-under-the-same-user-session-on-a-windows-10-11-device--why). For more information about how to apply policy to Windows devices, see the article [Require an app protection policy on Windows devices (preview)](how-to-app-protection-policy-windows.md).
+To apply this grant control, Conditional Access requires that the device is registered in Microsoft Entra ID, which requires using a broker app. The broker app can be either Microsoft Authenticator for iOS or Microsoft Company Portal for Android devices. If a broker app isn't installed on the device when the user attempts to authenticate, the user is redirected to the app store to install the broker app. App protection policies are generally available for iOS and Android, and in public preview for Microsoft Edge on Windows. [Windows devices support no more than 3 Microsoft Entra user accounts in the same session](../devices/faq.yml#i-can-t-add-more-than-3-microsoft-entra-user-accounts-under-the-same-user-session-on-a-windows-10-11-device--why). For more information about how to apply policy to Windows devices, see the article [Require an app protection policy on Windows devices (preview)](how-to-app-protection-policy-windows.md).
 
 Applications must meet certain requirements to support app protection policies. Developers can find more information about these requirements in the section [Apps you can manage with app protection policies](/mem/intune/apps/app-protection-policy#apps-you-can-manage-with-app-protection-policies). 
 

articles/active-directory/develop/scenario-web-app-call-api-acquire-token.md

@@ -61,7 +61,7 @@ public async Task<IActionResult> Profile()
 
  // Use the access token to call a protected web API.
  HttpClient client = new HttpClient();
- client.DefaultRequestHeaders.Add("Authorization", authorizationHeader);
+ client.DefaultRequestHeaders.Add("Authorization", accessToken);
  string json = await client.GetStringAsync(url);
 }
 ```

articles/active-directory/devices/TOC.yml

@@ -7,16 +7,16 @@
 - name: Tutorials
   expanded: false
   items:
-  - name: Azure AD join a new Windows device
+  - name: Microsoft Entra join a new Windows device
     href: device-join-out-of-box.md
 - name: Concepts
   expanded: true
   items:
-  - name: Azure AD registered devices
+  - name: Microsoft Entra registered devices
     href: concept-device-registration.md
-  - name: Azure AD joined devices 
+  - name: Microsoft Entra joined devices 
     href: concept-directory-join.md
-  - name: Hybrid Azure AD joined devices
+  - name: Microsoft Entra hybrid joined devices
     href: concept-hybrid-join.md
   - name: Device registration flows
     href: device-registration-how-it-works.md
@@ -27,36 +27,36 @@
 - name: How-to guides
   expanded: false
   items:
-  - name: Plan your Azure AD device deployment
+  - name: Plan your Microsoft Entra device deployment
     href: plan-device-deployment.md
-  - name: Azure AD join
+  - name: Microsoft Entra join
     expanded: false
     items:
-    - name: Plan your Azure AD join implementation
+    - name: Plan your Microsoft Entra join implementation
       href: device-join-plan.md
-    - name: Assign local admins to Azure AD joined devices
+    - name: Assign local admins to Microsoft Entra joined devices
       href: assign-local-admin.md
-  - name: Hybrid Azure AD join
+  - name: Microsoft Entra hybrid join
     expanded: false
     items:
-    - name: Plan your hybrid Azure AD join implementation
+    - name: Plan your Microsoft Entra hybrid join implementation
       href: hybrid-join-plan.md
-    - name: Targeted hybrid Azure AD join deployment
+    - name: Targeted Microsoft Entra hybrid join deployment
       href: hybrid-join-control.md 
-    - name: Configure hybrid Azure AD join
+    - name: Configure Microsoft Entra hybrid join
       href: how-to-hybrid-join.md
-    - name: Verifying hybrid Azure AD join
+    - name: Verifying Microsoft Entra hybrid join
       href: how-to-hybrid-join-verify.md
-    - name: Troubleshoot hybrid Azure AD join
+    - name: Troubleshoot Microsoft Entra hybrid join
       expanded: false
       items:
-      - name: Troubleshoot hybrid Azure AD joined Windows current version
+      - name: Troubleshoot Microsoft Entra hybrid joined Windows current version
         href: troubleshoot-hybrid-join-windows-current.md
       - name: Troubleshoot pending device state
         href: /troubleshoot/azure/active-directory/pending-devices?toc=/azure/active-directory/fundamentals/toc.json
       - name: Troubleshoot using dsregcmd
         href: troubleshoot-device-dsregcmd.md
-      - name: Troubleshoot hybrid Azure AD joined down level Windows devices
+      - name: Troubleshoot Microsoft Entra hybrid joined down level Windows devices
         href: troubleshoot-hybrid-join-windows-legacy.md
   - name: Local Administrator Password Solution
     href: howto-manage-local-admin-passwords.md
@@ -69,9 +69,9 @@
     href: troubleshoot-primary-refresh-token.md
   - name: Manage stale devices
     href: manage-stale-devices.md
-  - name: Azure Linux VMs and Azure AD
+  - name: Azure Linux VMs and Microsoft Entra ID
     href: howto-vm-sign-in-azure-ad-linux.md
-  - name: Azure Windows VMs and Azure AD
+  - name: Azure Windows VMs and Microsoft Entra ID
     href: howto-vm-sign-in-azure-ad-windows.md
   - name: Virtual desktop infrastructure
     href: howto-device-identity-virtual-desktop-infrastructure.md
@@ -93,10 +93,10 @@
     href: troubleshoot-mac-sso-extension-plugin.md
 - name: Reference
   items:
-  - name: Hybrid Azure AD join reference
+  - name: Microsoft Entra hybrid join reference
     expanded: false
     items:
-    - name: Configure hybrid Azure AD join manually
+    - name: Configure Microsoft Entra hybrid join manually
       href: hybrid-join-manual.md
     - name: Enable older operating systems
       href: how-to-hybrid-join-downlevel.md