Azure / Azure/azure-powershell
[Feature]: Azure Bastion Native Client Support in PowerShell
- Dominant language
- C#
- Stars
- 4.8k
- Forks
- 4.3k
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 54
Description
### Description of the new feature
AzureCLI has an option to connect to a VM on port 3389 or 22 for RDP or SSH, using the 'Native Client'.
https://docs.microsoft.com/en-us/azure/bastion/connect-native-client-windows
```powershell
az network bastion rdp --name "" --resource-group "" --target-resource-id ""
```
We have a few Bastion Network Cmdlets. These would also need updates to allow for the extra settings on the bastion that are in preview at the moment.
```powershell
gcm -module az.network -Name *bastion*
CommandType Name Version Source
----------- ---- ------- ------
Cmdlet Get-AzBastion 4.14.0 az.network
Cmdlet New-AzBastion 4.14.0 az.network
Cmdlet Remove-AzBastion 4.14.0 az.network
Cmdlet Set-AzBastion 4.14.0 az.network
```

### Proposed implementation details (optional)
Add support, parity with az cli.
https://docs.microsoft.com/en-us/rest/api/virtualnetwork/bastion-hosts/create-or-update#request-body
Contributor guide
Research direction
Start with the Azure CLI native-client example and the linked Bastion create-or-update REST request body. Then inspect the Get-AzBastion, New-AzBastion, Remove-AzBastion, and Set-AzBastion cmdlets to understand where the additional preview settings belong. Done means the PowerShell Bastion cmdlets provide parity for native RDP or SSH connections and the extra Bastion settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, powershell
- Domain
- cli, cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100