Skip to content

Commit 00206a5

Browse files
Merge pull request #218803 from mumian/1117-spec-roles
1117 spec roles
2 parents 102f12d + 5a5aca3 commit 00206a5

File tree

2 files changed

+18
-6
lines changed

2 files changed

+18
-6
lines changed

articles/azure-resource-manager/bicep/template-specs.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create & deploy template specs in Bicep
33
description: Describes how to create template specs in Bicep and share them with other users in your organization.
44
ms.topic: conceptual
55
ms.custom: ignite-2022
6-
ms.date: 11/10/2022
6+
ms.date: 11/17/2022
77
---
88

99
# Azure Resource Manager template specs in Bicep
@@ -32,9 +32,12 @@ To learn more about template specs, and for hands-on guidance, see [Publish libr
3232

3333
## Required permissions
3434

35-
To create a template spec, you need **write** access to `Microsoft.Resources/templateSpecs` and `Microsoft.Resources/templateSpecs/versions`.
35+
There are two Azure build-in roles defined for template spec:
3636

37-
To deploy a template spec, you need **read** access to `Microsoft.Resources/templateSpecs` and `Microsoft.Resources/templateSpecs/versions`. In addition, you also need the permissions for deploying a Bicep file. See [Deploy - CLI](./deploy-cli.md#required-permissions) or [Deploy - PowerShell](./deploy-powershell.md#required-permissions).
37+
- [Template Spec Reader](../../role-based-access-control//built-in-roles.md#template-spec-reader)
38+
- [Template Spec Contributor](../../role-based-access-control//built-in-roles.md#template-spec-contributor)
39+
40+
In addition, you also need the permissions for deploying a Bicep file. See [Deploy - CLI](./deploy-cli.md#required-permissions) or [Deploy - PowerShell](./deploy-powershell.md#required-permissions).
3841

3942
## Why use template specs?
4043

@@ -200,7 +203,7 @@ az ts show \
200203

201204
## Deploy template spec
202205

203-
After you've created the template spec, users with **read** access to the template spec can deploy it. For information about granting access, see [Tutorial: Grant a group access to Azure resources using Azure PowerShell](../../role-based-access-control/tutorial-role-assignments-group-powershell.md).
206+
After you've created the template spec, users with the [Template Specs Reader](#required-permissions) role can deploy it. In addition, you also need the permissions for deploying an ARM template. See [Deploy - CLI](./deploy-cli.md#required-permissions) or [Deploy - PowerShell](./deploy-powershell.md#required-permissions).
204207

205208
Template specs can be deployed through the portal, PowerShell, Azure CLI, or as a Bicep module in a larger template deployment. Users in an organization can deploy a template spec to any scope in Azure (resource group, subscription, management group, or tenant).
206209

articles/azure-resource-manager/templates/template-specs.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Create & deploy template specs
33
description: Describes how to create template specs and share them with other users in your organization.
44
ms.topic: conceptual
5-
ms.date: 11/10/2022
5+
ms.date: 11/17/2022
66
ms.custom: devx-track-azurepowershell, devx-track-azurecli, ignite-2022
77
---
88

@@ -41,6 +41,15 @@ If you currently have your templates in a GitHub repo or storage account, you ru
4141

4242
The templates you include in a template spec should be verified by administrators in your organization to follow the organization's requirements and guidance.
4343

44+
## Required permissions
45+
46+
There are two Azure build-in roles defined for template spec:
47+
48+
- [Template Spec Reader](../../role-based-access-control//built-in-roles.md#template-spec-reader)
49+
- [Template Spec Contributor](../../role-based-access-control//built-in-roles.md#template-spec-contributor)
50+
51+
In addition, you also need the permissions for deploying a Bicep file. See [Deploy - CLI](./deploy-cli.md#required-permissions) or [Deploy - PowerShell](./deploy-powershell.md#required-permissions).
52+
4453
## Create template spec
4554

4655
The following example shows a simple template for creating a storage account in Azure.
@@ -216,7 +225,7 @@ az ts show \
216225

217226
## Deploy template spec
218227

219-
After you've created the template spec, users with **read** access to the template spec can deploy it. For information about granting access, see [Tutorial: Grant a group access to Azure resources using Azure PowerShell](../../role-based-access-control/tutorial-role-assignments-group-powershell.md). In addition, you also need the permissions for deploying an ARM template. See [Deploy - CLI](./deploy-cli.md#required-permissions) or [Deploy - PowerShell](./deploy-powershell.md#required-permissions).
228+
After you've created the template spec, users with the [template spec reader](#required-permissions) role can deploy it. In addition, you also need the permissions for deploying an ARM template. See [Deploy - CLI](./deploy-cli.md#required-permissions) or [Deploy - PowerShell](./deploy-powershell.md#required-permissions).
220229

221230
Template specs can be deployed through the portal, PowerShell, Azure CLI, or as a linked template in a larger template deployment. Users in an organization can deploy a template spec to any scope in Azure (resource group, subscription, management group, or tenant).
222231

0 commit comments

Comments
 (0)