Skip to content

Commit 9cab075

Browse files
committed
route server
1 parent eeec571 commit 9cab075

File tree

3 files changed

+63
-1
lines changed

3 files changed

+63
-1
lines changed

articles/route-server/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,8 @@
4343
href: route-injection-in-spokes.md
4444
- name: IP anycast
4545
href: anycast.md
46+
- name: Roles and permissions
47+
href: roles-permissions.md
4648
- name: How-to guides
4749
items:
4850
- name: Configure and manage Route Server
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: About route server roles and permissions
3+
description: Learn about roles and permissions for Azure Route Server
4+
author: siddomala
5+
ms.author: halkazwini
6+
ms.service: azure-route-server
7+
ms.topic: conceptual
8+
ms.date: cherylmc
9+
---
10+
11+
---
12+
# About roles and permissions for the Virtual WAN Hub
13+
14+
Azure Route Server utilizes multiple underlying resources during both creation and management operations.
15+
Because of this, it's essential to verify permissions on all involved resources during these operations.
16+
17+
## Azure built-in roles
18+
19+
You can choose to assign [Azure built-in roles](../role-based-access-control/built-in-roles.md) to a user, group, service principal, or managed identity such as [Network contributor](../role-based-access-control/built-in-roles.md#network-contributor), which support all the required permissions for creating the gateway.
20+
For more information, see [Steps to assign an Azure role](../role-based-access-control/role-assignments-steps.md).
21+
22+
## Custom roles
23+
24+
If the [Azure built-in roles](../role-based-access-control/built-in-roles.md) don't meet the specific needs of your organization, you can create your own custom roles.
25+
Just like built-in roles, you can assign custom roles to users, groups, and service principals at management group, subscription, and resource group scopes.
26+
For more information, see [Steps to create a custom role](../role-based-access-control/custom-roles.md#steps-to-create-a-custom-role) .
27+
28+
To ensure proper functionality, check your custom role permissions to confirm user service principals, and managed identities operating the VPN gateway have the necessary permissions.
29+
To add any missing permissions listed here, see [Update a custom role](../role-based-access-control/custom-roles-portal.md#update-a-custom-role).
30+
31+
## Permissions
32+
33+
Depending on whether you're creating new resources or using existing ones, add the appropriate permissions from the following list:
34+
35+
|Resource | Resource status | Required Azure permissions |
36+
|---|---|---|
37+
| Subnet | Create new| Microsoft.Network/virtualNetworks/subnets/write<br>Microsoft.Network/virtualNetworks/subnets/join/action |
38+
| Subnet | Use existing| Microsoft.Network/virtualNetworks/subnets/read<br>Microsoft.Network/virtualNetworks/subnets/join/action |
39+
| IP addresses| Create new| Microsoft.Network/publicIPAddresses/write<br>Microsoft.Network/publicIPAddresses/join/action |
40+
| IP addresses | Use existing| Microsoft.Network/publicIPAddresses/read<br>Microsoft.Network/publicIPAddresses/join/action |
41+
42+
For more information, see [Azure permissions for Networking](../role-based-access-control/permissions/networking.md) and [Virtual network permissions](../virtual-network/virtual-network-manage-subnet.md#permissions).
43+
44+
## Roles scope
45+
46+
In the process of custom role definition, you can specify a role assignment scope at four levels: management group, subscription, resource group, and resources. To grant access, you assign roles to users, groups, service principals, or managed identities at a particular scope.
47+
48+
These scopes are structured in a parent-child relationship, with each level of hierarchy making the scope more specific. You can assign roles at any of these levels of scope, and the level you select determines how widely the role is applied.
49+
50+
For example, a role assigned at the subscription level can cascade down to all resources within that subscription, while a role assigned at the resource group level will only apply to resources within that specific group. Learn more about scope level
51+
For more information, see [Scope levels](../role-based-access-control/scope-overview.md#scope-levels).
52+
53+
> [!NOTE]
54+
> Allow sufficient time for [Azure Resource Manager cache](../role-based-access-control/troubleshooting.md) to refresh after role assignment changes.
55+
56+
## Next steps
57+
58+
- [What is Azure Role Based Access](../role-based-access-control/overview.md)
59+
60+
- [Azure Role Based Access Control](../role-based-access-control/role-assignments-list-portal.yml)

articles/virtual-wan/roles-permissions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: About virtual hub roles and permissions
33
titleSuffix: Virtual Hub
4-
description: Learn about roles and permissions for Virtual WAN Hub.
4+
description: Learn about roles and permissions for a Virtual WAN Hub.
55
author: siddomala
66
ms.service: azure-virtual-wan
77
ms.topic: conceptual

0 commit comments

Comments
 (0)