A cloud-based identity and access management service for securing user authentication and resource access
Loss of access to a resource group that still appears on the bill is typically caused by a change in permissions or role assignments, not by deletion of the resources.
Common causes in this scenario:
- Role assignment removed or changed
- The account might have been removed from a role assignment (for example, Contributor or Reader) on the subscription, resource group, or specific resources.
- If only Reader access remains, many management features are disabled. For web apps and similar resources, Reader access prevents actions like viewing deployments, logs, or configuration, and some blades in the portal appear disabled.
- Solution: An administrator must assign a role with write permissions (such as Contributor) on the resource group or subscription.
- Insufficient scope of access
- Access might exist only at the app (resource) level but not at the resource group or App Service plan level. Some features (pricing tier, scaling, quotas, TLS/SSL, alerts, Application Insights, etc.) require write access at the App Service plan or resource group scope.
- Solution: Ensure a built-in role with write permissions is assigned at the App Service plan or resource group level, not just on individual resources.
- Different account signed in
- If multiple Microsoft accounts are used (work and personal), the browser may be signed in with an account that does not have access, even though billing still shows the resources.
- Solution: Sign out of all Microsoft accounts in the browser, clear site data if needed, and sign back in with the account that owns or has been granted access to the subscription/resource group.
- Access controlled via groups or entitlement management
- Access may be granted through Microsoft Entra groups or access packages. If group membership or access package assignments changed, effective access to the resource group can be lost.
- Solution: Have an Entra administrator verify group membership, dynamic group rules, and any entitlement management policies that grant access to the subscription or resource group.
If access is needed again, an administrator with sufficient privileges on the subscription or resource group must reassign an appropriate Azure built-in role (for example, Contributor) at the correct scope.
References:
- Troubleshoot Azure RBAC
- Troubleshoot no data: Application Insights for .NET and .NET Core
- Review access for yourself to groups or applications in access reviews
- Troubleshoot entitlement management
- Common issues: Azure resource group privileges
- Problems signing in to a Microsoft application
- az staticwebapp list
- Can not access Azure - Microsoft Q&A
- Unable to access this even after accesses - Microsoft Q&A