Mar 17 2020 04:42 PM - edited Mar 25 2020 08:28 AM
UPDATE: This issue has been resolved in Production. A fix for pre-production environments will roll out with normal service updates.
A number of users have reported issues connecting to the WVD web client using both Microsoft Edge (Chromium) and Google Chrome. The February release of the new Chromium 80 engine - used by both Edge and Chrome - included changes SameSite cookie classification. More information can be found on the Chromium blog and Chromium developer guidance.
We are working on rolling out a fix to production. In the interim, please use the following workarounds to continue using the web client:
We will post an update on this thread when a fix is available in production.
Mar 20 2020 12:59 PM
Mar 23 2020 02:59 PM - edited Mar 25 2020 08:26 AM
This is fixed in Production. A fix for pre-production environments will roll out on the normal update schedule. Users in production should not be impacted any longer.
Jun 15 2022 06:02 AM - edited Jun 15 2022 06:03 AM
@briantaintor - Broken again in Microsoft Edge Version 102.0.1245.41 (Official build) (64-bit). https://client.wvd.microsoft.com/arm/webclient/index.html redirects to https://client.wvd.microsoft.com/arm/webclient/legacy/index.html. Works properly in Chrome Version 102.0.5005.115 (Official Build) (64-bit) and Firefox 101.0.1 (64-bit).