Forum Discussion
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
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):
- 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
- Sign in to the Windows Virtual Desktop consent page with a global administrator account.
- Click Accept
- Wait a minute for Azure AD to record consent
- 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
- Sign in to the Windows Virtual Desktop consent page as global administrator, as you did in step 2
- Select Accept
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):
- 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
- Sign in to the Windows Virtual Desktop consent page with a global administrator account.
- Click Accept
- Wait a minute for Azure AD to record consent
- 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
- Sign in to the Windows Virtual Desktop consent page as global administrator, as you did in step 2
- Select Accept
- Bingo! Fixed my issue! So we still have to do the consents like with the 2019 fall version.
- DavidBelanger
Microsoft
Consent will not be needed with the Spring Update in general but this is a temporary workaround for the Windows client.
- DavidBelanger
