Skip to content

Commit 55cb4c0

Browse files
committed
add just-in-time
1 parent 3d4ac23 commit 55cb4c0

1 file changed

Lines changed: 11 additions & 4 deletions

File tree

articles/bastion/troubleshoot.md

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
title: 'Troubleshoot Azure Bastion'
33
description: Learn how to troubleshoot Azure Bastion.
44
services: bastion
5-
author: charwen
5+
author: isamorris
66
ms.service: bastion
77
ms.topic: troubleshooting
8-
ms.date: 05/08/2023
9-
ms.author: charwen
8+
ms.date: 01/11/2024
9+
ms.author: isamorris
1010
---
1111

1212
# Troubleshoot Azure Bastion
@@ -70,6 +70,13 @@ The key's randomart image is:
7070

7171
**A:** You can troubleshoot your connectivity issues by navigating to the **Connection Troubleshoot** tab (in the **Monitoring** section) of your Azure Bastion resource in the Azure portal. Network Watcher Connection Troubleshoot provides the capability to check a direct TCP connection from a virtual machine (VM) to a VM, fully qualified domain name (FQDN), URI, or IPv4 address. To start, choose a source to start the connection from, and the destination you wish to connect to and select "Check". For more information, see [Connection Troubleshoot](../network-watcher/network-watcher-connectivity-overview.md).
7272

73+
If just-in-time (JIT) is enabled, you might need to add additional role assignments to connect to Bastion. Add the following permissions to the user, and then try reconnecting to Bastion. For more information, see [Enable just-in-time access on VMs](../defender-for-cloud/just-in-time-access-usage.md).
74+
75+
| Setting | Description|
76+
|---|---|
77+
|Microsoft.Security/locations/jitNetworkAccessPolicies/read|Gets the just-in-time network access policies|
78+
Microsoft.Security/locations/jitNetworkAccessPolicies/write | Creates a new just-in-time network access policy or updates an existing one |
79+
7380

7481
## <a name="filetransfer"></a>File transfer issues
7582

@@ -81,7 +88,7 @@ The key's randomart image is:
8188

8289
**Q:** When I try to connect using Azure Bastion, I can't connect to the target VM, and I get a black screen in the Azure portal.
8390

84-
**A:** This happens when there's either a network connectivity issue between your web browser and Azure Bastion (your client Internet firewall may be blocking WebSockets traffic or similar), or between the Azure Bastion and your target VM. Most cases include an NSG applied either to AzureBastionSubnet, or on your target VM subnet that is blocking the RDP/SSH traffic in your virtual network. Allow WebSockets traffic on your client internet firewall, and check the NSGs on your target VM subnet. See [Unable to connect to virtual machine](#connectivity) to learn how to use **Connection Troubleshoot** to troubleshoot your connectivity issues.
91+
**A:** This happens when there's either a network connectivity issue between your web browser and Azure Bastion (your client Internet firewall might be blocking WebSockets traffic or similar), or between the Azure Bastion and your target VM. Most cases include an NSG applied either to AzureBastionSubnet, or on your target VM subnet that is blocking the RDP/SSH traffic in your virtual network. Allow WebSockets traffic on your client internet firewall, and check the NSGs on your target VM subnet. See [Unable to connect to virtual machine](#connectivity) to learn how to use **Connection Troubleshoot** to troubleshoot your connectivity issues.
8592

8693
## Next steps
8794

0 commit comments

Comments
 (0)