Skip to content

Commit 67a4ab6

Browse files
Merge pull request #259213 from mayankdaruka-msft/mayankdaruka/update-vmaccess-docs
Update VMAccess Linux docs
2 parents 3b2d8ab + 3803156 commit 67a4ab6

9 files changed

+335
-280
lines changed

articles/bastion/bastion-connect-vm-ssh-linux.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ Use the following steps to authenticate using a password from Azure Key Vault.
113113
* Make sure you have **List** and **Get** access to the secrets stored in the Key Vault resource. To assign and modify access policies for your Key Vault resource, see [Assign a Key Vault access policy](../key-vault/general/assign-access-policy-portal.md).
114114

115115
> [!NOTE]
116-
> Please store your SSH private key as a secret in Azure Key Vault using the **PowerShell** or **Azure CLI** experience. Storing your private key via the Azure Key Vault portal experience will interfere with the formatting and result in unsuccessful login. If you did store your private key as a secret using the portal experience and no longer have access to the original private key file, see [Update SSH key](../virtual-machines/extensions/vmaccess.md#update-ssh-key) to update access to your target VM with a new SSH key pair.
116+
> Please store your SSH private key as a secret in Azure Key Vault using the **PowerShell** or **Azure CLI** experience. Storing your private key via the Azure Key Vault portal experience will interfere with the formatting and result in unsuccessful login. If you did store your private key as a secret using the portal experience and no longer have access to the original private key file, see [Update SSH key](../virtual-machines/extensions/vmaccess-linux.md#update-ssh-key) to update access to your target VM with a new SSH key pair.
117117
>
118118
119119
1. To work with the VM in a new browser tab, select **Open in new browser tab**.
@@ -163,7 +163,7 @@ Use the following steps to authenticate using a private key stored in Azure Key
163163
* Make sure you have **List** and **Get** access to the secrets stored in the Key Vault resource. To assign and modify access policies for your Key Vault resource, see [Assign a Key Vault access policy](../key-vault/general/assign-access-policy-portal.md).
164164

165165
> [!NOTE]
166-
> Please store your SSH private key as a secret in Azure Key Vault using the **PowerShell** or **Azure CLI** experience. Storing your private key via the Azure Key Vault portal experience will interfere with the formatting and result in unsuccessful login. If you did store your private key as a secret using the portal experience and no longer have access to the original private key file, see [Update SSH key](../virtual-machines/extensions/vmaccess.md#update-ssh-key) to update access to your target VM with a new SSH key pair.
166+
> Please store your SSH private key as a secret in Azure Key Vault using the **PowerShell** or **Azure CLI** experience. Storing your private key via the Azure Key Vault portal experience will interfere with the formatting and result in unsuccessful login. If you did store your private key as a secret using the portal experience and no longer have access to the original private key file, see [Update SSH key](../virtual-machines/extensions/vmaccess-linux.md#update-ssh-key) to update access to your target VM with a new SSH key pair.
167167
>
168168
169169
* **Azure Key Vault Secret**: Select the Key Vault secret containing the value of your SSH private key.

articles/bastion/bastion-connect-vm-ssh-windows.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ Use the following steps to authenticate using a password from Azure Key Vault.
129129
* Make sure you have **List** and **Get** access to the secrets stored in the Key Vault resource. To assign and modify access policies for your Key Vault resource, see [Assign a Key Vault access policy](../key-vault/general/assign-access-policy-portal.md).
130130

131131
> [!NOTE]
132-
> Please store your SSH private key as a secret in Azure Key Vault using the **PowerShell** or **Azure CLI** experience. Storing your private key via the Azure Key Vault portal experience will interfere with the formatting and result in unsuccessful login. If you did store your private key as a secret using the portal experience and no longer have access to the original private key file, see [Update SSH key](../virtual-machines/extensions/vmaccess.md#update-ssh-key) to update access to your target VM with a new SSH key pair.
132+
> Please store your SSH private key as a secret in Azure Key Vault using the **PowerShell** or **Azure CLI** experience. Storing your private key via the Azure Key Vault portal experience will interfere with the formatting and result in unsuccessful login. If you did store your private key as a secret using the portal experience and no longer have access to the original private key file, see [Update SSH key](../virtual-machines/extensions/vmaccess-linux.md#update-ssh-key) to update access to your target VM with a new SSH key pair.
133133
>
134134
135135
1. To work with the VM in a new browser tab, select **Open in new browser tab**.
@@ -156,7 +156,7 @@ Use the following steps to authenticate using a private key stored in Azure Key
156156
* Make sure you have **List** and **Get** access to the secrets stored in the Key Vault resource. To assign and modify access policies for your Key Vault resource, see [Assign a Key Vault access policy](../key-vault/general/assign-access-policy-portal.md).
157157

158158
> [!NOTE]
159-
> Please store your SSH private key as a secret in Azure Key Vault using the **PowerShell** or **Azure CLI** experience. Storing your private key via the Azure Key Vault portal experience will interfere with the formatting and result in unsuccessful login. If you did store your private key as a secret using the portal experience and no longer have access to the original private key file, see [Update SSH key](../virtual-machines/extensions/vmaccess.md#update-ssh-key) to update access to your target VM with a new SSH key pair.
159+
> Please store your SSH private key as a secret in Azure Key Vault using the **PowerShell** or **Azure CLI** experience. Storing your private key via the Azure Key Vault portal experience will interfere with the formatting and result in unsuccessful login. If you did store your private key as a secret using the portal experience and no longer have access to the original private key file, see [Update SSH key](../virtual-machines/extensions/vmaccess-linux.md#update-ssh-key) to update access to your target VM with a new SSH key pair.
160160
>
161161
162162
* **Azure Key Vault Secret**: Select the Key Vault secret containing the value of your SSH private key.

articles/virtual-machines/.openpublishing.redirection.virtual-machines.json

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1307,12 +1307,17 @@
13071307
},
13081308
{
13091309
"source_path_from_root": "/articles/virtual-machines/linux/using-vmaccess-extension.md",
1310-
"redirect_url": "/azure/virtual-machines/extensions/vmaccess",
1310+
"redirect_url": "/azure/virtual-machines/extensions/vmaccess-linux",
13111311
"redirect_document_id": false
13121312
},
13131313
{
13141314
"source_path_from_root": "/articles/virtual-machines/linux/using-vmaccess-extension-nodejs.md",
1315-
"redirect_url": "/azure/virtual-machines/extensions/vmaccess",
1315+
"redirect_url": "/azure/virtual-machines/extensions/vmaccess-linux",
1316+
"redirect_document_id": false
1317+
},
1318+
{
1319+
"source_path_from_root": "/articles/virtual-machines/extensions/vmaccess.md",
1320+
"redirect_url": "/azure/virtual-machines/extensions/vmaccess-linux",
13161321
"redirect_document_id": false
13171322
},
13181323
{

articles/virtual-machines/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1069,8 +1069,8 @@
10691069
- name: Use templates
10701070
displayName: Desired state configuration, dsc
10711071
href: ./extensions/dsc-template.md
1072-
- name: Virtual machine access
1073-
href: ./extensions/vmaccess.md
1072+
- name: VMAccess for Linux
1073+
href: ./extensions/vmaccess-linux.md
10741074
- name: Third-party extensions
10751075
items:
10761076
- name: Chef

articles/virtual-machines/copy-files-to-vm-using-scp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,4 +67,4 @@ The `-r` flag instructs SCP to recursively copy the files and directories from t
6767

6868
## Next steps
6969

70-
* [Manage users, SSH, and check or repair disks on Azure Linux VMs using the 'VMAccess' Extension](./extensions/vmaccess.md)
70+
* [Manage users, SSH, and check or repair disks on Azure Linux VMs using the 'VMAccess' Extension](./extensions/vmaccess-linux.md)

articles/virtual-machines/extensions/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Otherwise, specific troubleshooting information for each extension can be found
6565
| microsoft.enterprisecloud.monitoring.omsagentforlinux | [Azure Monitor for Linux](oms-linux.md#troubleshoot-and-support)
6666
| microsoft.enterprisecloud.monitoring.microsoftmonitoringagent | [Azure Monitor for Windows](oms-windows.md#troubleshoot-and-support) |
6767
| stackify.linuxagent.extension.stackifylinuxagentextension | [Stackify Retrace for Linux](stackify-retrace-linux.md#troubleshoot-and-support) |
68-
| vmaccessforlinux.microsoft.ostcextensions | [Reset password for Linux](vmaccess.md#troubleshoot-and-support) |
68+
| vmaccessforlinux.microsoft.ostcextensions | [VMAccess for Linux](vmaccess-linux.md#troubleshoot-and-support) |
6969
| microsoft.recoveryservices.vmsnapshot | [Snapshot for Linux](vmsnapshot-linux.md#troubleshoot-and-support) |
7070
| microsoft.recoveryservices.vmsnapshot | [Snapshot for Windows](vmsnapshot-windows.md#troubleshoot-and-support) |
7171

0 commit comments

Comments
 (0)