New Azure WVD deployment - unable to log into WVD portals

Question

Hi,
I'm trying to test out the new release of WVD.
Im keeping things simple with just the default desktop application group which has been assigned to one user.
Workspace is there and the application group is assigned to it.

I have a VM running AD in the same virtual network.
Accounts have been created in AD and sync'd to Azure AD using AD Connect.

Because this is a test environment I have no custom domain setup so I am logging into the WVD portal and client with the onmicrosoft account not my internal domain UPN.

When I log into the remote desktop client and try to Subscribe with a user that has been assigned rights to the default desktop application group I receive an error below. Anyone have any ideas?

Answer 1

@mij2020 This is an OAuth error. Make sure below service principals are present in your tenant under Azure AD > Enterprise application > All Applications > Search Windows Virtual

If these are not present, you need to access below URLs and specify Global Admin credentials when you are prompted and "Accept" to create these. If these Service Principals are present and you are still facing the issue, there may be a possiblilty that required permissions are not configured properly. Accessing below URLs will re-configure required permissions. So in both cases, I would suggest you to access Below URLs with Global Admin account and Accept the consent prompt.

• https://login.microsoftonline.com/{tenant}/adminconsent?client_id=5a0aa725-4958-4b0c-80a9-34562e23f3b7&redirect_uri=https%3A%2F%2Frdweb.wvd.microsoft.com%2FRDWeb%2FConsentCallback
• https://login.microsoftonline.com/{tenant}/adminconsent?client_id=fa4345a4-a730-4230-84a8-7d9651b86739&redirect_uri=https%3A%2F%2Frdweb.wvd.microsoft.com%2FRDWeb%2FConsentCallback

-----------------------------------------------------------------------------------------------------------

Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.

Answer 2

Thank you - adding these two Enterprise apps allowed the accounts to login.

Because I was testing the old WVD non ARM system I removed these 2 Enterprise apps because I wanted to completely remove and start again from fresh using the new ARM Spring release version of WVD.

I had assumed that they would have been re-created if needed for the new release.
If they are required for the Spring release version - then why were they not created during the provisioning process? I don't see in the new release WVD documentation that I needed to go through the consent process similar to the old way.
I'm just curious.

Thanks