rough draft

Author: siddomala

articles/route-server/route-server-faq.md

@@ -42,7 +42,7 @@ Yes, if you peer a virtual network hosting the Azure Route Server to another vir
 These public endpoints are required for Azure's underlying SDN and management platform to communicate with Azure Route Server. Because Route Server is considered part of the customer's private network, Azure's underlying platform is unable to directly access and manage Route Server via its private endpoints due to compliance requirements. Connectivity to Route Server's public endpoints is authenticated via certificates, and Azure conducts routine security audits of these public endpoints. As a result, they do not constitute a security exposure of your virtual network.
 
 > [!NOTE]
-> Note: These certificates are signed by an internal certificate authority, so this certificate chain will appear to not be signed by a known trusted authority. As a result, this does not represent an SSL vulnerability.
+> These certificates are signed by an internal certificate authority, so this certificate chain will appear to not be signed by a known trusted authority. As a result, this does not represent an SSL vulnerability.
 >
 
 ### Does Azure Route Server support IPv6?

articles/virtual-wan/TOC.yml

@@ -128,6 +128,8 @@
       href: virtual-wan-expressroute-about.md
   - name: Virtual hub settings
     href: hub-settings.md
+  - name: Roles and permissions
+    href: roles-permissions.md
   - name: Gateway settings
     href: gateway-settings.md
   - name: Apply Zero Trust principles

articles/virtual-wan/roles-permissions.md

@@ -0,0 +1,60 @@
+---
+title: About virtual hub roles and permissions
+titleSuffix: Virtual Hub
+description: Learn about roles and permissions for Virtual WAN Hub.
+author: siddomala
+ms.service: azure-virtual-wan
+ms.topic: conceptual
+ms.date: 12/13/2024
+ms.author: cherylmc
+
+---
+# About roles and permissions for the Virtual WAN Hub
+
+The Virtual WAN hub utilizes multiple underlying resources during both creation and management operations.
+Because of this, it's essential to verify permissions on all involved resources during these operations.
+
+## Azure built-in roles
+
+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.
+For more information, see [Steps to assign an Azure role](../role-based-access-control/role-assignments-steps.md).
+
+## Custom roles
+
+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.
+Just like built-in roles, you can assign custom roles to users, groups, and service principals at management group, subscription, and resource group scopes.
+For more information, see [Steps to create a custom role](../role-based-access-control/custom-roles.md#steps-to-create-a-custom-role)  .
+
+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.
+To add any missing permissions listed here, see [Update a custom role](../role-based-access-control/custom-roles-portal.md#update-a-custom-role).
+
+## Permissions
+
+Depending on whether you're creating new resources or using existing ones, add the appropriate permissions from the following list:
+
+|Resource | Resource status | Required Azure permissions |
+|---|---|---|
+| Subnet | Create new| Microsoft.Network/virtualNetworks/subnets/write<br>Microsoft.Network/virtualNetworks/subnets/join/action |
+| Subnet | Use existing| Microsoft.Network/virtualNetworks/subnets/read<br>Microsoft.Network/virtualNetworks/subnets/join/action |
+| IP addresses| Create new| Microsoft.Network/publicIPAddresses/write<br>Microsoft.Network/publicIPAddresses/join/action |
+| IP addresses  | Use existing| Microsoft.Network/publicIPAddresses/read<br>Microsoft.Network/publicIPAddresses/join/action |
+
+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).
+
+## Roles scope
+
+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.
+
+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.
+
+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
+For more information, see [Scope levels](../role-based-access-control/scope-overview.md#scope-levels).
+
+> [!NOTE]
+> Allow sufficient time for [Azure Resource Manager cache](../role-based-access-control/troubleshooting.md) to refresh after role assignment changes.
+
+## 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)