Azure Virtual Desktop don´t visible to the Guest account

Paulo Jorge Agripino 0 Reputation points
2026-09-15T10:51:22.5233333+00:00

I build an Azure Virtual desktop environment, I created a security group, that allow the use of the AVD, for internal users, and guest users.

The guest users when enter on https://windows,cloud,microsoft, they authenticate on the Microsoft with their credential, but don't see the AVD environment, the internal user, after authenticate, can see and enter without problems.

If the guest user enters on https://myaccount.microsoft.com/organizations they can see both organizations their own, and the organization that owns the AVD, but cannot see it, and without that cannot access the AVD.

I already try several things, the assignment manually the role of Virtual Machine user login on the resource group for the guest user, but the result is always negative.

Regards

Azure Virtual Desktop
Azure Virtual Desktop

A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Marcin Policht 107.9K Reputation points MVP Volunteer Moderator
    2026-09-15T11:15:14.39+00:00

    Start by verifying that the requirements listed at https://learn.microsoft.com/en-us/azure/virtual-desktop/authentication#external-identity are satisfied. If so, focus on the B2B guest access and tenant context. For the guest, verify Microsoft Entra ID → External Identities → Cross-tenant access settings in the tenant that owns AVD. Confirm that inbound B2B collaboration from the guest's home tenant is allowed. Also check Conditional Access policies that apply to Guest or external users, particularly policies requiring MFA, authentication strength, compliant devices, or other conditions.

    The other key area is the AVD tenant context. The guest authenticates with their home-tenant credentials, while the AVD resources are in your tenant. After authentication, the guest would access the AVD service in the context of the tenant that owns the AVD deployment. Test with the current Windows App/web client and explicitly select or switch to the organization that owns the AVD environment if the client presents that option.


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.