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
> You don't need a SAS URI to publish your VM. You can simply share an image in Partner Center. 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.
16
16
17
-
Generating SAS URIs for your VHDs has these requirements:
17
+
Before getting started, you will need the following:
18
18
19
-
-Only List and Read permissions are required. Don't provide Write or Delete access.
20
-
-The duration for access (expiry date) should be a minimum of three weeks from when the SAS URI is created.
21
-
-To protect against UTC time changes, set the start date to one day before the current date. For example, if the current date is June 16, 2020, select 6/15/2020.
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)
> You can skip this step if you already have a vhd uploaded in a Storage Account.
26
+
> You can skip this step if you already have a VHD uploaded to a storage account.
27
27
28
-
To extract the vhd from your VM, you need to take a snapshot of your VM disk and extract vhd from the snapshot.
28
+
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.
29
29
30
-
Start by taking a snapshot of the VM disk:
30
+
### Take a snapshot of your VM disk
31
31
32
-
1. Sign in to the Azure portal.
33
-
2. Starting at the upper-left, select Create a resource, then search for and select Snapshot.
34
-
3. In the Snapshot blade, select Create.
35
-
4. Enter a Name for the snapshot.
36
-
5. Select an existing resource group or enter the name for a new one.
37
-
6. For Source disk, select the managed disk to snapshot.
38
-
7. Select the Account type to use to store the snapshot. Use Standard HDD unless you need it stored on a high performing SSD.
39
-
8. Select Create.
32
+
1. Sign in to the [Azure portal](https://www.portal.azure.com/).
33
+
1. Select **Create a resource**, then search for and select **Snapshot**.
34
+
1. In the Snapshot blade, select **Create**.
35
+
1. Select the **Subscription**. Select an existing resource group within the selected subscription or **Create new** and enter the name for a new resource group to be created. This is the resource group the snapshot will be associated to.
36
+
1. Enter a **Name** for the snapshot.
37
+
1. For **Source type**, select **Disk**.
38
+
1. Select the **Source subscription**, which is the subscription that contains the VM disk. This may be different from the destination subscription of the new snapshot.
39
+
1. For **Source disk**, select the managed disk to snapshot.
40
+
1. For the **Storage type**, select **Standard HDD** unless you need it stored on a high performing SSD.
41
+
1. Select **Review + Create**. Upon successful validation, select **Create**.
40
42
41
-
### Extract the VHD
43
+
### Extract the VHD into your storage account
42
44
43
-
Use the following script to export the snapshot into a VHD in your storage account.
45
+
Use the following script to export the snapshot into a VHD in your storage account. For each of parameters, insert your information accordingly.
44
46
45
47
```azurecli
46
48
#Provide the subscription Id where the snapshot is created
47
-
$subscriptionId=yourSubscriptionId
49
+
subscriptionId=yourSubscriptionId
48
50
49
51
#Provide the name of your resource group where the snapshot is created
50
-
$resourceGroupName=myResourceGroupName
52
+
resourceGroupName=myResourceGroupName
51
53
52
54
#Provide the snapshot name
53
-
$snapshotName=mySnapshot
55
+
snapshotName=mySnapshot
54
56
55
57
#Provide Shared Access Signature (SAS) expiry duration in seconds (such as 3600)
56
58
#Know more about SAS here: https://docs.microsoft.com/azure/storage/storage-dotnet-shared-access-signature-part-1
57
-
$sasExpiryDuration=3600
59
+
sasExpiryDuration=3600
58
60
59
-
#Provide storage account name where you want to copy the underlying VHD file. Currently, only general purpose v1 storage is supported.
60
-
$storageAccountName=mystorageaccountname
61
+
#Provide storage account name where you want to copy the underlying VHD file.
62
+
storageAccountName=mystorageaccountname
61
63
62
64
#Name of the storage container where the downloaded VHD will be stored.
63
-
$storageContainerName=mystoragecontainername
65
+
storageContainerName=mystoragecontainername
64
66
65
-
#Provide the key of the storage account where you want to copy the VHD
66
-
$storageAccountKey=mystorageaccountkey
67
+
#Provide the access key for the storage account that you want to copy the VHD to.
68
+
storageAccountKey=mystorageaccountkey
67
69
68
70
#Give a name to the destination VHD file to which the VHD will be copied.
This script uses 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 above 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.
80
81
81
82
|Command |Notes |
82
83
|---------|---------|
83
-
| az disk grant-access |Generates read-only SAS that is used to copy the underlying VHD file to a storage account or download it to on-premises|
84
-
| az storage blob copy start |Copies a blob asynchronously from one storage account to another. Use az storage blob show to check the status of the new blob.|
84
+
| az disk grant-access | Generates read-only SAS that is used to copy the underlying VHD file to a storage account or download it to on-premises.|
85
+
| az storage blob copy start | Copies a blob asynchronously from one storage account to another. Use [az storage blob show](/cli/azure/storage/blob#az-storage-blob-show) to check the status of the new blob. |
85
86
86
-
## Generate the SAS address
87
+
## Generate the SAS URI
87
88
88
-
There are two common tools used to create a SAS address (URL):
89
+
There are two common tools used to create a SAS address (URI):
89
90
90
-
1.**Azure Storage Explorer** – Available on the Azure portal.
91
-
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.
92
93
93
-
### Using Tool 1: Azure Storage Explorer
94
+
### Using Tool 1: Azure Storage browser
94
95
95
-
1. Go to your **Storage Account**.
96
-
2. Open **Storage Explorer**.
96
+
1. Go to your **Storage account**.
97
+
2. Open **Storage browser** and select **blob containers**.
98
+
3. In your **Container**, right-click the VHD file and select **Generate SAS**.
99
+
4. In the **Shared Access Signature** menu that appears, complete the following fields:
5. To create the associated SAS URI for this VHD, select **Create**.
111
-
6. Copy the URI and save it to a text file in a secure location. This generated SAS URI is for container-level access. To make it specific, edit the text file to add the VHD name.
112
-
7. Insert your VHD name after the vhds string in the SAS URI (include a forward slash). The final SAS URI should look like this:
8. Repeat these steps for each VHD in the plans you will publish.
101
+
1. Permissions – Select read permissions. Don’t provide write or delete permissions.
102
+
1. Start date/time – This is the permission start date for VHD access. To protect against UTC time changes, provide a date that is one day before the current date. For example, if the current date is July 15, 2022, set the date as 07/14/2022.
103
+
1. Expiry date/time – This is the permission expiration date for VHD access. Provide a date at least three weeks beyond the current date.
104
+
105
+
5. To create the associated SAS URI for this VHD, select **Generate SAS token and URL**.
106
+
6. Copy the Blob SAS URL and save it to a text file in a secure location.
107
+
7. Repeat these steps for each VHD you want to publish.
117
108
118
109
### Using Tool 2: Azure CLI
119
110
120
-
1. Download and install [Microsoft Azure CL](/cli/azure/install-azure-cli)I. Versions are available for Windows, macOS, and various distros of Linux.
121
-
2. Create a PowerShell file (.ps1 file extension), copy in the following code, then save it locally.
5. Using one of the following methods, run this script with administrative privileges to create a SAS connection string for container-level access:
142
-
143
-
- Run the script from the console. In Windows, right-click the script and select **Run as administrator**.
144
-
- Run the script from a PowerShell script editor such as [Windows PowerShell ISE](/powershell/scripting/components/ise/introducing-the-windows-powershell-ise). This screen shows the creation of a SAS connection string within this editor:
145
-
146
-
[](media/vm/create-sas-uri-power-shell-ise.png#lightbox)
147
-
148
-
6. Copy the SAS connection string and save it to a text file in a secure location. Edit this string to add the VHD location information to create the final SAS URI.
149
-
7. In the Azure portal, go to the blob storage that includes the VHD associated with the new URI.
150
-
8. Copy the URL of the blob service endpoint:
117
+
Before running the command above, remember to insert the following parameter values.
151
118
152
-
119
+
| Parameter value | Description |
120
+
| --------------- | ----------- |
121
+
| account-name | Your Azure storage account name. |
122
+
| account-key | Your Azure storage account key. |
123
+
| container-name | Your blob container that hosts the VHD file. |
124
+
| start-date | This is the permission start date for VHD access. Provide a date one day before the current date. For example, if the current date is July 15, 2022, set the date as 07/14/2022. Provide dates in UTC date/time format (YYYY-MM-DDT00:00:00Z), such as 2022-04-01T00:00:00Z. |
125
+
| expiry-date | This is the permission expiration date for VHD access. Provide a date at least three weeks after the current date. Provide dates in UTC date/time format (YYYY-MM-DDT00:00:00Z), such as 2022-04-01T00:00:00Z. |
153
126
154
-
9. Edit the text file with the SAS connection string from step 6. Create the complete SAS URI using this format:
127
+
1. Copy the SAS connection string and save it to a text file in a secure location. Edit this string to add the VHD location information to create the final SAS URI.
128
+
1. In the Azure portal, go to the blob container that includes the VHD associated with the new URI.
129
+
1. Copy the URL of the blob service endpoint.
130
+
1. Edit the text file with the SAS connection string from step 2. Create the complete SAS URI using this format. Be sure to insert a “?” between the endpoint URL and the connection string.
Following are common issues encountered when working with shared access signatures (which are used to identify and share the uploaded VHDs for your solution), along with suggested resolutions.
136
+
This table shows the common errors encountered when providing a shared access signatures (SAS) URI in Partner Center, along with suggested resolutions.
161
137
162
138
| Issue | Failure Message | Fix |
163
139
| --- | --- | --- |
164
-
| *Failure in copying images* | | |
165
-
| "?" is not found in SAS URI | `Failure: Copying Images. Not able to download blob using provided SAS Uri.` | Update the SAS URI using recommended tools. |
166
-
| "st" and "se" parameters not in SAS URI | `Failure: Copying Images. Not able to download blob using provided SAS Uri.` | Update the SAS URI with proper **Start Date** and **End Date** values. |
167
-
| "sp=rl" not in SAS URI | `Failure: Copying Images. Not able to download blob using provided SAS Uri.` | Update the SAS URI with permissions set as `Read` and `List`. |
168
-
| SAS URI has white spaces in VHD name | `Failure: Copying Images. Not able to download blob using provided SAS Uri.` | Update the SAS URI to remove white spaces. |
140
+
| "?" 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>` |
141
+
| "st" parameter not in SAS URI | `Specified SAS URL cannot be reached.` | Update the SAS URI with proper **Start Date** ("st") value. |
142
+
| "se" parameter not in SAS URI | `The end date parameter (se) is required.` | Update the SAS URI with proper **End Date** (“se”) value. |
143
+
| "sp=r" not in SAS URI | `Missing Permissions (sp) must include 'read' (r).` | Update the SAS URI with permissions set as `Read` (“sp=r”). |
169
144
| 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. |
170
-
| SAS URI "st" and "se" parameters do not have full date-time specification | `Failure: Copying Images. Not able to download blob due to incorrect SAS Uri.` | SAS URI **Start Date** and **End Date** parameters (`st` and `se` substrings) must have full date-time format, such as `11-02-2017T00:00:00Z`. Shortened versions are invalid (some commands in Azure CLI may generate shortened values by default). |
145
+
| 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). |
171
146
172
147
For details, see [Grant limited access to Azure Storage resources using shared access signatures (SAS)](../storage/common/storage-sas-overview.md).
173
148
@@ -176,12 +151,11 @@ For details, see [Grant limited access to Azure Storage resources using shared a
176
151
Check the SAS URI before publishing it on Partner Center to avoid any issues related to SAS URI post submission of the request. This process is optional but recommended.
177
152
178
153
- The URI includes your VHD image filename, including the filename extension `.vhd`.
179
-
- `Sp=rl` appears near the middle of your URI. This string shows Read and List access is specified.
154
+
- `Sp=r` appears near the middle of your URI. This string shows Read permission is granted.
180
155
- When `sr=c` appears, this means that container-level access is specified.
181
156
- Copy and paste the URI into a browser to test-download the blob (you can cancel the operation before the download completes).
182
157
183
158
## Next steps
184
159
185
-
- If you run into issues, see [VM SAS failure messages](azure-vm-sas-failure-messages.md)
186
-
- [Sign in to Partner Center](https://go.microsoft.com/fwlink/?linkid=2165935)
187
160
- [Create a virtual machine offer on Azure Marketplace](azure-vm-offer-setup.md)
161
+
- [Sign in to Partner Center and publish your image by providing the SAS URI](https://go.microsoft.com/fwlink/?linkid=2165935)
0 commit comments