SOLVED

CAA20004 - AADSTS65005 - The app needs access to a service

Brass Contributor

Hello,


I've recently deployed WVD Spring 2020 and my users report the following error with the WVD client

"AADSTS65005 - The app needs access to a service.  https://mrs-prod.ame.gbl/mrs-RDInfra-prod"

 

Users report no issues using the HTML5 client.   What did I miss during the configuration process?

Note:  I've registered the Microsoft.DesktopVirtualization resource provider

 

How do I resolve this issue?

 

Thanks,

D

7 Replies
best response confirmed by ddasilva (Brass Contributor)
Solution

Hello,

 

I realized that I did not provide consent for the WVD server and client app.  I believe the Spring 2020 documentation is missing references to provide consent.  Perhaps MS could update their r documentation to mitigate the issue with other clients? 

 

I fixed the issue by following the steps below (pulled from the Fall 2019 documentation):

 

  1. Open a browser and begin the admin consent flow to the Windows Virtual Desktop server app.  https://login.microsoftonline.com/common/adminconsent?client_id=5a0aa725-4958-4b0c-80a9-34562e23f3b7...
  2. Sign in to the Windows Virtual Desktop consent page with a global administrator account.
  3. Click Accept
  4. Wait a minute for Azure AD to record consent
  5. Open a browser and begin the admin consent flow to the Windows Virtual Desktop client app. https://login.microsoftonline.com/common/adminconsent?client_id=fa4345a4-a730-4230-84a8-7d9651b86739...
  6. Sign in to the Windows Virtual Desktop consent page as global administrator, as you did in step 2
  7. Select Accept
Bingo! Fixed my issue! So we still have to do the consents like with the 2019 fall version.
Consent will not be needed with the Spring Update in general but this is a temporary workaround for the Windows client.

@David Belanger Is there a reason why we would have a mixed experience with the Windows Client issue mentioned here? I've heard that some have not needed to go through the grant consent process with the Spring 2020 Update, but I just ran into an issue where I could not use the Windows client (HTML5 client was fine) until I did that step. Is there something we can look for as an indicator of sorts?

@ddasilva 

 

I've deployed the Spring Update twice now and both times needed to do the consent due to the error on the Windows RD Client.

1 best response

Accepted Solutions
best response confirmed by ddasilva (Brass Contributor)
Solution

Hello,

 

I realized that I did not provide consent for the WVD server and client app.  I believe the Spring 2020 documentation is missing references to provide consent.  Perhaps MS could update their r documentation to mitigate the issue with other clients? 

 

I fixed the issue by following the steps below (pulled from the Fall 2019 documentation):

 

  1. Open a browser and begin the admin consent flow to the Windows Virtual Desktop server app.  https://login.microsoftonline.com/common/adminconsent?client_id=5a0aa725-4958-4b0c-80a9-34562e23f3b7...
  2. Sign in to the Windows Virtual Desktop consent page with a global administrator account.
  3. Click Accept
  4. Wait a minute for Azure AD to record consent
  5. Open a browser and begin the admin consent flow to the Windows Virtual Desktop client app. https://login.microsoftonline.com/common/adminconsent?client_id=fa4345a4-a730-4230-84a8-7d9651b86739...
  6. Sign in to the Windows Virtual Desktop consent page as global administrator, as you did in step 2
  7. Select Accept

View solution in original post