An Azure service that provides private and fully managed Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines.
just a simple and quick answer. VM config can be fine, Bastion UI/support just hasnt caught up yet & yeah this is likely platform support gap, not ur config. Bastion Entra ID login support is not always available for every new Windows Server image right away, and Windows Server 2025 may not be fully lit up in Bastion UI yet even if the VM itself is Entra joined and RBAC is correct. For now, use local admin or domain account through Bastion, or use normal RDP with Entra login where supported. For migration, dont remove local break-glass admin yet. Keep local admin disabled/rotated but available for recovery, assign Virtual Machine Administrator Login / Virtual Machine User Login, verify Entra login works outside Bastion first, then move users gradually. If Bastion still does not show Entra option only on Server 2025, open support and ask for Windows Server 2025 + Bastion Entra login support confirmation.
rgds, Alex
&
if my answer helps pls accept it.