Lock resource ARM template sample should use extension resource scopes

[anthony-c-martin]

We should update our ARM Template docs examples to consistently demonstrate the 'best practice' way to deploy extension resources - using the 'scope' property, rather than munging the 'type' and 'name' fields to generating a resourceId.

See this article for an example: https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/scope-extension-resources?tabs=azure-cli#apply-to-resource

In the example provided in this particular doc, I'd expect something like:

{
  "scope": "[concat('Microsoft.Web/sites', variables('siteName'))]",
  "type": "Microsoft.Authorization/locks",
  "name": "siteLock",
  ...
}

instead of:

{
  "type": "Microsoft.Web/sites/providers/locks",
  "name": "[concat(variables('siteName'), '/Microsoft.Authorization/siteLock')]",
  ...
}

@tfitzmac FYI

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4e7af209-7240-dd2a-7130-e7fb3143986a
• Version Independent ID: a653b0d1-877d-09f7-17fa-11bf06c37cc9
• Content: Lock resources to prevent changes - Azure Resource Manager
• Content Source: articles/azure-resource-manager/management/lock-resources.md
• Service: azure-resource-manager
• Sub-service: management
• GitHub Login: @tfitzmac
• Microsoft Alias: tomfitz

[BharathNimmala-MSFT]

@anthony-c-martin Thanks a lot for bringing this to our attention. I am assigning this issue to our document author @tfitzmac to further review and update the document accordingly.

[tfitzmac]

@anthony-c-martin - thanks for this feedback. I have submitted an update that shows the new scope property. It should get published tomorrow morning.

[tfitzmac]

#please-close