How to configure Bastion for Kerberos authentication using the Azure portal (Preview)

This article shows you how to configure Azure Bastion to use Kerberos authentication. Kerberos authentication can be used with both the Basic and the Standard Bastion SKUs. For more information about Kerberos authentication, see the Kerberos authentication overview. For more information about Azure Bastion, see What is Azure Bastion?


  • During Preview, the Kerberos setting for Azure Bastion can be configured in the Azure portal only.
  • VMs migrated from on-premises to Azure are not currently supported for Kerberos. 
  • Cross-realm authentication is not currently supported for Kerberos. 


  • An Azure account with an active subscription. If you don't have one, create one for free. To be able to connect to a VM through your browser using Bastion, you must be able to sign in to the Azure portal.

  • An Azure virtual network. For steps to create a VNet, see Quickstart: Create a virtual network.

Update VNet DNS servers

In this section, the following steps help you update your virtual network to specify custom DNS settings.

  1. Sign in to the Azure portal.
  2. Go to the virtual network for which you want to deploy the Bastion resources.
  3. Go to the DNS servers page for your VNet and select Custom. Add the IP address of your Azure-hosted domain controller and Save.

Deploy Bastion

  1. Begin configuring your bastion deployment using the steps in Tutorial: Deploy Bastion using manual configuration settings. Configure the settings on the Basics tab. Then, at the top of the page, click Advanced to go to the Advanced tab.

  2. On the Advanced tab, select Kerberos.

    Screenshot of select bastion features.

  3. At the bottom of the page, select Review + create, then Create to deploy Bastion to your virtual network.

  4. Once the deployment completes, you can use it to sign in to any reachable Windows VMs joined to the custom DNS you specified in the earlier steps.

To modify an existing Bastion deployment

In this section, the following steps help you modify your virtual network and existing Bastion deployment for Kerberos authentication.

  1. Update the DNS settings for your virtual network.
  2. Go to the portal page for your Bastion deployment and select Configuration.
  3. On the Configuration page, select Kerberos authentication, then select Apply.
  4. Bastion will update with the new configuration settings.

To verify Bastion is using Kerberos

Once you have enabled Kerberos on your Bastion resource, you can verify that it's actually using Kerberos for authentication to the target domain-joined VM.

  1. Sign into the target VM (either via Bastion or not). Search for "Edit Group Policy" from the taskbar and open the Local Group Policy Editor.
  2. Select Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
  3. Find the policy Networking security: Restrict NTLM: Incoming NTLM Traffic and set it to Deny all domain accounts. Because Bastion uses NTLM for authentication when Kerberos is disabled, this setting ensures that NTLM-based authentication is unsuccessful for future sign-in attempts on the VM.
  4. End the VM session.
  5. Connect to the target VM again using Bastion. Sign-in should succeed, indicating that Bastion used Kerberos (and not NTLM) for authentication.

Next steps

For more information about Azure Bastion, see What is Azure Bastion?