update

Author: mumian

articles/azure-resource-manager/templates/templates-cloud-consistency.md

@@ -444,7 +444,7 @@ In general, avoid hardcoded endpoints in a template. The best practice is to use
 The following reference template function retrieves the endpoint namespace from the storage resource provider:
 
 ```json
-"diskUri":"[concat(reference(resourceId('Microsoft.Storage/storageAccounts/', variables('storageAccountName'))).primaryEndpoints.blob, 'container/myosdisk.vhd')]"
+"diskUri":"[concat(reference(resourceId('Microsoft.Storage/storageAccounts', variables('storageAccountName'))).primaryEndpoints.blob, 'container/myosdisk.vhd')]"
 ```
 
 By replacing the hardcoded value of the storage account endpoint with the `reference` template function, you can use the same template to deploy to different environments successfully without making any changes to the endpoint reference.