Let’s Fix AVD Refreshing Your Token Error. I don’t know how many of you have seen this AVD issue Oops, we couldn’t connect to “Session Desktop”.
Well, it’s not an issue instead it’s more a security feature! I regularly get this error message when I try to access the session desktop after around ~20-30 minutes of idle time (especially with the AVD web Client).
Let’s see how to fix it quickly. Well, there is nothing much to fix it. This post is more for end-users who get surprised by this error sometimes. I have seen a couple of times end users raising a ticket for this issue.
Refresh and Session token Policies for AVD
You can read more about Azure AD refresh and session tokens-related configuration from Microsoft docs. In Azure AD, a policy object represents a set of rules that are enforced on individual applications or on all applications in an organization.
Each policy type has a unique structure, with a set of properties that are applied to objects to which they are assigned.
Error Message & Fix
The following is the exact error message that you get mostly because of a time-out.
Oops, we couldn’t connect to “Session Desktop”. We ate working on refreshing your token, please try again after a short while or refresh the page.
- The fix is to click on the REFRESH button.
- In most of the scenarios, this refresh helps. If not, check out the following steps.
- Logoff from the AVD Web client portal. https://aka.ms/wvdARMweb
Close Browser, Re-open, and Login back.
Resources
- Install Subscribe Windows RD Client for AVD End User Step by Step Guide
- Microsoft VDI Story AVD Concept Setup Guide Myths Known Issues
- AVD Video PlayList ➡➡https://aka.ms/WVDPlaylist
- AVD AMA 28th Aug 2019 Azure Virtual Desktop Microsoft AVD FAQs from AMA
- Microsoft VDI Story AVD Concept Setup Guide Myths Known Issues
- SCCM Intune Support for Persistent Non-Persistent VDI VMs
Author
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…