We have found that disabling Azure AD authentication under the RDP Properties of the session host pool will allow us to workaround the issue when 5020435 is installed on the session hosts. We do have a Microsoft support ticket open and we are awaiting further information, but I wanted to share this preliminary workaround. Note, this can also be worked around by removing enablerdsaadauth:i:1 from the Advanced tab under RDP Properties, too.
Unable to connect to Azure Remote Deskop after updates
After KB5020435 is applied to the AVD session hosts, and after updating the remote client's Remote Desktop app version beyond 1.2.3213, clients are unable to connect to the session hosts. After authentication, they receive the following error message: An authentication error has occurred. A specified logon session does not exist. It may have already been terminated. Error code: 0x0, extended error code: 0x0, Activity ID: 5278116b-4dd6-4e08-a3b8-5f1bce1c0000. If we uninstall that hotfix from the AVD session hosts or use an older version of the Remote Desktop client for Windows, this error does not occur.
Our AVD session hosts are running Windows 10 21H2.
End users are running a mix of operating systems and clients. The problem occurs with the Windows client (versions noted above), and with the web client, but does not occur on the Store App client or on macOS clients.