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

Author: gitName

.openpublishing.redirection.json

@@ -3209,6 +3209,11 @@
       "redirect_url": "/azure/api-management/monitor-api-management",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/api-management/api-management-key-concepts-experiment.md",
+      "redirect_url": "/azure/api-management/api-management-key-concepts",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/vpn-gateway/vpn-gateway-cross-premises-options.md",
       "redirect_url": "/previous-versions/azure/vpn-gateway/vpn-gateway-about-vpn-gateway-settings",
@@ -6060,9 +6065,9 @@
       "redirect_document_id": false
     },
     {
-      "source_path_from_root": "/articles/reliability/reliability-postgre-flexible.md",
-      "redirect_url": "/azure/reliability/reliability-postgresql-flexible-server",
-      "redirect_document_id": false
+      "source_path_from_root": "/articles/reliability/reliability-postgresql-flexible-server.md",
+      "redirect_url": "/azure/reliability/reliability-azure-database-postgresql",
+      "redirect_document_id": true
     },
     {
       "source_path_from_root": "/articles/remote-rendering/tutorials/unity/changing-environment-and-materials.md",
@@ -7915,8 +7920,8 @@
       "redirect_document_id": false
     },
     {
-      "source_path": "articles/reliability/reliability-event-hubs.md",
-      "redirect_url": "/azure/event-hubs/event-hubs-business-continuity-outages-disasters",
+      "source_path": "articles/event-hubs/event-hubs-business-continuity-outages-disasters.md",
+      "redirect_url": "/azure/reliability/reliability-event-hubs",
       "redirect_document_id": false
     },
     {
@@ -7934,9 +7939,5 @@
       "redirect_url": "/azure/iot-hub-device-update/",
       "redirect_document_id": false
     }
-
-
-
-    
   ]
 }

articles/active-directory-b2c/partner-grit-app-proxy.md

