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
Copy file name to clipboardExpand all lines: articles/confidential-computing/virtual-machine-metablob-disk.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,9 @@ ms.date: 09/05/2025
9
9
ms.author: raginjup
10
10
ms.reviewer: raginjup
11
11
---
12
-
# New capabilities for managing confidential VM disks
12
+
# New capabilities for managing confidential virtual machine disks
13
13
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.
15
15
16
16
> [!NOTE]
17
17
> 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
21
21
Before you begin, ensure you have the following:
22
22
23
23
* 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.
25
25
* The appropriate version of the tools you are using:
26
26
* Azure REST API version 2025-01-02 or later.
27
27
* Azure CLI version 2.77.0 or later.
28
28
* Azure PowerShell version 14.4.0 or later.
29
29
30
30
## 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.
32
32
33
33
### [Azure REST API](#tab/rest-access)
34
34
35
35
To get the VMMD SAS URI using the Azure REST API, use the `beginGetAccess` endpoint with version `2025-01-02` or later.
36
36
37
-
Grant access to a confidential VM disk
37
+
Grant access to a confidential virtual machine disk
38
38
* API: beginGetAccess
39
39
* New in response: securityMetadataAccessSAS
40
40
@@ -61,11 +61,11 @@ Status code: 200
61
61
"securityMetadataAccessSAS": "VM Metadata SAS URI"
62
62
}
63
63
```
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)
65
65
66
66
### [Azure CLI](#tab/cli-access)
67
67
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`.
69
69
70
70
**Example:**
71
71
@@ -103,7 +103,7 @@ Grant-AzDiskAccess `
103
103
-SecureVmGuestStateSas
104
104
```
105
105
> [!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.
107
107
108
108
**Returned value schema:**
109
109
@@ -121,7 +121,7 @@ Grant-AzDiskAccess `
121
121
122
122
### [Azure REST API](#tab/rest-create)
123
123
124
-
To create a confidential VM disk with VMMD URI
124
+
To create a confidential virtual machine disk with VMMD URI
125
125
* API: createOption ImportSecure
126
126
* Include: securityMetadataUri in the request
127
127
@@ -174,11 +174,11 @@ Status code: 200
174
174
}
175
175
}
176
176
```
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)
178
178
179
179
### [Azure CLI](#tab/cli-create)
180
180
181
-
To create a confidential VM disk with VMMD URI
181
+
To create a confidential virtual machine disk with VMMD URI
182
182
* Include the --security-metadata-uri parameter.
183
183
* Requires Azure CLI version 2.77.0 or later.
184
184
@@ -213,7 +213,7 @@ Grant-AzDiskAccess `
213
213
-SecureVmGuestStateSas
214
214
```
215
215
> [!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.
0 commit comments