Oct 21 2020 07:54 AM
We've built a solution (web part) that allows users to launch Windows Virtual Desktop apps and desktops from within SharePoint. For this, we used some of the ideas that were described in following article:
The first thing we do, from a client's perspective, is fetch the webfeeddiscovery xml from https://rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx. We parse the xml and try to read the Tenant Feed Url and then we continue with some other requests to show all apps and desktops in the web part.
Up until recently this worked fine and we were able to show the user a list of apps and desktops which he/she has access to and could then open these using a downloaded RDP file.
Unfortunately we're not longer able to use this endpoint because of CORS headers not being present in the response.
When we do a fetch to that webfeeddiscovery.aspx url (or a different url we've had some success with in the past:
Oct 21 2020 11:52 AM
With the help of a colleague I was able to fix the issue myself. Apparently something changed on the service end that now requires an extra header:
With the addition of this header the request is now again successful:
Nov 04 2020 06:05 AM
aaaaand it's broken again...
Same CORS errors, even with the custom header added.
I checked the headers in the regular webclient (at https://rdweb.wvd.microsoft.com/arm/webclient/index.html) and noticed they updated the X-MS-User-Agent header to include a different (newer?) version: