Multiple WVD tenants in the same subscription

[Thomas-DeWitte]

Good day community!

I have a question regarding multitenancy in WVD.

Is it possible to have one single subscription where we manage the WVD session hosts which are member of multiple WVD tenants each pointing to their own Azure AD tenant?

It would describe a bit below slide where Azure AD is a different tenant per setup.

The idea would be to have the ability to manage the session hosts (of different WVD tenants and according Azure AD tenants) in one single subscription.

Is this technically possible and supported?

Kind regards,

Thomas

[#2]

I'm also interested in the answer to this. Furthermore, it would be nice to see some best practices on a service provider model type of documentation. The solution speaks about multi-tenancy but at the same time, you need ADDS or AD server for each and every client.

[#3]

@Thomas-DeWitte What you are asking is not possible. You can currently deploy multiple WVD tenants, but they are all managed by a single AAD tenant. WVD uses a combination of AAD identity synchronized with either AAD DS or AD DS. Since WVD is using an Azure Service provided by a subscription, a subscription and its services can only be managed by a single AAD tenant. "WVD tenants" are really just a logical grouping inside the WVD service. It's confusing using "tenant" since we use that term to describe AAD instances and is probably why Microsoft is changing that term, in ARM WVD 2020, to "workspace".

Host Pools and session hosts are a child object of WVD tenants so they are locked to the same identity boundaries.

[#4]

Could you just simply host each customer in separate host pools?