Support Chrome in Server 2016 for compliant/hybrid join (using "Windows 10 Accounts" extension)
This has been listed as "Coming Soon" for six months? A year? Because Server 2016 isn't supported, we have to assign public IPs to Azure VMs and then exempt those IPs from CA rules. We didn't have to do this with Server 2012 R2, yet here in October 2018 we have to do it with Server 2016!
I am sure backporting the fixes and improvements to hybrid join in Win 10 v1703 is work MS does not care to do and that is why this is not supported yet. Remember we have no Edge on Server 2016 so we must use Chrome!
The lack of the Chrome extension supporting Server 2016 complicates our server builds and CA rules, increasing the risk of a gap somewhere.
same issue does appear to exist with Edge Insider based on chromium. I have just tested it and that appears to start working with Win10 1903, not LTSC 2019 (1809), not LTSB 2016 (1607)
Microsoft has added "Chrome" as supported on 2019 (not 2016) here: https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/technical-reference but I wonder if this really works with Hybrid Azure AD Join - need to test it.
Alex Rourke commented
They have completely removed Chrome from the list of browsers supported in Server 2016. Not even "Coming Soon" anymore. I just don't understand Microsoft sometimes, they really love to make people's lives needlessly difficult. I'm sure I know their answer - "Use VDI with Windows 10!"
Can you tell us when you plan support that? We need to use another browser engine then IE and MS Edge is not supported on Server 2016!
We definitely need this. We have many customers with thousands of users running RDS/Citrix XenApp and want to use Chrome.