question

PeterThurwachterMINDTREELIMITED-2688 avatar image
0 Votes"
PeterThurwachterMINDTREELIMITED-2688 asked AnuragSingh-MSFT answered

If Redhat OpenShift(ARO) by default makes a Resource Group "Read Only", is there anyway to modify the "Deny Assignment" so that access to this RG can be given to other Users? [ 2112280060001080 ]

Hello Experts,

When using Azure Redhat OpenShift(ARO), using the IAM blade, it seems impossible to add access control to new users. The end goal is to allow them to confirm the cost of a specific Resource Group in cost Management.

It seems this inability to do so is because said resource group is locked in a read-only state.
https://docs.microsoft.com/en-us/azure/openshift/openshift-faq


Are control plane nodes abstracted away as they are with Azure Kubernetes Service (AKS)?

No. All resources, including the cluster master nodes, run in your customer subscription.
These types of resources are put in a read-only resource group.




According to this “How blueprint locks work” link: https://docs.microsoft.com/en-us/azure/governance/blueprints/concepts/resource-locking#how-blueprint-locks-work


An Azure RBAC deny assignments deny action is applied to artifact resources during assignment of a blueprint if the assignment selected the Read Only or Do Not Delete option. The deny action is added by the managed identity of the blueprint assignment and can only be removed from the artifact resources by the same managed identity.



Further down the same document, there are sections pertaining to “Exclude a principal from a deny assignment” and “Exclude an action from a deny assignment”

IF this resource group was made “read-only” by Redhat OpenShift, does that mean there is simply no way to modify this “deny assignment” so that a subscription owner can add new users that have the ability to view the cost of this resource group?

Thank you,


azure-redhat-openshift
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @PeterThurwachterMINDTREELIMITED-2688

Welcome to Microsoft Q&A!

The first link shared in the question states that the "Azure Managed Application lives in a locked Resource Group". This is different from a lock in the sense of Azure Blueprints (the second link).

You can read more about Resource Group Locking in this link: Lock resources to prevent unexpected changes. If you would like to make changes to the Resource group, you would have to:

> First remove this lock (from Resource group blade --> Locks option)
> Make the changes (add required user/permission)
> and Apply this lock again.

This lock is applied to prevent users from accidentally deleting or modifying critical resources.

163159-image.png

Please let me know if you have any questions.


Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

0 Votes 0 ·
image.png (34.5 KiB)

1 Answer

AnuragSingh-MSFT avatar image
0 Votes"
AnuragSingh-MSFT answered

@PeterThurwachterMINDTREELIMITED-2688, I see that feedback was shared at the link below for this limitation. Please feel free to add any additional comment below to help others looking for answers to similar queries.

https://feedback.azure.com/d365community/idea/0e154339-0c7e-ec11-a81b-0022484bfd94

Copying the excerpt from the feedback as below:

Currently, it is not possible to add new users (with viewing roles) to an already existing ARO resource group after resource group creation due to the Deny Assignments placed on the Resource Group. Although it is understandable the Deny Assignments (that is automatically put in place) is a very effective protective measure, it can also be problematic if there is a need to later modify after the Resource Groups' initial creation.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.