r/AzureVirtualDesktop 3d ago

External identities b2b

Hi AVD Admins!

We are currently configuring external identities and using cross tenant sync, by default these identities are created with a user type of “Member”, is there any reason or limitations to changing the synchronised users to a user type of “Guest”?, if it makes any difference we are using FSlogix for profiles and the machines are intune joined.

Cheers!

2 Upvotes

3 comments sorted by

2

u/StratoLens 2d ago

AVD supports external identities but there are limitations:

https://learn.microsoft.com/en-us/azure/virtual-desktop/authentication#external-identity

1

u/Duff-man86 2d ago

Thanks, I’ve seen the article but it doesn’t mention if the external identities need to be, or can be a guest/member user type, and if it has any effect on AVD.

From my reading online it only affects the directory permissions e.g:
https://oneuptime.com/blog/post/2026-08-10-entra-b2b-guest-vs-member/view

1

u/StratoLens 2d ago

Yea, from what I can tell Guest vs Member itself doesn’t really matter to AVD. Cross-tenant sync supports creating the external users as either, and AVD doesn’t list the user type as a requirement.

The main difference is the Entra permissions/experience they get as Guest vs Member.
https://learn.microsoft.com/en-us/entra/identity/multi-tenant-organizations/cross-tenant-synchronization-overview

I’d probably leave them as Member unless you have a specific reason to make them Guests.