Skip to content

Commit ed24875

Browse files
committed
Final sync with Word doc
1 parent 13af766 commit ed24875

File tree

1 file changed

+10
-11
lines changed

1 file changed

+10
-11
lines changed

articles/marketplace/azure-vm-get-sas-uri.md

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -12,23 +12,22 @@ ms.date: 08/17/2022
1212
# Generate a SAS URI for a VM image
1313

1414
> [!NOTE]
15-
> A Shared access signature (SAS) URI can be used to publish your virtual machine (VM). Alternatively, you can share an image in Partner Center via Azure compute gallery. Refer to [Create a virtual machine using an approved base](azure-vm-use-approved-base.md) or [Create a virtual machine using your own image](azure-vm-use-own-image.md) instructions.
15+
> A Shared access signature (SAS) URI can be used to publish your virtual machine (VM). Alternatively, you can share an image in Partner Center via Azure compute gallery. Refer to [Create a virtual machine using an approved base](azure-vm-use-approved-base.md) or [Create a virtual machine using your own image](azure-vm-use-own-image.md) for further instructions.
1616
1717
Before getting started, you will need the following:
1818

19-
• a virtual machine
20-
• a [storage account](/azure/storage/common/storage-account-create?tabs=azure-portal) with a container for storing the virtual hard drive (VHD)
21-
• your [storage account key](/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys)
19+
- A virtual machine
20+
- A [storage account](/azure/storage/common/storage-account-create?tabs=azure-portal) with a container for storing the virtual hard drive (VHD)
21+
- Your [storage account key](/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys)
2222

23-
24-
## Extract vhd from a VM
23+
## Extract VHD from a VM
2524

2625
> [!NOTE]
2726
> You can skip this step if you already have a VHD uploaded to a storage account.
2827
2928
To extract the VHD from your VM, you need to first take a snapshot of your VM disk and then extract the VHD from the snapshot into your storage account.
3029

31-
Take a snapshot of your VM disk:
30+
### Take a snapshot of your VM disk
3231

3332
1. Sign in to the [Azure portal](https://www.portal.azure.com/).
3433
1. Select **Create a resource**, then search for and select **Snapshot**.
@@ -78,7 +77,7 @@ sas=$(az snapshot grant-access --resource-group $resourceGroupName --name $snaps
7877
az storage blob copy start --destination-blob $destinationVHDFileName --destination-container $storageContainerName --account-name $storageAccountName --account-key $storageAccountKey --source-uri $sas
7978
```
8079

81-
This script about uses the following commands to generate the SAS URI for a snapshot and copies the underlying VHD to a storage account using the SAS URI. Each command in the table links to command specific documentation.
80+
This script about uses the following commands to generate the SAS URI for a snapshot and copies the underlying VHD to a storage account using the SAS URI.
8281

8382
|Command |Notes |
8483
|---------|---------|
@@ -89,8 +88,8 @@ This script about uses the following commands to generate the SAS URI for a snap
8988

9089
There are two common tools used to create a SAS address (URI):
9190

92-
1. **Azure Storage browser** – Available on the Azure portal.
93-
2. **Azure CLI** – Recommended for non-Windows operating systems and automated or continuous integration environments.
91+
- **Azure Storage browser** – Available on the Azure portal.
92+
- **Azure CLI** – Recommended for non-Windows operating systems and automated or continuous integration environments.
9493

9594
### Using Tool 1: Azure Storage browser
9695

@@ -142,7 +141,7 @@ This table shows the common errors encountered when providing a shared access si
142141
| --- | --- | --- |
143142
| "?" is not found in SAS URI | `Must be a valid Azure shared access signature URI.` | Ensure that the SAS URI provided uses the proper syntax and includes the “?”character.<br>Syntax: `<blob-service-endpoint-url>?<sas-connection-string>` |
144143
| "st" parameter not in SAS URI | `Specified SAS URL cannot be reached.` | Update the SAS URI with proper **Start Date** ("st") value. |
145-
| "se" parameter not in SAS URI | `The end date parameter (se) is required.` | Update the SAS URI with proper End Date (“se”) value. |
144+
| "se" parameter not in SAS URI | `The end date parameter (se) is required.` | Update the SAS URI with proper **End Date** (“se”) value. |
146145
| "sp=r" not in SAS URI | `Missing Permissions (sp) must include 'read' (r).` | Update the SAS URI with permissions set as `Read` (“sp=r”). |
147146
| SAS URI Authorization error | `Failure: Copying Images. Not able to download blob due to authorization error.` | Review and correct the SAS URI format. Regenerate if necessary. |
148147
| SAS URI "st" and "se" parameters do not have full date-time specification | `The start time parameter (st) is not a valid date string.`<br>OR<br>`The end date parameter (se) is not a valid date string.` | SAS URI **Start Date** and **End Date** parameters (“st” and “se” substrings) must have full date-time format (YYYY-MM-DDT00:00:00Z), such as 11-02-2017T00:00:00Z. Shortened versions are invalid (some commands in Azure CLI may generate shortened values by default). |

0 commit comments

Comments
 (0)