Hi Dragan Gataric,
Thank you for reaching out to Microsoft Q&A portal.
To assist you further and identify the root cause, we kindly request you to check few things from the Azure portal and on the affected client machine.
1. Once verify the "Preferred Application Group Type" of your Host Pool. To check this, follow the below steps:
- Go to Azure Portal > Azure Virtual Desktop > Host Pools.
- Select the relevant host pool.
- On the Overview tab, locate the setting for Preferred application group type. Please confirm if this setting is configured as “Desktop”. If this is set to “RemoteApp”, users will not see the full desktop experience even if assigned correctly.
2.Once Confirm if the users are assigned to the correct Desktop Application Group (DAG). To check this, follow the below steps:
- In the Host Pool, select Application groups from the left-hand menu.
- Click on your Desktop Application Group (not a RemoteApp group).
- On the left pane, go to Assignments. Please confirm that the correct users or user groups are explicitly listed and assigned here. 3. Also confirm your Session Host Availability. To check this, follow the below steps:
- Go to the Host Pool in Azure Portal.
- Click on Session Hosts from the left menu. Check whether at least one session host is showing as “Available”. If all session hosts are in states such as “Unavailable”, “Unhealthy”, or “Disconnected”, the desktop won’t be accessible to users.
4.Review the Windows App Version and Client Cache. To check this, follow the below steps:
- On your device, open the new Windows App.
- Click on the Settings to view the version number. Please share the Windows App version in use.
Additionally, once remove and re-add the workspace. This can resolve issues caused by stale or cached entitlements.
And also, please let us know few more things:
- Whether any changes were made recently to the VM images (e.g., switching to Community Gallery)?
- Were any Conditional Access, Intune, or Azure AD Join policies applied recently?
These details will help us determine whether a recent configuration or policy change may be contributing to the issue.