Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into work-msix-glossary

Author: Heidilohr

.openpublishing.redirection.json

@@ -17508,6 +17508,11 @@
             "redirect_url": "/azure/virtual-wan/scenario-route-between-vnets-firewall",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/bastion/connect-native-client-windows.md",
+            "redirect_url": "/azure/bastion/native-client",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/virtual-wan/high-availability-vpn-client.md",
             "redirect_url": "/azure/virtual-wan/global-hub-profile",

articles/active-directory-b2c/partner-xid.md

@@ -122,10 +122,10 @@ Get the custom policy starter packs from GitHub, then update the XML files in th
       <Domain>X-ID</Domain>
       <DisplayName>X-ID</DisplayName>
       <TechnicalProfiles>
-        <TechnicalProfile Id="X-ID-Oauth2">
+        <TechnicalProfile Id="X-ID-OIDC">
           <DisplayName>X-ID</DisplayName>
           <Description>Login with your X-ID account</Description>
-          <Protocol Name="OAuth2" />
+          <Protocol Name="OpenIdConnect" />
           <Metadata>
             <Item Key="METADATA">https://oidc-uat.x-id.io/.well-known/openid-configuration</Item>
             <!-- Update the Client ID below to the X-ID Application ID -->
@@ -227,7 +227,7 @@ Add the new identity provider to the user journey.
 3. Set the value of **TargetClaimsExchangeId** to a friendly name.
 4. Add a **ClaimsExchange** element. 
 5. Set the **ID** to the value of the target claims exchange ID. This change links the xID button to `X-IDExchange` action. 
-6. Update the **TechnicalProfileReferenceId** value to the technical profile ID you created (`X-ID-Oauth2`).
+6. Update the **TechnicalProfileReferenceId** value to the technical profile ID you created (`X-ID-OIDC`).
 7. Add an Orchestration step to call xID UserInfo endpoint to return claims about the authenticated user `X-ID-Userdata`.
 
 The following XML demonstrates the user journey orchestration with xID identity provider.
@@ -245,7 +245,7 @@ The following XML demonstrates the user journey orchestration with xID identity
 
         <OrchestrationStep Order="2" Type="ClaimsExchange">
           <ClaimsExchanges>
-            <ClaimsExchange Id="X-IDExchange" TechnicalProfileReferenceId="X-ID-Oauth2" />
+            <ClaimsExchange Id="X-IDExchange" TechnicalProfileReferenceId="X-ID-OIDC" />
           </ClaimsExchanges>
         </OrchestrationStep>
 

articles/active-directory/cloud-infrastructure-entitlement-management/TOC.yml

@@ -1,9 +1,9 @@
-  - name: Permissions Management
+  - name: Microsoft Entra Permissions Management
     href: index.yml
   - name: Overview
     expanded: true
     items:
-      - name: What's Permissions Management?
+      - name: What's Microsoft Entra Permissions Management?
         href: overview.md       
   - name: How-to guides
     expanded: true

articles/active-directory/cloud-infrastructure-entitlement-management/index.yml

@@ -1,10 +1,10 @@
 ### YamlMime:Landing
 
-title: Permissions Management
-summary: Permissions Management is a cloud infrastructure entitlement management (CIEM) solution that provides comprehensive visibility into permissions assigned to all identities (users and workloads),  actions, and resources across cloud infrastructures. It detects, right-sizes, and monitors unused and excessive permissions and enables Zero Trust security through least privilege access in Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).
+title: Microsoft Entra Permissions Management
+summary: Microsoft Entra Permissions Management is a cloud infrastructure entitlement management (CIEM) solution that provides comprehensive visibility into permissions assigned to all identities (users and workloads),  actions, and resources across cloud infrastructures. It detects, right-sizes, and monitors unused and excessive permissions and enables Zero Trust security through least privilege access in Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).
 
 metadata:
-  title: Permissions Management
+  title: Microsoft Entra Permissions Management
   description: Learn how to use Permissions Management and Cloud Infrastructure Entitlement Management (CIEM)
   services: active-directory
   author: jenniferf-skc
@@ -13,7 +13,7 @@ metadata:
   ms.subservice: ciem
   ms.workload: identity
   ms.topic: landing-page
-  ms.date: 03/09/2022
+  ms.date: 06/16/2023
   ms.author: jfields
 
 
@@ -24,7 +24,7 @@ landingContent:
 # Cards and links should be based on top customer tasks or top subjects
 # Start card title with a verb
   # Card
