Skip to content

Commit 35978da

Browse files
authored
Merge pull request #307258 from jenniferf-skc/ARBACYmltoMD-4
[BULK Update] Updating link paths for YML to Markdown conversion. role-assignment-portal.yml
2 parents 9f3903d + 65d4729 commit 35978da

74 files changed

Lines changed: 94 additions & 95 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

articles/api-management/api-management-howto-app-insights.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ You can easily integrate Azure Application Insights with Azure API Management. A
4545

4646
* If you enable a user-assigned managed identity, take note of the identity's **Client ID**.
4747

48-
1. Assign the identity the **Monitoring Metrics Publisher** role, scoped to the Application Insights resource. To assign the role, use the [Azure portal](../role-based-access-control/role-assignments-portal.yml) or other Azure tools.
48+
1. Assign the identity the **Monitoring Metrics Publisher** role, scoped to the Application Insights resource. To assign the role, use the [Azure portal](/azure/role-based-access-control/role-assignments-portal) or other Azure tools.
4949

5050
## Scenario overview
5151

articles/api-management/api-management-howto-disaster-recovery-backup-restore.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Azure generates two 512-bit storage account access keys for each storage account
6565

6666
* If you enable a user-assigned managed identity, take note of the identity's **Client ID**.
6767
* If you will back up and restore to different API Management instances, enable a managed identity in both the source and target instances.
68-
1. Assign the identity the **Storage Blob Data Contributor** role, scoped to the storage account used for backup and restore. To assign the role, use the [Azure portal](../role-based-access-control/role-assignments-portal.yml) or other Azure tools.
68+
1. Assign the identity the **Storage Blob Data Contributor** role, scoped to the storage account used for backup and restore. To assign the role, use the [Azure portal](/azure/role-based-access-control/role-assignments-portal) or other Azure tools.
6969

7070

7171
## Back up an API Management service

articles/api-management/api-management-howto-log-event-hubs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ To log events to the event hub, you need to configure credentials for access fro
4646

4747
* If you enable a user-assigned managed identity, take note of the identity's **Object ID**.
4848

49-
1. Assign the identity the **Azure Event Hubs Data sender** role, scoped to the Event Hubs namespace or to the event hub used for logging. To assign the role, use the [Azure portal](../role-based-access-control/role-assignments-portal.yml) or another Azure tool.
49+
1. Assign the identity the **Azure Event Hubs Data sender** role, scoped to the Event Hubs namespace or to the event hub used for logging. To assign the role, use the [Azure portal](/azure/role-based-access-control/role-assignments-portal) or another Azure tool.
5050

5151

5252
### Option 2: Configure an Event Hubs connection string

articles/api-management/api-management-howto-send-service-bus.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ To send messages to the service bus, you need to configure a managed identity fo
5555

5656
* If you enable a user-assigned managed identity, take note of the identity's **Client ID**.
5757

58-
1. Assign the identity the **Azure Service Bus Data Sender** role, scoped to the service bus. To assign the role, use the [Azure portal](../role-based-access-control/role-assignments-portal.yml) or other Azure tools.
58+
1. Assign the identity the **Azure Service Bus Data Sender** role, scoped to the service bus. To assign the role, use the [Azure portal](/azure/role-based-access-control/role-assignments-portal) or other Azure tools.
5959

6060
## Configure send-service-bus-message policy
6161

articles/api-management/api-management-role-based-access-control.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Azure API Management relies on Azure role-based access control (Azure RBAC) to e
2323

2424
API Management currently provides three built-in service roles. These roles can be assigned at different scopes, including subscription, resource group, and individual API Management instance. For instance, if you assign the "API Management Service Reader" role to a user at the resource-group level, then the user has read access to all API Management instances inside the resource group.
2525

26-
The following table provides brief descriptions of the built-in roles. You can assign these roles by using the Azure portal or other tools, including Azure [PowerShell](../role-based-access-control/role-assignments-powershell.md), [Azure CLI](../role-based-access-control/role-assignments-cli.md), and [REST API](../role-based-access-control/role-assignments-rest.md). For details about how to assign built-in roles, see [Assign Azure roles to manage access to your Azure subscription resources](../role-based-access-control/role-assignments-portal.yml).
26+
The following table provides brief descriptions of the built-in roles. You can assign these roles by using the Azure portal or other tools, including Azure [PowerShell](../role-based-access-control/role-assignments-powershell.md), [Azure CLI](../role-based-access-control/role-assignments-cli.md), and [REST API](../role-based-access-control/role-assignments-rest.md). For details about how to assign built-in roles, see [Assign Azure roles to manage access to your Azure subscription resources](/azure/role-based-access-control/role-assignments-portal).
2727

