Merge pull request #114116 from mumian/0506-ds-store

add the sku restriction

Author: PRMerger20

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

@@ -5,7 +5,7 @@ services: azure-resource-manager
 author: mumian
 ms.service: azure-resource-manager
 ms.topic: conceptual
-ms.date: 04/30/2020
+ms.date: 05/06/2020
 ms.author: jgao
 
 ---
@@ -299,8 +299,8 @@ To see the deploymentScripts resource in the portal, select **Show hidden types*
 
 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:
 
-- 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).
-- Storage account firewall rules must be turned off. See [Configure Azure Storage firewalls and virtual network](../../storage/common/storage-network-security.md)
+- Supported storage account kinds are: general-purpose v2, general-purpose v1 and FileStorage accounts. Only FileStorage supports premium SKU. For more information, see [Types of storage accounts](../../storage/common/storage-account-overview.md).
+- Storage account firewall rules are not supported yet. For more information, see [Configure Azure Storage firewalls and virtual networks](../../storage/common/storage-network-security.md).
 - Deployment script's user-assigned managed identity must have permissions to manage the storage account, which includes read, create, delete file shares.
 
 To specify an existing storage account, add the following json to the property element of `Microsoft.Resources/deploymentScripts`:
@@ -312,6 +312,16 @@ To specify an existing storage account, add the following json to the property e
 },
 ```
 
+- **storageAccountName**: specify the name of the storage account.
+- **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:
+
+    ```json
+    "storageAccountSettings": {
+        "storageAccountName": "[variables('storageAccountName')]",
+        "storageAccountKey": "[listKeys(resourceId('Microsoft.Storage/storageAccounts', variables('storageAccountName')), '2019-06-01').keys[0].value]"
+    }
+    ```
+
 See [Sample templates](#sample-templates) for a complete `Microsoft.Resources/deploymentScripts` definition sample.
 
 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.
@@ -331,7 +341,7 @@ The life cycle of these resources is controlled by the following properties in t
 - **retentionInterval**: Specify the time interval that a script resource will be retained and after which will be expired and deleted.
 
 > [!NOTE]
-> It is not recommended to use the deployment script resources for other purposes.
+> It is not recommended to use the storage account and the container instance that are generated by the script service for other purposes. The two resources might be removed depending on the script life cycle.
 
 ## Run script more than once