Share via

Given Single session Hostpool Access but not showing in the Windows app

Vittal Kasaram 40 Reputation points
2026-05-15T04:10:36.4366667+00:00

Hi ,

I given access to single session hostpool but not showing in the windows App..

But Multisession Hostpool it was showing.. Pls suggest

Thanks

Azure Virtual Desktop
Azure Virtual Desktop

A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ankit Yadav 14,445 Reputation points Microsoft External Staff Moderator
    2026-05-15T07:28:32.6333333+00:00

    Hello Vittal,

    Based on your description, the behavior you are seeing is not specific to single-session host pools. In Azure Virtual Desktop, both single-session and multi-session host pools are published to users through application groups and workspaces in the same way. If a resource is not appearing in the Windows Remote Desktop client, it usually indicates a configuration or assignment gap rather than a platform limitation.

    Please verify the following points:

    • Application group assignment: Ensure that your single-session host pool has a Desktop application group and that the required user or group is assigned to it. Without this assignment, the resource will not appear in the client.
    • Workspace association: Confirm that this Desktop application group is correctly associated with a workspace. Only application groups that are assigned to a workspace are published to users.
    • Client subscription and refresh: After making changes, allow some time for the configuration to propagate. Then refresh or re-subscribe to the workspace in the Remote Desktop client to retrieve the latest feed.
    • Client validity: Ensure you are using a supported Azure Virtual Desktop client and that you are signed in with the same account that has been assigned access.

    This behavior is consistent with how Azure Virtual Desktop publishes resources. There is no documented difference where single-session host pools would not appear while multi-session host pools do, provided both are configured correctly.

    If the issue persists after validating the above, you may want to double-check that the correct workspace is being used and that the user assignment is applied to the intended application group.

    References:

    Was this answer helpful?

    0 comments
  2. Vittal Kasaram 40 Reputation points
    2026-05-15T04:16:11.7533333+00:00
    1. App group access The Windows app shows resources from application groups (Desktop or RemoteApp). Ensure:
      • The user is granted access to the desktop application group associated with the personal host pool.
      • Use Get-RdsAppGroupUser (Microsoft.RDInfra.RDPowershell) to verify that the user principal name is listed for the app group. If not, add the user to that app group and test again.
      Where i can get this ..?

    Was this answer helpful?

  3. AI answer

    2026-05-15T04:10:49.0533333+00:00

    For a single-session (personal) host pool to appear in the Windows app, confirm these points step by step:

    1. Host pool type and assignment
      Single-session access normally means a Personal host pool. In a personal host pool, users must be assigned to a specific session host, or automatic assignment must be enabled:
      • In the host pool properties, ensure Host pool type is set to Personal.
      • Check Assignment type:
        • Automatic: the service assigns the first available personal desktop to the user on first sign-in.
        • Direct: each user must be explicitly assigned to a session host. Make sure the affected user is assigned.
          If the user is not assigned (and assignment type is Direct), the desktop will not appear in the client.
    2. App group access
      The Windows app shows resources from application groups (Desktop or RemoteApp). Ensure:
      • The user is granted access to the desktop application group associated with the personal host pool.
      • Use Get-RdsAppGroupUser (Microsoft.RDInfra.RDPowershell) to verify that the user principal name is listed for the app group. If not, add the user to that app group and test again.
    3. Workspace/feed and visibility
      • Confirm the Workspace that contains the personal host pool’s app group is subscribed in the Windows app.
      • If using private access / Private Link for the Workspace or host pool, verify the client has network line-of-sight to the private endpoints. Misconfigured private access can prevent feed discovery or resource enumeration.
    4. Session host registration and status
      • Make sure at least one session host in the personal host pool is correctly registered and Available:
        • The VM must be domain-joined (Microsoft Entra ID or AD DS / Entra Domain Services).
        • Azure Virtual Desktop Agent and Agent Bootloader must be installed and registered with a valid registration token, as described in the session host registration steps.
        • After registration, the host should appear in the host pool with status Available; if needed, restart the VM once the agent is up to date.
      • If no session host is available, the desktop may not appear or may be unusable.
    5. Compare with working multi-session host pool
      Since the multi-session host pool appears correctly:
      • Compare app group assignments: ensure the same user is added to the personal host pool’s desktop app group.
      • Compare Workspace configuration: both app groups should be associated with the same Workspace (or the Workspace the Windows app is subscribed to).

    If, after these checks, the personal desktop still does not appear, re-verify user assignment to the personal host pool and app group with Get-RdsAppGroupUser, and confirm the session host is registered and Available.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.