You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2023. It is now read-only.
I'm trying to follow the "OpenNESS Devkit for Azure" template that is shown on openness-experience-kits/cloud/.
When I try to deploy the template on Portal Azure, I get an error of this type:
"The client '2a6fc298-c33a-4a3e-840e-d237ec92c777' with object id '2a6fc298-c33a-4a3e-840e-d237ec92c777' does not have authorization to perform action 'Microsoft.ContainerInstance/register/action' over scope '/subscriptions/53b81d7e-9278-4218-a658-9d7b3ae89c66' or the scope is invalid. If access was recently granted, please refresh your credentials."}]}
I assume it has something to do with this prerequisite: "Your account needs the Managed Identity Contributor role in order to create a user assigned managed identity".
But I already tried to assign this role to the Managed Identity that is being created and nothing changed.
For people who managed to deploy this template to Azure, what should I do to deal with this permission error?
Thank you
The text was updated successfully, but these errors were encountered:
Not sure if you are still pursuing this, but putting it here for general help.
I faced the exact same error. I was able to resolve it by providing "ContainerInstance" and "ContainerRegistry" Resource provider to my subscribtion entity...
Hi,
I'm trying to follow the "OpenNESS Devkit for Azure" template that is shown on openness-experience-kits/cloud/.
When I try to deploy the template on Portal Azure, I get an error of this type:
I assume it has something to do with this prerequisite: "Your account needs the Managed Identity Contributor role in order to create a user assigned managed identity".
But I already tried to assign this role to the Managed Identity that is being created and nothing changed.
For people who managed to deploy this template to Azure, what should I do to deal with this permission error?
Thank you
The text was updated successfully, but these errors were encountered: