An Azure service that provides private and fully managed Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines.
Thanks for reaching out in Microsoft Q&A forum,
I get this message: An internal error has occurred within the Bastion Host, and the connection has been terminated. If the problem persists, please contact support.
Your Azure Bastion host connection failure across all VMs, showing the "internal error" message, is a common issue often tied to network configuration, resource health, or transient service glitches.
- Check your Bastion resource's Resource Health in the portal it must show "Available"; if degraded, await auto-recovery.
- In the Azure portal, go to your Bastion resource > Overview: Verify provisioning state is "Succeeded" and SKU supports your needs (Standard/Premium for native clients). Ensure AzureBastionSubnet (min /26, 5+ IPs free) exists in the VNet and hosts no other resources. Enable diagnostics to Log Analytics for
BastionConnectionlogs if not already set. - Examine NSGs on AzureBastionSubnet and VM NIC/subnet:
- Inbound: Allow TCP 443 (GatewayManager service tag) and RDP/SSH (3389/22 from VNet).
- Outbound: Allow 443/22/3389 to VNet/internet (AzureCloud tag). Run Connection Troubleshoot in Bastion's Help tab via Network Watcher for automated diagnostics. Test incognito mode in Edge/Chrome, disabling VPNs/firewalls temporarily.
Reference:
Troubleshoot Azure Bastion | Microsoft Learn
Kindly let us know if the above helps or you need further assistance on this issue.
Please do not forget to
and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.