An Azure service that provides a flexible, self-service deployment of fully managed OpenShift clusters.
Your issue arises because Azure Red Hat OpenShift (ARO) resource groups are locked down by design. To manage NSGs, you must attach your own during cluster creation—on existing clusters, NSG changes in managed groups are blocked, and full control usually requires redeployment.
When you create an ARO cluster, Azure automatically creates a dedicated "Managed Resource Group" for cluster resources (VMs, NSGs, etc.). This group has a DenyAssignment, meaning even users with Global Admin or Tenant Owner roles are prevented from making changes such as editing NSG rules or adding users inside this resource group.
https://access.redhat.com/solutions/7024799
Only the Cluster Service Principal is excluded from the deny assignment; all other users, including admins, are blocked. This strict control is designed to maintain cluster integrity and security but often becomes a major headache when you need to troubleshoot or customize.
https://learn.microsoft.com/en-us/azure/openshift/howto-bring-nsg
Use “Bring Your Own NSG” Feature: If you use your own NSG from your own resource group (not the managed one), you retain the ability to add or change rules as you like. Future changes should be done through this NSG, not the cluster’s managed NSGs.
You cannot modify the NSG in the Managed Resource Group due to DenyAssignment. If you need to make changes, you may have to Re-deploy ARO with the "Bring Your Own NSG" feature, ensuring your custom NSG is attached during setup.
If you have any further queries, let me know. If the information is helpful, please click on Upvote.