Skip to content

Commit 387ff17

Browse files
authored
Update terminology from 'VM' to 'virtual machine'
1 parent 5544296 commit 387ff17

1 file changed

Lines changed: 12 additions & 12 deletions

File tree

articles/confidential-computing/virtual-machine-metablob-disk.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@ ms.date: 09/05/2025
99
ms.author: raginjup
1010
ms.reviewer: raginjup
1111
---
12-
# New capabilities for managing confidential VM disks
12+
# New capabilities for managing confidential virtual machine disks
1313

14-
This article outlines the changes to be aware when using confidential VMs with Virtual Machine Metadata (VMMD) blob.
14+
This article outlines the changes to be aware when using confidential virtual machines with Virtual Machine Metadata (VMMD) blob.
1515

1616
> [!NOTE]
1717
> The VMMD feature support described here are available in Azure REST API version **2025-01-02** and later, Azure CLI version **2.77.0** and later, Azure PowerShell version **14.4.0** and later.
@@ -21,20 +21,20 @@ This article outlines the changes to be aware when using confidential VMs with V
2121
Before you begin, ensure you have the following:
2222

2323
* An Azure account with an active subscription. [Create an account for free.](https://azure.microsoft.com/free)
24-
* A confidential VM with managed disks.
24+
* A confidential virtual machine with managed disks.
2525
* The appropriate version of the tools you are using:
2626
* Azure REST API version 2025-01-02 or later.
2727
* Azure CLI version 2.77.0 or later.
2828
* Azure PowerShell version 14.4.0 or later.
2929

3030
## Disk Access
31-
The process for granting access to confidential VM disks has been updated to provide a SAS URI for the VMMD blob. This is in addition to the existing SAS URIs for the OS disk and the VM guest state (VMGS) blob.
31+
The process for granting access to confidential virtual machine disks has been updated to provide a SAS URI for the Virtual Machine Metadata Disk (VMMD) blob. This is in addition to the existing SAS URIs for the OS disk and the VM guest state (VMGS) blob.
3232

3333
### [Azure REST API](#tab/rest-access)
3434

3535
To get the VMMD SAS URI using the Azure REST API, use the `beginGetAccess` endpoint with version `2025-01-02` or later.
3636

37-
Grant access to a confidential VM disk
37+
Grant access to a confidential virtual machine disk
3838
* API: beginGetAccess
3939
* New in response: securityMetadataAccessSAS
4040

@@ -61,11 +61,11 @@ Status code: 200
6161
"securityMetadataAccessSAS": "VM Metadata SAS URI"
6262
}
6363
```
64-
Detailed documentation and more examples using Java, Go, JavaScript or dotnet [are available here.](/rest/api/compute/disks/create-or-update?view=rest-compute-2025-01-02&tabs=HTTP#create-a-managed-disk-from-importsecure-create-option-with-metadata-uri-for-confidential-vm&preserve-view=true)
64+
Detailed documentation and more examples using Java, Go, JavaScript, or dotnet [are available here.](/rest/api/compute/disks/create-or-update?view=rest-compute-2025-01-02&tabs=HTTP#create-a-managed-disk-from-importsecure-create-option-with-metadata-uri-for-confidential-vm&preserve-view=true)
6565

6666
### [Azure CLI](#tab/cli-access)
6767

68-
When using the `az disk grant-access` command in Azure CLI version 2.77.0 or later, confidential VMs with 3 blobs will include the `securityMetadataAccessSAS`.
68+
When using the `az disk grant-access` command in Azure CLI version 2.77.0 or later, confidential virtual machines with three blobs include the `securityMetadataAccessSAS`.
6969

7070
**Example:**
7171

@@ -103,7 +103,7 @@ Grant-AzDiskAccess `
103103
-SecureVmGuestStateSas
104104
```
105105
> [!NOTE]
106-
> Multiline commands in PowerShell require a trailing backtick (\`) character which must have a space preceding it. There should NOT be any space or trailing comments after the backtick (\`) either. You may avoid this issue by entering the whole command in a single line.
106+
> Multiline commands in PowerShell require a trailing backtick (\`) character, which must have a space preceding it. There should NOT be any space or trailing comments after the backtick (\`) either. You may avoid this issue by entering the whole command in a single line.
107107
108108
**Returned value schema:**
109109

@@ -121,7 +121,7 @@ Grant-AzDiskAccess `
121121

122122
### [Azure REST API](#tab/rest-create)
123123

124-
To create a confidential VM disk with VMMD URI
124+
To create a confidential virtual machine disk with VMMD URI
125125
* API: createOption ImportSecure
126126
* Include: securityMetadataUri in the request
127127

@@ -174,11 +174,11 @@ Status code: 200
174174
}
175175
}
176176
```
177-
Detailed documentation and more examples using Java, Go, JavaScript or dotnet [are available here.](/rest/api/compute/disks/create-or-update?view=rest-compute-2025-01-02&tabs=HTTP#create-a-managed-disk-from-importsecure-create-option-with-metadata-uri-for-confidential-vm&preserve-view=true)
177+
Detailed documentation and more examples using Java, Go, JavaScript, or dotnet [are available here.](/rest/api/compute/disks/create-or-update?view=rest-compute-2025-01-02&tabs=HTTP#create-a-managed-disk-from-importsecure-create-option-with-metadata-uri-for-confidential-vm&preserve-view=true)
178178

179179
### [Azure CLI](#tab/cli-create)
180180

181-
To create a confidential VM disk with VMMD URI
181+
To create a confidential virtual machine disk with VMMD URI
182182
* Include the --security-metadata-uri parameter.
183183
* Requires Azure CLI version 2.77.0 or later.
184184

@@ -213,7 +213,7 @@ Grant-AzDiskAccess `
213213
-SecureVmGuestStateSas
214214
```
215215
> [!NOTE]
216-
> Multiline commands in PowerShell require a trailing backtick (\`) character which must have a space preceding it. There should NOT be any space or trailing comments after the backtick (\`) either. You may avoid this issue by entering the whole command in a single line.
216+
> Multiline commands in PowerShell require a trailing backtick (\`) character, which must have a space preceding it. There should NOT be any space or trailing comments after the backtick (\`) either. You may avoid this issue by entering the whole command in a single line.
217217
218218
**Returned value schema:**
219219

0 commit comments

Comments
 (0)