Could not connect to resources.

[microsoft]

Could not connect to resources.

[dwnatwick]

@LucaOtto. Is the user licensed for Microsoft 365 applications? Have you attempted a connection to the Remote Desktop rather than just the apps? Thank you very much.

[LucaOtto]

@dwnatwick : yes I attempted to connect to the desktops ( pooled and single). Same error. The users are demo users generated through the M365 portal. It shows that users are synched via AD Connect to the local AD ( Exercises 1 to 4).

[dwnatwick]

@LucaOtto . Did you assign the O365 licenses to the users when they were created?

[LucaOtto]

@dwnatwick I just ( double-checked): I used this demo user, she seems to have all the proper licenses in place:

[KitSkin]

@LucaOtto, if you go to the WVD Host Pool, under the Overview section, is the Unavailable listed as '0'? Another way to look at it, if you look at your Session Hosts for your host pool do they both have an 'Available' status and Drain Mode 'Off'?

[KitSkin]

Also, if you've been sitting idle on the website for 30 minutes or more, your token could have expired as well. To resolve this, just sign out the session and sign back in.

[LucaOtto]

@KitSkin yes, they are available and drain mode off. I connected to the desktop and/or published apps within a minute of completing the backend system setup, I don't believe it's because of the above.

[KitSkin]

Could you enable diagnostics and Log Analytics to help centralize the error reporting for diagnostics?

[LucaOtto]

My VS subscription has only few $$ left, I will have to wait the next billing cycle to do that.

[KitSkin]

the Log Analytics make it easier to diagnose the problem by putting everything in one place to query against, but you can also go to each resource and use the troubleshooting guides to examine errors on each:
https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-vm-configuration

One thing you might want to do is try with the Remote Desktop Client rather than the web client. Sometimes the errors will be logged with more verbosity in your local Event Log that aren't necessarily translated through the web client without the diagnostic logs enabled.

[DawnmarieDesJardins]

Closing issue - no additional communication from field & recent update merge with PR #9