I'm also working on this right now. I'm just dumping what I know so far in case it helps anyone else. I've run up against the RemoteDesktop and Microsoft.RDInfra.RDPowerShell modules not seeming to have support yet for a slight flavor change of MS virtual desktop. They don't seem to understand the concept of the "feed" that publishes the desktops to a given user.
However, I got a little further in actually getting a session into ASGRD. Sorry for the English response but I don't speak German, Google helped me with your comments.
Translated to English:
https://forum-asg--rd-com.translate.goog...r_pto=wapp
So by launching my desktop session from msrdcw, which subscribes to your "feed" of desktops and apps by pulling the URL
https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery
There is an alternate method which you can subscribe via you email used for Azure login. I've not tried it.
I found that
C:\Program Files\Remote Desktop\msrdcw.exe, working directory : C:\Program Files\Remote Desktop
calls
C:\Program Files\Remote Desktop\msrdc.exe
and from using task manager or Process Explorer, we see the command line looks like this:
"C:\Users\me\AppData\Local\rdclientwpf\( somecrazylong hex).rdp" /u:me.lastname@mydomain.com /l:1 /p:44252 /r:3 /aid

8digit-hex)-(4digit-hex)-(4digit-numeric-or-hex)-(4 digit hex)-(12digit-hex) /n:"Cloud PC Enterprise 4vCPU/16GB/256GB"
I've exempted the digits because some are likely specific to our Azure instance and could identify it.
The help for msrdc.exe:
[Window Title]
Remote Desktop Usage
[Content]
MSRDC <connection file> [/u:<username>]
"connection file" -- Specifies the name of an .RDP file for the connection.
/u:<username> -- The username to use when connecting.
It doesn't specify /l:1 /p:44252 /r:3 /aid: or /n: parameters, but I can see that n is the name of my cloud desktop.
I was able to take the above command and write a ext application, and it actually launches a session which prompts for credentials, then integrates it into a tab. The screen size doesn't expand to fit the full tab but it does function. This is likely because we don't have smart sizing turned on - I've not seen what the Azure side config looks like yet. ref:
https://web.archive.org/web/201710062017...ile-format and
https://superuser.com/questions/98494/wi...on-the-fly
I don't know about the longevity of that rdp file. It's signed so of course you can't alter it. I've been using the same RDP file for 3 days now and it's still working.
The process of pulling the machines in your feed seems to be described here, though W365 could have some minor variation from Windows Virtual Desktop, I'd think it would be close or identical:
https://virtuallyflatfeet.wordpress.com/...nt-to-wvd/