Cannot live without AD ?

%3CLINGO-SUB%20id%3D%22lingo-sub-465116%22%20slang%3D%22en-US%22%3ECannot%20live%20without%20AD%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-465116%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Guys%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20%22traditional%22%20AD%20services%20is%20still%20a%20requirement%20%3F%20(either%20on-premises%20AD%20or%20Azure%20AD%20domain%20services)%3CBR%20%2F%3EWhy%20is%20that%20%3F%20why%20can't%20these%20machines%20be%20just%20Azure%20AD%20joined%20%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-572016%22%20slang%3D%22en-US%22%3ERe%3A%20Cannot%20live%20without%20AD%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-572016%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F313219%22%20target%3D%22_blank%22%3E%40vinisz%3C%2FA%3E%26nbsp%3B%3A%20Yes%2C%20that%20is%20still%20required.%20There%20are%20multiple%20reasons%2C%20one%20of%20those%20being%20that%20many%20of%20these%20environments%20are%20setup%20for%20app%20compatibility%20that%20still%20do%20require%20talking%20over%20a%20domain.%20Another%20large%20factor%20is%20that%20it's%20currently%20difficult%20to%20remote%20into%20an%20Azure%20AD%20Joined%20machine%2C%20since%20the%20connecting%20device%20must%20also%20be%20Azure%20AD%20Joined.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%2C%20however%2C%20tracking%20this%20work%20for%20the%20future%20to%20make%20it%20easier%20to%20deploy%20more%20lightweight%20Windows%20Virtual%20Desktop%20environments%20when%20you%20don't%20need%20full%20domain%20dependency.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2396543%22%20slang%3D%22en-US%22%3ERe%3A%20Cannot%20live%20without%20AD%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2396543%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305776%22%20target%3D%22_blank%22%3E%40christianmontoya%3C%2FA%3E%26nbsp%3Bnot%20trying%20to%20revive%20an%20old%20thread%2C%20but%20wanted%20to%20check%20in%20on%20this%20after%202%20years.%20On-prem%20AD%20is%20legacy%20in%20my%20opinion%20but%20WVD%20is%20being%20held%20back%20by%20this%20dependency.%20Any%20news%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2422221%22%20slang%3D%22en-US%22%3ERe%3A%20Cannot%20live%20without%20AD%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2422221%22%20slang%3D%22en-US%22%3EThis%20is%20still%20the%20case%2C%20but%20watch%20this%20space.%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi Guys,

 

So, "traditional" AD services is still a requirement ? (either on-premises AD or Azure AD domain services)
Why is that ? why can't these machines be just Azure AD joined ? 

3 Replies

@vinisz : Yes, that is still required. There are multiple reasons, one of those being that many of these environments are setup for app compatibility that still do require talking over a domain. Another large factor is that it's currently difficult to remote into an Azure AD Joined machine, since the connecting device must also be Azure AD Joined.

 

We are, however, tracking this work for the future to make it easier to deploy more lightweight Windows Virtual Desktop environments when you don't need full domain dependency.

@christianmontoya not trying to revive an old thread, but wanted to check in on this after 2 years. On-prem AD is legacy in my opinion but WVD is being held back by this dependency. Any news?

This is still the case, but watch this space.