Skip to content

Commit 8f13415

Browse files
committed
add the sku restriction
1 parent b25704e commit 8f13415

File tree

1 file changed

+12
-2
lines changed

1 file changed

+12
-2
lines changed

articles/azure-resource-manager/templates/deployment-script-template.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-resource-manager
55
author: mumian
66
ms.service: azure-resource-manager
77
ms.topic: conceptual
8-
ms.date: 04/30/2020
8+
ms.date: 05/06/2020
99
ms.author: jgao
1010

1111
---
@@ -299,7 +299,7 @@ To see the deploymentScripts resource in the portal, select **Show hidden types*
299299

300300
A storage account and a container instance are needed for script execution and troubleshooting. You have the options to specify an existing storage account, otherwise the storage account along with the container instance are automatically created by the script service. The requirements for using an existing storage account:
301301

302-
- Supported storage account kinds are: General-purpose v2 accounts, General-purpose v1 accounts and fileStorage accounts. For more information, see [Types of storage accounts](../../storage/common/storage-account-overview.md).
302+
- Supported storage account kinds are: General-purpose v2/v1 accounts with standard performance tier, and fileStorage accounts with either standard or premium performance tier. For more information, see [Types of storage accounts](../../storage/common/storage-account-overview.md).
303303
- Storage account firewall rules must be turned off. See [Configure Azure Storage firewalls and virtual network](../../storage/common/storage-network-security.md)
304304
- Deployment script's user-assigned managed identity must have permissions to manage the storage account, which includes read, create, delete file shares.
305305

@@ -312,6 +312,16 @@ To specify an existing storage account, add the following json to the property e
312312
},
313313
```
314314

315+
- **storageAccountName**: specify the name of the storage account.
316+
- **storageAccountKey"**: specify one of the storage account keys. You can use the [`listKeys()`](./template-functions-resource.md#listkeys) function to retrieve the key. For example:
317+
318+
```json
319+
"storageAccountSettings": {
320+
"storageAccountName": "[variables('storageAccountName')]",
321+
"storageAccountKey": "[listKeys(resourceId('Microsoft.Storage/storageAccounts', variables('storageAccountName')), '2019-06-01').keys[0].value]"
322+
}
323+
```
324+
315325
See [Sample templates](#sample-templates) for a complete `Microsoft.Resources/deploymentScripts` definition sample.
316326

317327
When an existing storage account is used, the script service creates a file share with a unique name. See [Clean up deployment script resources](#clean-up-deployment-script-resources) for how the script service cleans up the file share.

0 commit comments

Comments
 (0)