Use Seamless SSO in AADDS environments.
At the moment, having seamless SSO in Azure Active Directory Domain Services doesn't work. Logically, this feature should be automatic...
At the moment, you can join a machine to AADDS domain, and log in to it with Azure AD credentials. But users still need to sign in manually to Office.com, office apps, etc.
This is extremely important in a AADDS Windows Virtual Desktop scenario (where Microsoft Office is hosted as RemoteApps). To access Office, users will need to log in to WVD, then AGAIN into the remoteapp host itself, and AGAIN into the Microsoft Office apps - all with the same credentials.
We are using Azure ADDS for WVD to use WVD VMs directly on tablet end points. Without SSO this service is almost useless. Hope there is a solution from Microsoft soon
Mukhtar Mohammed commented
We are using Azure ADDS for WVD and looks like this will make our customers/users unhappy.
Requesting to have a look at this soon.
Marcin Rybarczyk commented
We been trying to move our application to Azure Active Directory Services and Azure SQL. Unfortunately our application is using windows integrated authentication that is not supperted via Azure SQL so we decided to replace it with Azure Active Directory Integrated Authentication but it is not working for machine added do Azure Active Directory Domain Services because there is no Seamless SSO feature. So currently microsoft don't have any integrated authentication for this scenario. There are many organisation that relay on integrated authentication and access management via security groups. We are force right now to deploy domain controller in Azure and cancel AADDS subscription. I'm surprised that this topic is not under highest possible priority. Especially with big trend that people want to use WVD.
Stanislav Galchonkov commented
For WVD Azure ADDS environments, this seems to be a real blocker to move with Windows Virtual Desktop product into SMB with Microsoft 365 Business Premium. WVD becomes quite painful for end-user with Azure ADDS
Dilum Jay commented
Must have feature for better end user experience.
Karen Davtyan commented
Its really needs for WVD
Greg D. Obleshchuk commented
This is not am optional feature it is a must have . Without SSO we are forced to enter user id's and passwords into our services so they can connect to Azure resources (like databases) . I can't vote strongly enough to have this oversight fixed.
How long does it take to review this? With this kind of lack in progress, you would think the federal government was handling it. This should be done already.
This should have been taken care of yesterday. And if not yesterday, then today. And if not today, then tomorrow.
We have been waiting on this fix for nearly 18 months, and at this point, it is holding us back. Can we get this moved up on the priority list please?
James Pike commented
Can we please have this? Voted +1
Also, while I have your attention, has anyone ever pulled up to a red light at like 3 am and the sensors not detect your car so you sit there for 5 minutes deciding whether to break the law and run the light?
How has this not been done already? This is holding up a major migration to full Azure for our company. Every other application has SSO, why not OneDrive? Major oversight... please fix immediately
Jackson Peel commented
This should be higher priority. Seeing as how this has been listed as Under Review since October 2019 is disappointing. We've made the transition to WVD with AADDS, and now it feels like we have taken a step back.
+1. This should be done immediately
Stefan Nordkamp | Exite ICT commented
Jason Meaney commented
@Nick Romanek, +1. Voted!
Nick Romanek commented
Can we please get this fixed ASAP? I feel like WVD shouldn't have been released without this important feature. If you want customers to use Microsoft Office, why make it difficult for them to do so? You took the extra step of integrating it in the multi-user OS, but left out the authentication piece. I'm trying to deploy WVD to our company now but this is a show-stopper.
Mark Condez commented
Indeed, SSO should work in AAD DS, doesn't make sense once you are inside WVD environment with authenticated Azure AD login that you need to authenticate MS SaaS with the same azure AD login.
Voted +1, hope MS will address this immediately as its annoying experience for shifted users.
Karen Davtyan commented
very important feature!!!
Matthias Taveirne commented
Vote+1, SSO in AAD DS to Azure AD integrated services like Office365 is must these days. User experience is quiet bad at the moment in Windows Virtual Desktop with all these login popups all the time.
Is there an update on this feature?