Cannot access my organization Virtual Machine resources

The most likely cause is missing or insufficient Azure role-based access control (RBAC) permissions on the subscription, resource group, or virtual machine resources, which can make VM features or entire resources not appear in the portal even though they exist for the organization.

Use these steps to resolve:

1. Confirm access scope
   • Ask the Azure subscription or resource group administrator to verify that the account is assigned an appropriate built-in role (for example, Reader, Virtual Machine Contributor, or Contributor) at the correct scope (subscription or the specific resource group that contains the VMs).
   • If only the VM resource is shared but not the related resources (network, storage, etc.), some features and blades can appear disabled or incomplete.
2. Ensure a role with at least read access is assigned
   • If no role is assigned, the account will not see the resources at all.
   • If only very limited roles are assigned, some features will be disabled. For virtual machines, write access is required for actions such as start/stop, disk changes, IP changes, extensions, availability sets, load balancers, and alert rules.
   • The admin should assign an Azure built-in role with sufficient permissions (for example, Contributor on the resource group that contains the VMs) so that the VM and its features appear correctly.
3. Check for disabled features due to RBAC
   • If the account can see some parts of the VM but certain tiles or actions are disabled, this is expected behavior when only read access is granted. Features like start/stop, configuration changes, logs, and console require write permissions.
   • The fix is again to assign a role with write permissions for the VM or its resource group.
4. If the portal view still shows an error
   • After confirming correct RBAC assignments, sign out of the Azure portal and sign back in, or try a different browser/private window to rule out a cached portal issue.
   • If other team members with the same role at the same scope do not see the issue, the subscription admin can temporarily assign a higher-privilege role (such as Contributor) to test whether the problem is purely permission-related.

If, after RBAC is corrected and the portal cache is cleared, the issue persists only for this account, the subscription admin should open a support request with Microsoft from a working admin account, including the timestamp and correlationId shown in the error.

References:

• Troubleshoot Azure RBAC