Skip to content

Commit f19b955

Browse files
Merge pull request #116489 from mmadrigal98/patch-3
CSS Networking.md
2 parents f08c517 + fea8ce7 commit f19b955

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/virtual-network/manage-network-security-group.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -665,6 +665,9 @@ az network asg delete --resource-group myResourceGroup --name myASG
665665

666666
To manage network security groups, security rules, and application security groups, your account must be assigned to the [Network contributor](../role-based-access-control/built-in-roles.md?toc=%2fazure%2fvirtual-network%2ftoc.json#network-contributor) role. A [Custom role](../role-based-access-control/custom-roles.md?toc=%2fazure%2fvirtual-network%2ftoc.json) can also be used that's assigned the appropriate permissions as listed in the following tables:
667667

668+
> [!NOTE]
669+
> You might NOT see the full list of service tags if the Network Contributor role has been assigned at a Resource Group level. To view the full list, you can assign this role at a Subscription scope instead. If you can only allow Network Contributor for the Resource Group, you can then also create a custom role for the permissions "Microsoft.Network/locations/serviceTags/read" and "Microsoft.Network/locations/serviceTagDetails/read" and assign them at a Subscription scope along with the Network Contributor at Resource Group scope.
670+
668671
### Network security group
669672

670673
| Action | Name |

0 commit comments

Comments
 (0)