You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Connect to a VM using Bastion and a Linux native client
14
14
15
-
This article helps you connect via Azure Bastion to a VM in VNet using the native client on your local Linux computer. The native client feature lets you connect to your target VMs via Bastion using Azure CLI, and expands your sign-in options to include local SSH key pair and Microsoft Entra ID. For more information and steps to configure Bastion for native client connections, see [Configure Bastion for native client connections](native-client.md). Connections via native client require the Bastion Standard SKU or higher.
15
+
This article helps you connect via Azure Bastion to a VM in virtual network using the native client on your local Linux computer. The native client feature lets you connect to your target VMs via Bastion using Azure CLI, and expands your sign-in options to include local SSH key pair and Microsoft Entra ID. For more information and steps to configure Bastion for native client connections, see [Configure Bastion for native client connections](native-client.md). Connections via native client require the Bastion Standard SKU or higher.
16
16
17
17
:::image type="content" source="./media/native-client/native-client-architecture.png" alt-text="Diagram shows a connection via native client." lightbox="./media/native-client/native-client-architecture.png":::
18
18
@@ -21,7 +21,7 @@ After you've configured Bastion for native client support, you can connect to a
21
21
* Connect to a Linux VM using **az network bastion ssh**.
22
22
* Connect to a Windows VM using **az network bastion tunnel**.
23
23
* Connect to any VM using **az network bastion tunnel**.
24
-
*[Upload files](vm-upload-download-native.md#tunnel-command) to your target VM over SSH using **az network bastion tunnel**. File download from the target VM to the local client is currently not supported for this command.
24
+
*[Transfer files](vm-upload-download-native.md#tunnel-command) to your target VM over SSH using **az network bastion tunnel**.
25
25
26
26
## Prerequisites
27
27
@@ -35,9 +35,9 @@ Verify that the following roles and ports are configured in order to connect to
35
35
36
36
## <aname="ssh"></a>Connect to a Linux VM
37
37
38
-
The steps in the following sections help you connect to a Linux VM from a Linux native client using the **az network bastion** command. This extension can be installed by running, `az extension add --name bastion`.
38
+
The steps in the following sections help you connect to a Linux VM from a Linux native client using the **az network bastion** command. This extension can be installed by running, `az extension add --name bastion`.
39
39
40
-
When you connect using this command, file transfers aren't supported. If you want to upload files, connect using the [az network bastion tunnel](#tunnel) command instead.
40
+
When you connect using this command, file transfers aren't supported. If you want to transfer files, connect using the [az network bastion tunnel](#tunnel) command instead.
#### <aname="VM-IP"></a>SSH to a Linux VM IP address
75
75
76
-
You can connect to a VM private IP address instead of the resource ID. Be aware that Microsoft Entra authentication, and custom ports and protocols aren't supported when using this type of connection. For more information about IP-based connections, see [Connect to a VM - IP address](connect-ip-address.md).
76
+
You can connect to a VM private IP address instead of the resource ID. Microsoft Entra ID authentication, and custom ports and protocols, aren't supported when using this type of connection. For more information about IP-based connections, see [Connect to a VM - IP address](connect-ip-address.md).
77
77
78
78
Using the `az network bastion` command, replace `--target-resource-id` with `--target-ip-address` and the specified IP address to connect to your VM. The following example uses --ssh-key for the authentication method.
Copy file name to clipboardExpand all lines: articles/bastion/connect-vm-native-client-windows.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ author: cherylmc
6
6
ms.service: azure-bastion
7
7
ms.custom: devx-track-azurecli
8
8
ms.topic: how-to
9
-
ms.date: 04/05/2024
9
+
ms.date: 01/28/2025
10
10
ms.author: cherylmc
11
11
---
12
12
13
13
# Connect to a VM using Bastion and the Windows native client
14
14
15
-
This article helps you connect to a VM in the VNet using the native client (SSH or RDP) on your local Windows computer. The native client feature lets you connect to your target VMs via Bastion using Azure CLI, and expands your sign-in options to include local SSH key pair and Microsoft Entra ID. For more information and steps to configure Bastion for native client connections, see [Configure Bastion for native client connections](native-client.md). Connections via native client require the Bastion Standard SKU or higher.
15
+
This article helps you connect to a VM in the virtual network using the native client (SSH or RDP) on your local Windows computer. The native client feature lets you connect to your target VMs via Bastion using Azure CLI, and expands your sign-in options to include local SSH key pair and Microsoft Entra ID. For more information and steps to configure Bastion for native client connections, see [Configure Bastion for native client connections](native-client.md). Connections via native client require the Bastion Standard SKU or higher.
16
16
17
17
:::image type="content" source="./media/native-client/native-client-architecture.png" alt-text="Diagram shows a connection via native client." lightbox="./media/native-client/native-client-architecture.png":::
18
18
@@ -21,8 +21,8 @@ After you've configured Bastion for native client support, you can connect to a
21
21
* Connect to a Windows VM using **az network bastion rdp**.
22
22
* Connect to a Linux VM using **az network bastion ssh**.
23
23
* Connect to a VM using **az network bastion tunnel**.
24
-
*[Upload and download files](vm-upload-download-native.md#rdp) over RDP.
25
-
*Upload files over SSH using **az network bastion tunnel**.
24
+
*[Transfer files](vm-upload-download-native.md#rdp) over RDP.
25
+
*Transfer files over SSH using **az network bastion tunnel**.
Copy file name to clipboardExpand all lines: articles/bastion/native-client.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,20 +5,20 @@ description: Learn how to configure Bastion for native client connections.
5
5
author: cherylmc
6
6
ms.service: azure-bastion
7
7
ms.topic: how-to
8
-
ms.date: 01/24/2025
8
+
ms.date: 01/28/2025
9
9
ms.author: cherylmc
10
10
---
11
11
12
12
# Configure Bastion for native client connections
13
13
14
-
This article helps you configure your Bastion deployment to accept connections from the native client (SSH or RDP) on your local computer to VMs located in the virtual network. The native client feature lets you connect to your target VMs via Bastion using Azure CLI, and expands your sign-in options to include local SSH key pair and Microsoft Entra ID. Additionally, you can also upload or download files, depending on the connection type and client.
14
+
This article helps you configure your Bastion deployment to accept connections from the native client (SSH or RDP) on your local computer to VMs located in the virtual network. The native client feature lets you connect to your target VMs via Bastion using Azure CLI, and expands your sign-in options to include local SSH key pair and Microsoft Entra ID. Additionally, you can also transfer files, depending on the connection type and client.
15
15
16
16
:::image type="content" source="./media/native-client/native-client-architecture.png" alt-text="Diagram shows a connection via native client." lightbox="./media/native-client/native-client-architecture.png":::
17
17
18
18
You can configure this feature by modifying an existing Bastion deployment, or you can deploy Bastion with the feature configuration already specified. Your capabilities on the VM when connecting via native client are dependent on what is enabled on the native client.
Copy file name to clipboardExpand all lines: includes/bastion-native-connect-tunnel.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,15 +2,15 @@
2
2
author: cherylmc
3
3
ms.service: azure-bastion
4
4
ms.topic: include
5
-
ms.date: 06/22/2023
5
+
ms.date: 01/28/2025
6
6
ms.author: cherylmc
7
7
---
8
-
The **az network bastion tunnel** command is another way that you can connect to your VMs. When you use this command, you can do the following:
8
+
The **az network bastion tunnel** command is another way that you can connect to your VMs. When you use this command, you can do the following:
9
9
10
10
* Connect from native clients on *non*-Windows local computers. (For example, a Linux computer.)
11
11
* Connect to a VM using SSH or RDP. (The bastion tunnel doesn't relay web servers or hosts.)
12
12
* Use the native client of your choice.
13
-
*[Upload files](../articles/bastion/vm-upload-download-native.md#tunnel-command) to your target VM from your local computer. File download from the target VM to the local client is currently not supported for this command.
13
+
*[Transfer files](../articles/bastion/vm-upload-download-native.md#tunnel-command) to your target VM from your local computer. File download from the target VM to the local client is currently not supported for this command.
Copy file name to clipboardExpand all lines: includes/bastion-native-ip-address.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,10 @@
2
2
author: cherylmc
3
3
ms.service: azure-bastion
4
4
ms.topic: include
5
-
ms.date: 06/22/2023
5
+
ms.date: 01/28/2025
6
6
ms.author: cherylmc
7
7
---
8
-
You can also connect to a VM private IP address, instead of the resource ID. Microsoft Entra authentication, and custom ports and protocols aren't supported when using this type of connection. For more information about IP-based connections, see [Connect to a VM - IP address](../articles/bastion/connect-ip-address.md).
8
+
You can also connect to a VM private IP address, instead of the resource ID. Microsoft Entra ID authentication, and custom ports and protocols, aren't supported when using this type of connection. For more information about IP-based connections, see [Connect to a VM - IP address](../articles/bastion/connect-ip-address.md).
9
9
10
10
Using the `az network bastion tunnel` command, replace `--target-resource-id` with `--target-ip-address` and the specified IP address to connect to your VM.
0 commit comments