Skip to content

Commit e1cb5fd

Browse files
authored
Merge pull request #218605 from davidsmatlak/ds-fix-links-1116
Fixes broken links to API versions
2 parents b1e79bd + 1131be1 commit e1cb5fd

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

articles/azure-resource-manager/bicep/scenarios-rbac.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ The following example shows how to create a user-assigned managed identity and a
7070

7171
When you delete a user, group, service principal, or managed identity from Azure AD, it's a good practice to delete any role assignments. They aren't deleted automatically.
7272

73-
Any role assignments that refer to a deleted principal ID become invalid. If you try to reuse a role assignment's name for another role assignment, the deployment will fail. To work around this behavior, you should either remove the old role assignment before you recreate it, or ensure that you use a unique name when you deploy a new role assignment. [This quickstart template illustrates how you can define a role assignment in a Bicep module and use a principal ID as a seed value for the role assignment name.](https://azure.microsoft.com/resources/templates/key-vault-managed-identity-role-assignment/)
73+
Any role assignments that refer to a deleted principal ID become invalid. If you try to reuse a role assignment's name for another role assignment, the deployment will fail. To work around this behavior, you should either remove the old role assignment before you recreate it, or ensure that you use a unique name when you deploy a new role assignment. This [quickstart template](/samples/azure/azure-quickstart-templates/key-vault-managed-identity-role-assignment) illustrates how you can define a role assignment in a Bicep module and use a principal ID as a seed value for the role assignment name.
7474

7575
## Custom role definitions
7676

@@ -99,6 +99,6 @@ Role definition resource names must be unique within the Azure Active Directory
9999
- [Assign a role at subscription scope](https://azure.microsoft.com/resources/templates/subscription-role-assignment/)
100100
- [Assign a role at tenant scope](https://azure.microsoft.com/resources/templates/tenant-role-assignment/)
101101
- [Create a resourceGroup, apply a lock and RBAC](https://azure.microsoft.com/resources/templates/create-rg-lock-role-assignment/)
102-
- [Create key vault, managed identity, and role assignment](https://azure.microsoft.com/resources/templates/key-vault-managed-identity-role-assignment/)
102+
- [Create key vault, managed identity, and role assignment](/samples/azure/azure-quickstart-templates/key-vault-managed-identity-role-assignment)
103103
- Community blog posts
104104
- [Create role assignments for different scopes with Bicep](https://4bes.nl/2022/04/24/create-role-assignments-for-different-scopes-with-bicep/), by Barbara Forbes

articles/azure-resource-manager/templates/resource-extensions.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,11 @@ Azure Resource Manager template (ARM template) extensions are small applications
1515

1616
The existing extensions are:
1717

18-
- [Microsoft.Compute/virtualMachines/extensions](/azure/templates/microsoft.compute/2018-10-01/virtualmachines/extensions)
19-
- [Microsoft.Compute virtualMachineScaleSets/extensions](/azure/templates/microsoft.compute/2018-10-01/virtualmachinescalesets/extensions)
20-
- [Microsoft.HDInsight clusters/extensions](/azure/templates/microsoft.hdinsight/2018-06-01-preview/clusters)
21-
- [Microsoft.Sql servers/databases/extensions](/azure/templates/microsoft.sql/2014-04-01/servers/databases/extensions)
22-
- [Microsoft.Web/sites/siteextensions](/azure/templates/microsoft.web/2016-08-01/sites/siteextensions)
18+
- [Microsoft.Compute/virtualMachines/extensions](/azure/templates/microsoft.compute/virtualmachines/extensions)
19+
- [Microsoft.Compute virtualMachineScaleSets/extensions](/azure/templates/microsoft.compute/virtualmachinescalesets/extensions)
20+
- [Microsoft.HDInsight clusters/extensions](/azure/templates/microsoft.hdinsight/clusters)
21+
- [Microsoft.Sql servers/databases/extensions](/azure/templates/microsoft.sql/servers/databases/extensions)
22+
- [Microsoft.Web/sites/siteextensions](/azure/templates/microsoft.web/sites/siteextensions)
2323

2424
To find out the available extensions, browse to the [template reference](/azure/templates/). In **Filter by title**, enter **extension**.
2525

articles/azure-resource-manager/templates/template-tutorial-add-resource.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,9 +45,9 @@ Most resources also have a `location` property, which sets the region where you
4545

4646
The other properties vary by resource type and API version. It's important to understand the connection between the API version and the available properties, so let's jump into more detail.
4747

48-
In this tutorial, you add a storage account to the template. You can see the storage account's API version at [storageAccounts 2021-04-01](/azure/templates/microsoft.storage/2021-04-01/storageaccounts). Notice that you don't add all the properties to your template. Many of the properties are optional. The `Microsoft.Storage` resource provider could release a new API version, but the version you're deploying doesn't have to change. You can continue using that version and know that the results of your deployment are consistent.
48+
In this tutorial, you add a storage account to the template. You can see the storage account's API version at [storageAccounts 2021-09-01](/azure/templates/microsoft.storage/2021-09-01/storageaccounts). Notice that you don't add all the properties to your template. Many of the properties are optional. The `Microsoft.Storage` resource provider could release a new API version, but the version you're deploying doesn't have to change. You can continue using that version and know that the results of your deployment are consistent.
4949

50-
If you view an older API version, such as [storageAccounts 2016-05-01](/azure/templates/microsoft.storage/2016-05-01/storageaccounts), you see that a smaller set of properties is available.
50+
If you view an older [API version](/azure/templates/microsoft.storage/allversions) you might see that a smaller set of properties is available.
5151

5252
If you decide to change the API version for a resource, make sure you evaluate the properties for that version and adjust your template appropriately.
5353

0 commit comments

Comments
 (0)