Optimising Windows App for hot-desk environments

Question

Micrisoft is replacing Remote Desktop with Windows App. We support multiple clients using AVD, connecting to multi-session hosts.

The Remote Desktop application does not require a login. In the hot-desk environment, the user selects their subscription from the list and connects.

With Windows App, the application itself requires a login. This means that when a different user comes to the workstation, the UI presents them with a resource ready to connect to, but Windows App is signed in as a different user. It is not immediately apparent to the user which account Windows App is already signed into. There is an avatar and initials, but that is pretty subtle. The new user should choose their name from the drop-down list of accounts that have previously signed in, and if not present, add a new account.

In addition, if the previous user has vacated that PC less than 5 minutes previously, the new user can double-click the resource and connect without authentication (MFA).

This presentation of Windows App to the user is not ideal.

In addition, for users who access AVD servers across multiple tenancies, managing this in Windows App is much more awkward.

Are there ways in which we can optimise this experience for hot-desk environments and multi-tenant clients?