Forum Discussion

ddasilva's avatar
ddasilva
Brass Contributor
May 19, 2020
Solved

CAA20004 - AADSTS65005 - The app needs access to a service

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

  • ddasilva's avatar
    ddasilva
    May 19, 2020

    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&redirect_uri=https%3A%2F%2Frdweb.wvd.microsoft.com%2FRDWeb%2FConsentCallback
    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&redirect_uri=https%3A%2F%2Frdweb.wvd.microsoft.com%2FRDWeb%2FConsentCallback
    6. Sign in to the Windows Virtual Desktop consent page as global administrator, as you did in step 2
    7. Select Accept

7 Replies

  • HandA's avatar
    HandA
    Brass Contributor
    Jun 12, 2020

    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.

  • ddasilva's avatar
    ddasilva
    Brass Contributor
    May 19, 2020

    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&redirect_uri=https%3A%2F%2Frdweb.wvd.microsoft.com%2FRDWeb%2FConsentCallback
    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&redirect_uri=https%3A%2F%2Frdweb.wvd.microsoft.com%2FRDWeb%2FConsentCallback
    6. Sign in to the Windows Virtual Desktop consent page as global administrator, as you did in step 2
    7. Select Accept
    • PatBrodeur's avatar
      PatBrodeur
      Copper Contributor
      May 20, 2020
      Bingo! Fixed my issue! So we still have to do the consents like with the 2019 fall version.
      • DavidBelanger's avatar
        DavidBelanger
        Icon for Microsoft rankMicrosoft
        May 20, 2020
        Consent will not be needed with the Spring Update in general but this is a temporary workaround for the Windows client.

Resources