@@ -18,7 +18,7 @@ ms.subservice: b2c
 
 [!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
-In this sample tutorial, learn how to migrate a legacy application using header-based authentication to Azure Active Directory B2C (Azure AD B2C) with [Grit's app proxy](https://www.gritiam.com/appProxy.html).
+In this sample tutorial, learn how to migrate a legacy application using header-based authentication to Azure Active Directory B2C (Azure AD B2C) with [Grit's app proxy](https://www.gritiam.com/grit_legacy_app_proxy.html).
 
 Benefits of using Grit's app proxy are as follows:
 
@@ -122,7 +122,7 @@ From the list, select the IdP.
 
 ## Additional resources
 
-- [Grit app proxy documentation](https://www.gritiam.com/appProxy.html)
+- [Grit app proxy documentation](https://www.gritiam.com/grit_legacy_app_proxy.html)
 
 - [Configure the Grit IAM B2B2C solution with Azure AD B2C](partner-grit-iam.md)
 

articles/active-directory-b2c/partner-grit-editor.md

@@ -19,7 +19,7 @@ ms.subservice: b2c
 
 [!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
-[Grit Software Systems Visual Identity Experience Framework (IEF) Editor](https://www.gritiam.com/iefeditor.html), is a tool that saves time during Azure Active Directory B2C (Azure AD B2C) authentication deployment. It supports multiple languages without the need to write code. It also has a no code debugger for user journeys.
+[Grit Software Systems Visual Identity Experience Framework (IEF) Editor](https://www.gritiam.com/visual_authentication.html), is a tool that saves time during Azure Active Directory B2C (Azure AD B2C) authentication deployment. It supports multiple languages without the need to write code. It also has a no code debugger for user journeys.
 
 Use the Visual IEF Editor to:
 

articles/active-directory-b2c/partner-grit-iam.md

@@ -18,7 +18,7 @@ ms.subservice: b2c
 
 [!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
-In this tutorial, you learn how to integrate Azure Active Directory B2C (Azure AD B2C) authentication with a [Grit IAM B2B2C](https://www.gritiam.com/b2b2c.html) solution. You can use the solution to provide secure, reliable, self-serviceable, and user-friendly identity and access management to your customers. Shared profile data such as first name, last name, home address, and email used in web and mobile applications are stored in a centralized manner with consideration to compliance and regulatory needs.
+In this tutorial, you learn how to integrate Azure Active Directory B2C (Azure AD B2C) authentication with a [Grit IAM B2B2C](https://www.gritiam.com/IAM_solution_for_B2B2C.html) solution. You can use the solution to provide secure, reliable, self-serviceable, and user-friendly identity and access management to your customers. Shared profile data such as first name, last name, home address, and email used in web and mobile applications are stored in a centralized manner with consideration to compliance and regulatory needs.
 
 
 Use Grit's B2BB2C solution for:
@@ -30,7 +30,7 @@ Use Grit's B2BB2C solution for:
 
 To get started, ensure the following prerequisites are met:
 
-- A Grit IAM account. You can go to [Grit IAM B2B2C solution](https://www.gritiam.com/b2b2c.html) to get a demo.
+- A Grit IAM account. You can go to [Grit IAM B2B2C solution](https://www.gritiam.com/IAM_solution_for_B2B2C.html) to get a demo.
 - A Microsoft Entra subscription. If you don't have one, you can create a [free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 - An Azure AD B2C tenant linked to the Azure subscription. You can learn more at [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md). 
 - Configure your application in the Azure portal. 

articles/api-center/.openpublishing.redirection.json

@@ -4,7 +4,21 @@
             "source_path_from_root": "/articles/api-center/use-vscode-extension.md",
             "redirect_url": "/azure/api-center/build-register-apis-vscode-extension",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/api-center/add-metadata-properties.md",
+            "redirect_url": "tutorials/add-metadata-properties",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/api-center/configure-environments-deployments.md",
+            "redirect_url": "tutorials/configure-environments-deployments",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/api-center/register-apis.md",
+            "redirect_url": "tutorials/register-apis",
+            "redirect_document_id": true
         }
-
     ]
 }

articles/api-center/TOC.yml

@@ -28,11 +28,11 @@
   - name: Tutorials
     items:
     - name: 1 - Define custom metadata
-      href: add-metadata-properties.md
+      href: ./tutorials/add-metadata-properties.md
     - name: 2 - Add APIs to the inventory
-      href: register-apis.md
+      href: ./tutorials/register-apis.md
     - name: 3 - Add environments and deployments
-      href: configure-environments-deployments.md
+      href: ./tutorials/configure-environments-deployments.md
   expanded: true
 - name: API inventory
   items:

articles/api-center/authorize-api-access.md

@@ -26,9 +26,9 @@ You can configure settings to authorize access to APIs in your [API center](over
 
 * An API center in your Azure subscription. If you haven't created one already, see [Quickstart: Create your API center](set-up-api-center.md).
 
-* Register at least one API in your API center. For more information, see [Tutorial: Register APIs in your API inventory](register-apis.md).
+* Register at least one API in your API center. For more information, see [Tutorial: Register APIs in your API inventory](./tutorials/register-apis.md).
 
-* Configure an environment and a deployment for the API. For more information, see [Tutorial: Add environments and deployments for APIs](configure-environments-deployments.md).
+* Configure an environment and a deployment for the API. For more information, see [Tutorial: Add environments and deployments for APIs](./tutorials/configure-environments-deployments.md).
 
 * Set up the API Center portal. For more information, see [Set up API Center portal](set-up-api-center-portal.md).
 

articles/api-center/enable-api-analysis-linting.md

@@ -293,7 +293,7 @@ Now create an event subscription in your API center to trigger the function app
 
 To test the event subscription, try uploading or updating an API definition file associated with an API version in your API center. For example, upload an OpenAPI or AsyncAPI document. After the event subscription is triggered, the function app invokes the API linting engine to analyze the API definition.
 
-* For detailed steps to add an API, API version, and API definition to your API center, see [Tutorial: Register APIs in your API center](register-apis.md).
+* For detailed steps to add an API, API version, and API definition to your API center, see [Tutorial: Register APIs in your API center](./tutorials/register-apis.md).
 * To create an API by uploading an API definition file using the Azure CLI, see [Register API from a specification file](manage-apis-azure-cli.md#register-api-from-a-specification-file---single-step).
 
 To confirm that the event subscription was triggered:

articles/api-center/export-to-copilot-studio.yml

@@ -26,7 +26,7 @@ prerequisites:
 
   dependencies:
     - An API center instance. You can [create one](set-up-api-center.md) in the Azure portal.
-    - An API registered in the API center inventory. The API must have a version associated with a [deployment](configure-environments-deployments.md), and it must have an API definition in OpenAPI 2.0 format.
+    - An API registered in the API center inventory. The API must have a version associated with a [deployment](./tutorials/configure-environments-deployments.md), and it must have an API definition in OpenAPI 2.0 format.
     - A Power Platform [environment](/power-apps/powerapps-overview#power-apps-for-admins).
     - A Microsoft Copilot Studio [license](/microsoft-copilot-studio/requirements-licensing-subscriptions).
 

articles/api-center/includes/api-center-portal-user-sign-in.md

@@ -16,7 +16,7 @@ To enable sign-in to the API Center portal to access APIs, assign the **Azure AP
 > [!IMPORTANT]
 > By default, you and other administrators of the API center must sign-in to access APIs in the API Center portal. Be sure to assign the **Azure API Center Data Reader** role to yourself and other administrators.  
 
-For detailed prerequisites and steps to assign a role to users and groups, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml). Brief steps follow:
+For detailed prerequisites and steps to assign a role to users and groups, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal). Brief steps follow:
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your API center.
 1. In the left menu, select **Access control (IAM)** > **+ Add role assignment**.