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

Author: Karthigasree

.openpublishing.redirection.active-directory.json

@@ -10,6 +10,176 @@
       "redirect_url": "/azure/active-directory/develop/enterprise-app-role-management",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/global-secure-access/concept-global-secure-access-logs-monitoring.md",
+      "redirect_url": "/entra/global-secure-access/concept-global-secure-access-logs-monitoring",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/concept-private-access.md",
+      "redirect_url": "/entra/global-secure-access/concept-private-access",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/concept-remote-network-connectivity.md",
+      "redirect_url": "/entra/global-secure-access/concept-remote-network-connectivity",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/concept-traffic-dashboard.md",
+      "redirect_url": "/entra/global-secure-access/concept-traffic-dashboard",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/concept-traffic-forwarding.md",
+      "redirect_url": "/entra/global-secure-access/concept-traffic-forwarding",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/concept-universal-conditional-access.md",
+      "redirect_url": "/entra/global-secure-access/concept-universal-conditional-access",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-access-audit-logs.md",
+      "redirect_url": "/entra/global-secure-access/how-to-access-audit-logs",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-assign-traffic-profile-to-remote-network.md",
+      "redirect_url": "/entra/global-secure-access/how-to-assign-traffic-profile-to-remote-network",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-compliant-network.md",
+      "redirect_url": "/entra/global-secure-access/how-to-compliant-network",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-configure-connectors.md",
+      "redirect_url": "/entra/global-secure-access/how-to-configure-connectors",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-configure-customer-premises-equipment.md",
+      "redirect_url": "/entra/global-secure-access/how-to-configure-customer-premises-equipment",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-configure-per-app-access.md",
+      "redirect_url": "/entra/global-secure-access/how-to-configure-per-app-access",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-configure-quick-access.md",
+      "redirect_url": "/entra/global-secure-access/how-to-configure-quick-access",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-create-remote-network-custom-ike-policy.md",
+      "redirect_url": "/entra/global-secure-access/how-to-create-remote-network-custom-ike-policy",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-create-remote-networks.md",
+      "redirect_url": "/entra/global-secure-access/how-to-create-remote-networks",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-get-started-with-global-secure-access.md",
+      "redirect_url": "/entra/global-secure-access/how-to-get-started-with-global-secure-access",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-install-windows-client.md",
+      "redirect_url": "/entra/global-secure-access/how-to-install-windows-client",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-list-remote-networks.md",
+      "redirect_url": "/entra/global-secure-access/how-to-list-remote-networks",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-manage-microsoft-365-profile.md",
+      "redirect_url": "/entra/global-secure-access/how-to-manage-microsoft-365-profile",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-manage-private-access-profile.md",
+      "redirect_url": "/entra/global-secure-access/how-to-manage-private-access-profile",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-manage-remote-network-device-links.md",
+      "redirect_url": "/entra/global-secure-access/how-to-manage-remote-network-device-links",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-manage-remote-networks.md",
+      "redirect_url": "/entra/global-secure-access/how-to-manage-remote-networks",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-simulate-remote-network.md",
+      "redirect_url": "/entra/global-secure-access/how-to-simulate-remote-network",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-source-ip-restoration.md",
+      "redirect_url": "/entra/global-secure-access/how-to-source-ip-restoration",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-target-resource-microsoft-365-profile.md",
+      "redirect_url": "/entra/global-secure-access/how-to-target-resource-microsoft-365-profile",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-target-resource-private-access-apps.md",
+      "redirect_url": "/entra/global-secure-access/how-to-target-resource-private-access-apps",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-universal-tenant-restrictions.md",
+      "redirect_url": "/entra/global-secure-access/how-to-universal-tenant-restrictions",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-view-enriched-logs.md",
+      "redirect_url": "/entra/global-secure-access/how-to-view-enriched-logs",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/how-to-view-traffic-logs.md",
+      "redirect_url": "/entra/global-secure-access/how-to-view-traffic-logs",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/index.yml",
+      "redirect_url": "/entra/global-secure-access/index",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/overview-what-is-global-secure-access.md",
+      "redirect_url": "/entra/global-secure-access/overview-what-is-global-secure-access",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/reference-points-of-presence.md",
+      "redirect_url": "/entra/global-secure-access/reference-points-of-presence",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/reference-remote-network-configurations.md",
+      "redirect_url": "/entra/global-secure-access/reference-remote-network-configurations",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/global-secure-access/resource-faq.yml",
+      "redirect_url": "/entra/global-secure-access/resource-faq",
+      "redirect_document_id": true
+    },
     {
       "source_path_from_root": "/articles/active-directory/governance/tutorial-prepare-azure-ad-user-accounts.md",
       "redirect_url": "/azure/active-directory/governance/tutorial-prepare-user-accounts",

CODEOWNERS

@@ -69,7 +69,7 @@ articles/service-health @rboucher
 /articles/lighthouse/ @JnHs
 
 # Healthcare APIs
-/articles/healthcare-apis/ @ranvijaykumar @mikaelweave
+/articles/healthcare-apis/ @ranvijaykumar @chachachachami
 
 # Configuration
 *.json @SyntaxC4 @snoviking

articles/active-directory-b2c/active-directory-technical-profile.md

@@ -20,14 +20,16 @@ ms.subservice: B2C
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
 
+<!-- docutune:ignored "AAD-" -->
+
 Azure Active Directory B2C (Azure AD B2C) provides support for the Microsoft Entra user management. This article describes the specifics of a technical profile for interacting with a claims provider that supports this standardized protocol.
 
 ## Protocol
 
 The **Name** attribute of the **Protocol** element needs to be set to `Proprietary`. The **handler** attribute must contain the fully qualified name of the protocol handler assembly `Web.TPEngine.Providers.AzureActiveDirectoryProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null`.
 
 Following [custom policy starter pack](tutorial-create-user-flows.md?pivots=b2c-custom-policy#custom-policy-starter-pack) Microsoft Entra technical profiles include the **AAD-Common** technical profile. The Microsoft Entra technical profiles don't specify the protocol because the protocol is configured in the **AAD-Common** technical profile:
- 
+
 - **AAD-UserReadUsingAlternativeSecurityId** and **AAD-UserReadUsingAlternativeSecurityId-NoError** - Look up a social account in the directory.
 - **AAD-UserWriteUsingAlternativeSecurityId** - Create a new social account.
 - **AAD-UserReadUsingEmailAddress** - Look up a local account in the directory.

articles/active-directory-b2c/azure-monitor.md

@@ -38,7 +38,7 @@ Watch this video to learn how to configure monitoring for Azure AD B2C using Azu
 
 ## Deployment overview
 
-Azure AD B2C uses [Microsoft Entra ID monitoring](../active-directory/reports-monitoring/overview-monitoring-health.md). Unlike Microsoft Entra tenants, an Azure AD B2C tenant can't have a subscription associated with it. So, we need to take extra steps to enable the integration between Azure AD B2C and Log Analytics, which is where we send the logs.
+Azure AD B2C uses [Microsoft Entra monitoring](../active-directory/reports-monitoring/overview-monitoring-health.md). Unlike Microsoft Entra tenants, an Azure AD B2C tenant can't have a subscription associated with it. So, we need to take extra steps to enable the integration between Azure AD B2C and Log Analytics, which is where we send the logs.
 To enable _Diagnostic settings_ in Microsoft Entra ID within your Azure AD B2C tenant, you use [Azure Lighthouse](../lighthouse/overview.md) to [delegate a resource](../lighthouse/concepts/architecture.md), which allows your Azure AD B2C (the **Service Provider**) to manage a Microsoft Entra ID (the **Customer**) resource.
 
 > [!TIP]
@@ -365,4 +365,4 @@ To stop collecting logs to your Log Analytics workspace, delete the diagnostic s
 
 - For more information about adding and configuring diagnostic settings in Azure Monitor, see [Tutorial: Collect and analyze resource logs from an Azure resource](../azure-monitor/essentials/monitor-azure-resource.md).
 
-- For information about streaming Microsoft Entra ID logs to an event hub, see [Tutorial: Stream Microsoft Entra ID logs to an Azure event hub](../active-directory/reports-monitoring/tutorial-azure-monitor-stream-logs-to-event-hub.md).
+- For information about streaming Microsoft Entra logs to an event hub, see [Tutorial: Stream Microsoft Entra logs to an Azure event hub](../active-directory/reports-monitoring/tutorial-azure-monitor-stream-logs-to-event-hub.md).

articles/active-directory-b2c/custom-policies-series-sign-up-or-sign-in.md

@@ -303,7 +303,7 @@ When the custom policy runs:
 - **Orchestration Step 4** - This step runs if the user signs up (objectId doesn't exist), so we display the sign-up form by invoking the
 *UserInformationCollector* self-asserted technical profile. This step runs whether a user signs up or signs in. 
 
-- **Orchestration Step 5** - This step reads account information from Microsoft Entra ID (we invoke *AAD-UserRead* Microsoft Entra technical profile), so it runs whether a user signs up or signs in.   
+- **Orchestration Step 5** - This step reads account information from Microsoft Entra ID (we invoke `AAD-UserRead` Microsoft Entra technical profile), so it runs whether a user signs up or signs in.
 
 - **Orchestration Step 6** -  This step invokes the *UserInputMessageClaimGenerator* technical profile to assemble the user’s greeting message.
 

articles/active-directory-b2c/customize-ui.md

@@ -231,7 +231,7 @@ If you'd like to brand all pages in the user flow, set the page layout version f
 
 ## Enable company branding in custom policy pages
 
-Once you've configured company branding, enable it in your custom policy. Configure the [page layout version](contentdefinitions.md#migrating-to-page-layout) with page `contract` version for *all* of the content definitions in your custom policy. The format of the value must contain the word `contract`: _urn:com:microsoft:aad:b2c:elements:**contract**:page-name:version_. To specify a page layout in your custom policies that use an old **DataUri** value. For more information, learn how to [migrate to page layout](contentdefinitions.md#migrating-to-page-layout) with page version.
+Once you've configured company branding, enable it in your custom policy. Configure the [page layout version](contentdefinitions.md#migrating-to-page-layout) with page `contract` version for *all* of the content definitions in your custom policy. The format of the value must contain the word `contract`: *urn:com:microsoft:aad:b2c:elements:**contract**:page-name:version*. To specify a page layout in your custom policies that use an old **DataUri** value. For more information, learn how to [migrate to page layout](contentdefinitions.md#migrating-to-page-layout) with page version.
 
 The following example shows the content definitions with their corresponding the page contract, and *Ocean Blue* page template: 
 

articles/active-directory-b2c/force-password-reset.md

@@ -149,7 +149,7 @@ Once a password expiration policy has been set, you must also configure force pa
 
 ### Password expiry duration
 
-By default, the password is set not to expire. However, the value is configurable by using the [Set-MsolPasswordPolicy](/powershell/module/msonline/set-msolpasswordpolicy) cmdlet from the Azure AD Module for Windows PowerShell. This command updates the tenant, so that all users' passwords expire after number of days you configure.
+By default, the password is set not to expire. However, the value is configurable by using the [Set-MsolPasswordPolicy](/powershell/module/msonline/set-msolpasswordpolicy) cmdlet from the Azure AD PowerShell module. This command updates the tenant, so that all users' passwords expire after number of days you configure.
 
 ## Next steps
 

articles/active-directory-b2c/javascript-and-page-layout.md

@@ -68,7 +68,7 @@ For information about the different page layout versions, see the [Page layout v
 To specify a page layout version for your custom policy pages:
 
 1. Select a [page layout](contentdefinitions.md#select-a-page-layout) for the user interface elements of your application.
-1. Define a [page layout version](contentdefinitions.md#migrating-to-page-layout) with page `contract` version for *all* of the content definitions in your custom policy. The format of the value must contain the word `contract`: _urn:com:microsoft:aad:b2c:elements:**contract**:page-name:version_. 
+1. Define a [page layout version](contentdefinitions.md#migrating-to-page-layout) with page `contract` version for *all* of the content definitions in your custom policy. The format of the value must contain the word `contract`: *urn:com:microsoft:aad:b2c:elements:**contract**:page-name:version*.
 
 The following example shows the content definition identifiers and the corresponding **DataUri** with page contract: 
 

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

@@ -287,4 +287,4 @@ For additional information, review the following articles:
 
 - [Azure AD B2C custom policy overview](custom-policy-overview.md)
 - [Tutorial: Create user flows and custom policies in Azure Active Directory B2C](tutorial-create-user-flows.md?pivots=b2c-custom-policy)
-- [TransmitSecurity/azure-ad-b2c-bindid-integration](https://github.com/TransmitSecurity/azure-ad-b2c-bindid-integration) See, Azure AD B2C Integration
+- [`TransmitSecurity/azure-ad-b2c-bindid-integration`](https://github.com/TransmitSecurity/azure-ad-b2c-bindid-integration) See, Azure AD B2C Integration

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

@@ -54,7 +54,7 @@ The following architecture diagram shows the implementation.
 
 ## Configure the Azure AD B2C policy
 
-1. Go to [Azure-AD-B2C-HYPR-Sample/policy/](https://github.com/HYPR-Corp-Public/Azure-AD-B2C-HYPR-Sample/tree/master/policy).
+1. Go to [`Azure-AD-B2C-HYPR-Sample/policy/`](https://github.com/HYPR-Corp-Public/Azure-AD-B2C-HYPR-Sample/tree/master/policy).
 
 2. Follow the instructions in [Custom policy starter pack](tutorial-create-user-flows.md?pivots=b2c-custom-policy#custom-policy-starter-pack) to download [Active-directory-b2c-custom-policy-starterpack/LocalAccounts/](https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/tree/master/LocalAccounts)
 3. Configure the policy for the Azure AD B2C tenant.