OpenShift Network Security Policy Is Blocking my machine from Connecting to ARO Cluster

Patrick M. Kidney 0 Reputation points
2025-08-19T22:30:52.3766667+00:00

OpenShift Network Security Policy Is Blocking my machine from Connecting to ARO Cluster. If I try to configure an Network Security rule I get access is denied even though my account has Global Admin and my account owns the tenant. How can I configure the NSG if my account is getting access is denied. Its the most stupid problem. Microsoft makes changes and now I am having all kinds of Security related issues. My tenant is complete blocked from making any changes. How can I get around this security issues

Azure Red Hat OpenShift
Azure Red Hat OpenShift

An Azure service that provides a flexible, self-service deployment of fully managed OpenShift clusters.


1 answer

Sort by: Most helpful
  1. Anusree Nashetty 6,555 Reputation points Microsoft External Staff Moderator
    2025-08-20T15:34:00.69+00:00

    Hi Patrick M. Kidney

    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.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.