A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
Hello @Shailesh Panday
Based on your description, this is expected behavior for Windows Server 2022.
For Microsoft Entra ID authentication over RDP, the operating system must support Microsoft Entra sign-in for Remote Desktop. Simply onboarding the server to Azure Arc and assigning the Windows Admin Center Administrator Login RBAC role doesn't enable Entra ID authentication for RDP on a workgroup (non-domain joined) Windows Server 2022 machine.
While Windows Admin Center can authenticate to the Arc-enabled server using Microsoft Entra ID, the RDP session itself has separate operating system requirements. Microsoft documents support for Microsoft Entra sign-in on newer Windows Server releases (such as Windows Server 2025), but Windows Server 2022 does not support Microsoft Entra authentication for RDP on a non-domain-joined server.
For Windows Server 2022, your supported options are:
- Use a local Windows account for RDP.
- Join the server to Active Directory Domain Services (AD DS) and authenticate with domain credentials.
- Upgrade to a supported Windows Server version that provides Microsoft Entra ID sign-in support for Remote Desktop, if that aligns with your requirements.
So, if the same configuration works on Windows Server 2025 but not Windows Server 2022, that is consistent with the current Microsoft support matrix rather than an Azure Arc or Windows Admin Center configuration issue.
If your goal is specifically to enable Entra ID authentication for RDP on Windows Server 2022 in a workgroup configuration, I'm not aware of a supported configuration that enables this today. If Microsoft has a newer support statement or roadmap, it would be helpful for the product team to clarify that in the documentation.
Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.