Skip to content

Commit 29f9c72

Browse files
Merge pull request #293673 from cherylmc/bastion-upload
add download
2 parents f57df16 + 3eeb141 commit 29f9c72

9 files changed

+26
-26
lines changed

articles/bastion/connect-vm-native-client-linux.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ author: cherylmc
66
ms.service: azure-bastion
77
ms.custom: devx-track-azurecli, linux-related-content
88
ms.topic: how-to
9-
ms.date: 04/05/2024
9+
ms.date: 01/28/2025
1010
ms.author: cherylmc
1111
---
1212

1313
# Connect to a VM using Bastion and a Linux native client
1414

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.
1616

1717
:::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":::
1818

@@ -21,7 +21,7 @@ After you've configured Bastion for native client support, you can connect to a
2121
* Connect to a Linux VM using **az network bastion ssh**.
2222
* Connect to a Windows VM using **az network bastion tunnel**.
2323
* 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**.
2525

2626
## Prerequisites
2727

@@ -35,9 +35,9 @@ Verify that the following roles and ports are configured in order to connect to
3535

3636
## <a name="ssh"></a>Connect to a Linux VM
3737

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`.
3939

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.
4141

4242
This command lets you do the following:
4343

@@ -73,7 +73,7 @@ az network bastion ssh --name "<BastionName>" --resource-group "<ResourceGroupNa
7373

7474
#### <a name="VM-IP"></a>SSH to a Linux VM IP address
7575

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).
7777

7878
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.
7979

@@ -95,4 +95,4 @@ az network bastion ssh --name "<BastionName>" --resource-group "<ResourceGroupNa
9595

9696
## Next steps
9797

98-
[Upload or download files](vm-upload-download-native.md)
98+
[Transfer files](vm-upload-download-native.md)

articles/bastion/connect-vm-native-client-windows.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ author: cherylmc
66
ms.service: azure-bastion
77
ms.custom: devx-track-azurecli
88
ms.topic: how-to
9-
ms.date: 04/05/2024
9+
ms.date: 01/28/2025
1010
ms.author: cherylmc
1111
---
1212

1313
# Connect to a VM using Bastion and the Windows native client
1414

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.
1616

1717
:::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":::
1818

@@ -21,8 +21,8 @@ After you've configured Bastion for native client support, you can connect to a
2121
* Connect to a Windows VM using **az network bastion rdp**.
2222
* Connect to a Linux VM using **az network bastion ssh**.
2323
* 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**.
2626

2727
## <a name="prereq"></a>Prerequisites
2828

@@ -139,4 +139,4 @@ az network bastion ssh --name "<BastionName>" --resource-group "<ResourceGroupNa
139139

140140
## Next steps
141141

142-
[Upload or download files](vm-upload-download-native.md)
142+
[Transfer files](vm-upload-download-native.md)

articles/bastion/native-client.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,20 +5,20 @@ description: Learn how to configure Bastion for native client connections.
55
author: cherylmc
66
ms.service: azure-bastion
77
ms.topic: how-to
8-
ms.date: 01/24/2025
8+
ms.date: 01/28/2025
99
ms.author: cherylmc
1010
---
1111

1212
# Configure Bastion for native client connections
1313

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.
1515

1616
:::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":::
1717

1818
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.
1919

20-
>[!NOTE]
21-
>[!INCLUDE [Pricing](~/reusable-content/ce-skilling/azure/includes/bastion-pricing.md)]
20+
> [!NOTE]
21+
> [!INCLUDE [Pricing](~/reusable-content/ce-skilling/azure/includes/bastion-pricing.md)]
2222
2323
## Deploy Bastion with the native client feature
2424

@@ -69,4 +69,4 @@ Use the following table to understand how to connect from native clients. Notice
6969

7070
* [Connect from a Windows native client](connect-vm-native-client-windows.md)
7171
* [Connect using the az network bastion tunnel command](connect-vm-native-client-linux.md)
72-
* [Upload or download files](vm-upload-download-native.md)
72+
* [Transfer files](vm-upload-download-native.md)

includes/bastion-native-connect-multi-tunnel.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: cherylmc
33
ms.service: azure-bastion
44
ms.topic: include
5-
ms.date: 08/08/2023
5+
ms.date: 01/28/2025
66
ms.author: cherylmc
77
---
88

includes/bastion-native-connect-tunnel.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22
author: cherylmc
33
ms.service: azure-bastion
44
ms.topic: include
5-
ms.date: 06/22/2023
5+
ms.date: 01/28/2025
66
ms.author: cherylmc
77
---
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:
99

1010
* Connect from native clients on *non*-Windows local computers. (For example, a Linux computer.)
1111
* Connect to a VM using SSH or RDP. (The bastion tunnel doesn't relay web servers or hosts.)
1212
* 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.
1414

1515
Limitations:
1616

includes/bastion-native-ip-address.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
author: cherylmc
33
ms.service: azure-bastion
44
ms.topic: include
5-
ms.date: 06/22/2023
5+
ms.date: 01/28/2025
66
ms.author: cherylmc
77
---
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).
99

1010
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.
1111

includes/bastion-native-pre-vm-connect.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: cherylmc
33
ms.service: azure-bastion
44
ms.topic: include
5-
ms.date: 07/19/2023
5+
ms.date: 01/28/2025
66
ms.author: cherylmc
77
---
88
Before you begin, verify that you have the following prerequisites:

includes/bastion-native-roles-ports.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: cherylmc
33
ms.service: azure-bastion
44
ms.topic: include
5-
ms.date: 06/12/2023
5+
ms.date: 01/28/2025
66
ms.author: cherylmc
77
---
88
### Required roles

includes/bastion-remote-desktop-users.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
author: cherylmc
44
ms.service: azure-bastion
55
ms.topic: include
6-
ms.date: 08/03/2023
6+
ms.date: 01/28/2025
77
ms.author: cherylmc
88

99
---

0 commit comments

Comments
 (0)