2828
| Role | Read access<sup>[1]</sup> | Write access<sup>[2]</sup> | Service creation, deletion, scaling, VPN, and custom domain configuration | Access to the legacy publisher portal | Description
2929
| ------------- | ---- | ---- | ---- | ---- | ----
@@ -87,6 +87,6 @@ The [Azure Resource Manager resource provider operations](../role-based-access-c
8787

8888
To learn more about role-based access control in Azure, see the following articles:
8989
* [Get started with access management in the Azure portal](../role-based-access-control/overview.md)
90-
* [Assign Azure roles to manage access to your Azure subscription resources](../role-based-access-control/role-assignments-portal.yml)
90+
* [Assign Azure roles to manage access to your Azure subscription resources](/azure/role-based-access-control/role-assignments-portal)
9191
* [Custom roles in Azure RBAC](../role-based-access-control/custom-roles.md)
9292
* [Azure Resource Manager resource provider operations](../role-based-access-control/resource-provider-operations.md#microsoftapimanagement)

articles/api-management/how-to-create-workspace.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ To manage the workspace gateway, we recommend also assigning workspace users an
8080
>
8181
8282
* For a list of built-in workspace roles, see [How to use role-based access control in API Management](api-management-role-based-access-control.md).
83-
* For steps to assign a role, see [Assign Azure roles using the portal](../role-based-access-control/role-assignments-portal.yml?tabs=current).
83+
* For steps to assign a role, see [Assign Azure roles using the portal](/azure/role-based-access-control/role-assignments-portal?tabs=current).
8484

8585

8686
### Assign a service-scoped role

articles/api-management/self-hosted-gateway-enable-azure-ad.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ When configuring the custom roles, update the [`AssignableScopes`](../role-based
9999

100100
### Assign API Management Configuration API Access Validator Service Role
101101

102-
Assign the API Management Configuration API Access Validator Service Role to the managed identity of the API Management instance. For detailed steps to assign a role, see [Assign Azure roles using the portal](../role-based-access-control/role-assignments-portal.yml).
102+
Assign the API Management Configuration API Access Validator Service Role to the managed identity of the API Management instance. For detailed steps to assign a role, see [Assign Azure roles using the portal](/azure/role-based-access-control/role-assignments-portal).
103103

104104
- Scope: The resource group or subscription in which the API Management instance is deployed
105105
- Role: API Management Configuration API Access Validator Service Role

articles/app-service/includes/tutorial-dotnet-storage-managed-identity/introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,7 @@ You need to grant your web app access to the storage account before you can crea
180180

181181
In the [Azure portal](https://portal.azure.com), go into your storage account to grant your web app access. Select **Access control (IAM)** in the left pane, and then select **Role assignments**. You'll see a list of who has access to the storage account. Now you want to add a role assignment to a robot, the app service that needs access to the storage account. Select **Add** > **Add role assignment** to open the **Add role assignment** page.
182182

183-
Assign the **Storage Blob Data Contributor** role to the **App Service** at subscription scope. For detailed steps, see [Assign Azure roles using the Azure portal](../../../role-based-access-control/role-assignments-portal.yml).
183+
Assign the **Storage Blob Data Contributor** role to the **App Service** at subscription scope. For detailed steps, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
184184

185185
Your web app now has access to your storage account.
186186

articles/automanage/repair-automanage-account.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ If you're using an ARM template or the Azure CLI, you'll need the Principal ID (
7878

7979
1. Select **Add** > **Add role assignment** to open the **Add role assignment** page.
8080

81-
1. Assign the following role. For detailed steps, see [Assign Azure roles using the Azure portal](../role-based-access-control/role-assignments-portal.yml).
81+
1. Assign the following role. For detailed steps, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
8282

8383
| Setting | Value |
8484
| ---------------- | ---------------------------------- |

articles/automation/add-user-assigned-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -297,7 +297,7 @@ Before you can use your user-assigned managed identity for authentication, set u
297297
298298
Follow the principal of least privilege and carefully assign permissions only required to execute your runbook. For example, if the Automation account is only required to start or stop an Azure VM, then the permissions assigned to the Run As account or managed identity needs to be only for starting or stopping the VM. Similarly, if a runbook is reading from blob storage, then assign read only permissions.
299299
300-
This example uses Azure PowerShell to show how to assign the Contributor role in the subscription to the target Azure resource. The Contributor role is used as an example and may or may not be required in your case. Alternatively, you can also assign the role to the target Azure resource in the [Azure portal](../role-based-access-control/role-assignments-portal.yml).
300+
This example uses Azure PowerShell to show how to assign the Contributor role in the subscription to the target Azure resource. The Contributor role is used as an example and may or may not be required in your case. Alternatively, you can also assign the role to the target Azure resource in the [Azure portal](/azure/role-based-access-control/role-assignments-portal).
301301
302302
```powershell
303303
New-AzRoleAssignment `

0 commit comments

Comments
 (0)