Merge pull request #306552 from jenniferf-skc/ARBACYmltoMD

[Azure RBAC] Updating YAML link path for refactoring

Author: v-shils

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

@@ -69,7 +69,7 @@ In summary, you'll use Azure Lighthouse to allow a user or group in your Azure A
 
 - An Azure AD B2C account with [Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator) role on the Azure AD B2C tenant.
 
--  A Microsoft Entra account with the [Owner](../role-based-access-control/built-in-roles.md#owner) role in the Microsoft Entra subscription. See how to [Assign a user as an administrator of an Azure subscription](../role-based-access-control/role-assignments-portal-subscription-admin.yml). 
+-  A Microsoft Entra account with the [Owner](../role-based-access-control/built-in-roles.md#owner) role in the Microsoft Entra subscription. See how to [Assign a user as an administrator of an Azure subscription](/azure/role-based-access-control/role-assignments-portal-subscription-admin). 
 
 ## 1. Create or choose resource group
 

articles/api-center/import-api-management-apis.md

@@ -199,5 +199,5 @@ After importing APIs from API Management, you can view and manage the imported A
 * [Azure CLI reference for Azure API Center](/cli/azure/apic)
 * [Azure CLI reference for API Management](/cli/azure/apim)
 * [Use the Azure CLI to manage your API inventory](manage-apis-azure-cli.md)
-* [Assign Azure roles to a managed identity](../role-based-access-control/role-assignments-portal-managed-identity.yml)
+* [Assign Azure roles to a managed identity](/azure/role-based-access-control/role-assignments-portal-managed-identity)
 * [Azure API Management documentation](../api-management/index.yml)

articles/api-center/includes/configure-managed-identity-apim-reader.md

@@ -11,7 +11,7 @@ ms.author: danlep
 ms.custom: Include file
 ---
 
-To allow import of APIs, assign your API center's managed identity the **API Management Service Reader** role in your API Management instance. You can use the [portal](../../role-based-access-control/role-assignments-portal-managed-identity.yml) or the Azure CLI.
+To allow import of APIs, assign your API center's managed identity the **API Management Service Reader** role in your API Management instance. You can use the [portal](/azure/role-based-access-control/role-assignments-portal-managed-identity) or the Azure CLI.
 
 #### [Portal](#tab/portal)
 

articles/api-center/includes/configure-managed-identity-kv-secret-user.md

@@ -11,7 +11,7 @@ ms.author: danlep
 ms.custom: Include file
 ---
 
-To allow import of APIs, assign your API center's managed identity the **Key Vault Secrets User** role in your Azure key vault. You can use the [portal](../../role-based-access-control/role-assignments-portal-managed-identity.yml) or the Azure CLI.
+To allow import of APIs, assign your API center's managed identity the **Key Vault Secrets User** role in your Azure key vault. You can use the [portal](/azure/role-based-access-control/role-assignments-portal-managed-identity) or the Azure CLI.
 
 #### [Portal](#tab/portal)
 

articles/application-gateway/configuration-infrastructure.md

@@ -73,7 +73,7 @@ When an instance of your Application Gateway issues a DNS query, it uses the val
 
 The Application Gateway resource is deployed inside a virtual network, so checks are also performed to verify the permission on the virtual network resource. This validation is performed during both creation and management operations and also applies to the [managed identities for Application Gateway Ingress Controller](./tutorial-ingress-controller-add-on-new.md#deploy-an-aks-cluster-with-the-add-on-enabled).
 
-Check your [Azure role-based access control](../role-based-access-control/role-assignments-list-portal.yml) to verify that the users and service principals that operate application gateways have at least the following permissions on the virtual network or subnet:
+Check your [Azure role-based access control](/azure/role-based-access-control/role-assignments-list-portal) to verify that the users and service principals that operate application gateways have at least the following permissions on the virtual network or subnet:
 - **Microsoft.Network/virtualNetworks/subnets/join/action** 
 - **Microsoft.Network/virtualNetworks/subnets/read**
 
@@ -264,4 +264,4 @@ To view roles and permissions for other services, see the following links:
 - [Learn about frontend IP address configuration](configuration-frontend-ip.md)
 - [Learn about private Application Gateway deployment](application-gateway-private-deployment.md)
 - [What is Azure Role Based Access](../role-based-access-control/overview.md)
-- [Azure Role Based Access Control](../role-based-access-control/role-assignments-list-portal.yml)
+- [Azure Role Based Access Control](/azure/role-based-access-control/role-assignments-list-portal)

articles/azure-resource-manager/management/move-resource-group-and-subscription.md

@@ -117,7 +117,7 @@ Some important steps precede moving a resource. You can avoid errors if you veri
 
 1. If you move a resource with an active Azure role assignment (or its child resource with this same assignment), the role assignment doesn't move and becomes orphaned. You must create the role assignment again after the move. Although the system automatically removes the orphaned role assignment, we recommend that you remove it before the move.
 
-    To learn more about how to manage role assignments, see [List Azure role assignments](../../role-based-access-control/role-assignments-list-portal.yml#list-role-assignments-at-a-scope) and [Assign Azure roles](../../role-based-access-control/role-assignments-portal.yml).
+    To learn more about how to manage role assignments, see [List Azure role assignments](/azure/role-based-access-control/role-assignments-list-portal#list-role-assignments-at-a-scope) and [Assign Azure roles](/azure/role-based-access-control/role-assignments-portal).
 
 1. **For a move across subscriptions, the resource and its dependent resources must be located in the same resource group and they must be moved together.** For example, a virtual machine with managed disks requires you to move the virtual machine, managed disks, and other dependent resources together.
 

articles/communication-services/quickstarts/manage-teams-identity.md

@@ -93,7 +93,7 @@ The following roles can provide consent on behalf of a company:
 - Application admin
 - Cloud application admin
 
-If you want to check roles in Azure portal, see [List Azure role assignments](../../role-based-access-control/role-assignments-list-portal.yml).
+If you want to check roles in Azure portal, see [List Azure role assignments](/azure/role-based-access-control/role-assignments-list-portal).
 
 To construct an Administrator consent URL, the Fabrikam Microsoft Entra Administrator does the following steps:
 

articles/data-factory/how-to-use-sql-managed-instance-with-ir.md

@@ -71,7 +71,7 @@ You can now move your SQL Server Integration Services (SSIS) projects, packages,
 
 ### Configure virtual network
 
-1. **User permission**. The user who creates the Azure-SSIS IR must have the [role assignment](../role-based-access-control/role-assignments-list-portal.yml#list-role-assignments-for-a-user-at-a-scope) at least on Azure Data Factory resource with one of the options below:
+1. **User permission**. The user who creates the Azure-SSIS IR must have the [role assignment](/azure/role-based-access-control/role-assignments-list-portal#list-role-assignments-for-a-user-at-a-scope) at least on Azure Data Factory resource with one of the options below:
 
     - Use the built-in Network Contributor role. This role comes with the _Microsoft.Network/\*_ permission, which has a much larger scope than necessary.
     - Create a custom role that includes only the necessary _Microsoft.Network/virtualNetworks/\*/join/action_ permission. If you also want to bring your own public IP addresses for Azure-SSIS IR while joining it to an Azure Resource Manager virtual network, also include _Microsoft.Network/publicIPAddresses/*/join/action_ permission in the role.

articles/defender-for-iot/organizations/manage-users-portal.md

@@ -59,7 +59,7 @@ For more information, see:
 
 - [Azure user roles and permissions for Defender for IoT](roles-azure.md)
 - [Grant a user access to Azure resources using the Azure portal](../../role-based-access-control/quickstart-assign-role-user-portal.md)
-- [List Azure role assignments using the Azure portal](../../role-based-access-control/role-assignments-list-portal.yml)
+- [List Azure role assignments using the Azure portal](/azure/role-based-access-control/role-assignments-list-portal)
 - [Check access for a user to Azure resources](../../role-based-access-control/check-access.md)
 
 ## Next steps

articles/expressroute/roles-permissions.md

@@ -77,4 +77,4 @@ To view roles and permissions for other services, see the following links:
 ## Next steps
 
 [What is Azure Role Based Access](../role-based-access-control/overview.md)
-[Azure Role Based Access Control](../role-based-access-control/role-assignments-list-portal.yml)
+[Azure Role Based Access Control](/azure/role-based-access-control/role-assignments-list-portal)