Why Add Role assignment is disabled in every azure resource?
We add any role for Managed identity or service principal because of this.
It is completely blocking our learning.
I was trying to add role to a Managed Identity for a VM through the Storage Account, but the Add role assignment is disabled there.
For every azure resource, this same. Can you please tell why this is disabled.
How can we use the Managed Identity and Service principal in this case without role assignments.
Our playgrounds are set up to enforce a certain level of access, and to do this, one of the restrictions necessarily is on IAM. So we don’t allow the changes you’re trying to do here. For a bit more detail on why, we did a FAQ on the playgrounds, which I recommend reading.
In this case then , how can we explore the concepts of service principals and Managed identities in Azure. It is basically restricting the learning knowledge of the RBAC concepts in Azure.
Not only this, even we cannot integrate any Azure resource in our Azure DevOps pipelines because we cannot assign proper roles to the Service Principal.
There is no point then to keep this Azure Cloud and Azure DevOps in this platform as it is completely blocking the learning and practice of the most important parts.
Even in the free subscriptions these things are not blocked.
Please have a look into it.
Hello Team any update on the above, how can we integrate the Azure portal resources with the Azure DevOps without having the necessary RBAC permissions.
Please let us know.