-  - title: What's Permissions Management?
+  - title: What's Microsoft Entra Permissions Management?
     linkLists:
       - linkListType: overview
         links:

articles/active-directory/cloud-infrastructure-entitlement-management/onboard-enable-tenant.md

@@ -8,13 +8,13 @@ ms.service: active-directory
 ms.subservice: ciem
 ms.workload: identity
 ms.topic: how-to
-ms.date: 04/24/2023
+ms.date: 06/16/2023
 ms.author: jfields
 ---
 
-# Enable Permissions Management in your organization
+# Enable Microsoft Entra Permissions Management in your organization
 
-This article describes how to enable Permissions Management in your organization. Once you've enabled Permissions Management, you can connect it to your Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP) platforms.
+This article describes how to enable Microsoft Entra Permissions Management in your organization. Once you've enabled Permissions Management, you can connect it to your Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP) platforms.
 
 > [!NOTE]
 > To complete this task, you must have *Microsoft Entra Permissions Management Administrator* permissions. You can't enable Permissions Management as a user from another tenant who has signed in via B2B or via Azure Lighthouse.

articles/active-directory/cloud-infrastructure-entitlement-management/overview.md

@@ -8,15 +8,15 @@ ms.service: active-directory
 ms.subservice: ciem
 ms.workload: identity
 ms.topic: overview
-ms.date: 04/20/2022
+ms.date: 06/16/2023
 ms.author: jfields
 ---
 
-# What's Permissions Management?
+# What's Microsoft Entra Permissions Management?
 
 ## Overview
 
-Permissions Management is a cloud infrastructure entitlement management (CIEM) solution that provides comprehensive visibility into permissions assigned to all identities. For example, over-privileged workload and user identities, actions, and resources across multicloud infrastructures in Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).
+Microsoft Entra Permissions Management is a cloud infrastructure entitlement management (CIEM) solution that provides comprehensive visibility into permissions assigned to all identities. For example, over-privileged workload and user identities, actions, and resources across multicloud infrastructures in Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).
 
 Permissions Management  detects, automatically right-sizes, and continuously monitors unused and excessive permissions.
 
@@ -70,5 +70,6 @@ Once your organization has explored and implemented the discover, remediation an
 
 ## Next steps
 
-- For information on how to onboard Permissions Management for your organization, see [Enable Permissions Management in your organization](onboard-enable-tenant.md).
+- Deepen your learning with the [Introduction to Microsoft Entra Permissions Management](https://go.microsoft.com/fwlink/?linkid=2240016) learn module. 
+- Sign up for a [45-day free trial](https://aka.ms/TryPermissionsManagement) of Permissions Management.
 - For a list of frequently asked questions (FAQs) about Permissions Management, see [FAQs](faqs.md).

articles/active-directory/conditional-access/concept-token-protection.md

@@ -50,6 +50,7 @@ This preview supports the following configurations:
 - The following Windows client devices aren't supported:
    - Windows Server 
    - Surface Hub
+   - Windows-based Microsoft Teams Rooms (MTR) systems
 
 ## Deployment
 

articles/active-directory/devices/howto-vm-sign-in-azure-ad-windows.md

@@ -267,7 +267,7 @@ To connect to the remote computer:
 > [!IMPORTANT]
 > Remote connection to VMs that are joined to Azure AD is allowed only from Windows 10 or later PCs that are either Azure AD registered (minimum required build is 20H1) or Azure AD joined or hybrid Azure AD joined to the *same* directory as the VM. Additionally, to RDP by using Azure AD credentials, users must belong to one of the two Azure roles, Virtual Machine Administrator Login or Virtual Machine User Login. 
 >
-> If you're using an Azure AD-registered Windows 10 or later PC, you must enter credentials in the `AzureAD\UPN` format (for example, `AzureAD\[email protected]`). At this time, you can use Azure Bastion to log in with Azure AD authentication [via the Azure CLI and the native RDP client mstsc](../../bastion/connect-native-client-windows.md). 
+> If you're using an Azure AD-registered Windows 10 or later PC, you must enter credentials in the `AzureAD\UPN` format (for example, `AzureAD\[email protected]`). At this time, you can use Azure Bastion to log in with Azure AD authentication [via the Azure CLI and the native RDP client mstsc](../../bastion/native-client.md). 
 
 
 To log in to your Windows Server 2019 virtual machine by using Azure AD: