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
It's possible that users may hit this issue if they don't own the current subscription, and we try to iterate over their resource groups. This wasn't an issue before because we never used to allow users to choose RGs, though they would have still failed during deploy if they didn't have permissions.
The text was updated successfully, but these errors were encountered:
The root cause of this issue is that the users subscription was not properly registered in RDFE. There is an incident logged to correct the entry. In the meantime, I'm wondering if it makes sense to filter out these subs if there are authorization issues. In this users' case it wouldn't help because they only have one subscription and it most cases it would mask a real problem.
See this twitter post: https://twitter.com/oakcool/status/593800861463216128
It's possible that users may hit this issue if they don't own the current subscription, and we try to iterate over their resource groups. This wasn't an issue before because we never used to allow users to choose RGs, though they would have still failed during deploy if they didn't have permissions.
The text was updated successfully, but these errors were encountered: