Merge pull request #102420 from mumian/0127-resourceid

0127 resourceid

Author: PRMerger14

articles/azure-resource-manager/templates/error-not-found.md

@@ -92,5 +92,5 @@ In the reference function, use `Full` to get all of the properties including the
 For example, to get the tenant ID for a managed identity that is applied to a virtual machine scale set, use:
 
 ```json
-"tenantId": "[reference(concat('Microsoft.Compute/virtualMachineScaleSets/',  variables('vmNodeType0Name')), variables('vmssApiVersion'), 'Full').Identity.tenantId]"
+"tenantId": "[reference(resourceId('Microsoft.Compute/virtualMachineScaleSets',  variables('vmNodeType0Name')), variables('vmssApiVersion'), 'Full').Identity.tenantId]"
 ```

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(concat('Microsoft.Storage/storageAccounts/', variables('storageAccountName')), '2015-06-15').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.