AzureRmResourceGroupDeployment for storage account creation : The response for resource had empty or invalid content
See original GitHub issueTemplate file
{ "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#", "contentVersion": "1.0.0.0", "parameters": { "storageAccount_name": { "defaultValue": "stcr2130", "type": "String" } }, "variables": {}, "resources": [ { "type": "Microsoft.Storage/storageAccounts", "apiVersion": "2019-04-01", "name": "[parameters('storageAccount_name')]", "location": "southeastasia", "tags": { "Application": "STACR", "Purpose": "fileprocess", "AIRID": "2139" }, "sku": { "name": "Standard_LRS", "tier": "Standard" }, "kind": "StorageV2", "properties": { "supportsHttpsTrafficOnly": true, "encryption": { "services": { "file": { "enabled": true }, "blob": { "enabled": true } }, "keySource": "Microsoft.Storage" }, "accessTier": "Hot" } }, { "type": "Microsoft.Storage/storageAccounts/blobServices", "apiVersion": "2019-04-01", "name": "[concat(parameters('storageAccount_name'), '/default')]", "dependsOn": [ "[resourceId('Microsoft.Storage/storageAccounts', parameters('storageAccount_name'))]" ], "properties": { "cors": { "corsRules": [] }, "deleteRetentionPolicy": { "enabled": false } } } ] }
Getting below error
New-AzureRmResourceGroupDeployment : 10:01:30 AM - Resource Microsoft.Storage/storageAccounts 'stcr2130' failed with message '{
"error": {
"code": "ResourceDeploymentFailure",
"message": "The response for resource had empty or invalid content."
}
}'
At line:1 char:1
+ New-AzureRmResourceGroupDeployment -ResourceGroupName $resourcegroup ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-AzureRmResourceGroupDeployment], Exception
+ FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzureResourceGroupDeploymentCmdlet
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top GitHub Comments
I was able to fix my template, the subnets in this new subscription needed storage service endpoints added before the acl could be created, maybe this error is just stating some pre-req is required and was not found. Still, I think the error should probably be improved. @Rakesh201180 , since you aren’t using network acls, maybe confirm the storage account provider is added to the subscription. I’m not sure what other pre-reqs there would be for storage.
The storage RP team has confirmed that this has since been fixed - closing.