Authentication fails with entra ID (personal account) about acr HOT 5 OPEN

@northtyphoon Thanks for the suggestion. I did verify indeed that I was a service administrator, likely that this subscription was created awhile back.

And after assigning myself an "Owner" role of the subscription this is addressed.

However, this ends up impacting a lot of users with existing long-lived subscriptions. Would there be an alternative that doesn't require a workaround?

from acr.

@shanselman you are right, you still login with MSA. For ACR, there should be no side-effect after you grant owner role. You can still keep the co-admin in case you have a concern on other services. Azure will retire it after 8/31/2024.

from acr.

@weikanglim can you check if you are the classic admin on the subscription? If yes, you can work around it by granting your account the own role on the subscription.

from acr.

@weikanglim we plan to rollout a fix to support the classic administrators by Jan. However, classic administers is deprecated. It will be great to recommend your customer to take the chance to migrate to standard Azure RBAC.

https://learn.microsoft.com/en-us/azure/role-based-access-control/classic-administrators

Important

Classic resources and classic administrators will be [retired on August 31, 2024](https://azure.microsoft.com/updates/cloud-services-retirement-announcement/). Remove unnecessary Co-Administrators and use Azure RBAC for fine-grained access control.

from acr.

@weikanglim we plan to rollout a fix to support the classic administrators by Jan. However, classic administers is deprecated. It will be great to recommend your customer to take the chance to migrate to standard Azure RBAC.

https://learn.microsoft.com/en-us/azure/role-based-access-control/classic-administrators

Important

Classic resources and classic administrators will be [retired on August 31, 2024](https://azure.microsoft.com/updates/cloud-services-retirement-announcement/). Remove unnecessary Co-Administrators and use Azure RBAC for fine-grained access control.

Are there any ramifications to this migration? We can still login with our MSAs, right?

from acr.