Skip to content

Commit 9ec27cb

Browse files
Merge pull request #217964 from mumian/1110-template-specs-permissions
Add additional information for template specs deployment permissions
2 parents d06cfd3 + bb72283 commit 9ec27cb

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

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

Lines changed: 2 additions & 2 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: 08/23/2022
6+
ms.date: 11/10/2022
77
---
88

99
# Azure Resource Manager template specs in Bicep
@@ -34,7 +34,7 @@ To learn more about template specs, and for hands-on guidance, see [Publish libr
3434

3535
To create a template spec, you need **write** access to `Microsoft.Resources/templateSpecs` and `Microsoft.Resources/templateSpecs/versions`.
3636

37-
To deploy a template spec, you need **read** access to `Microsoft.Resources/templateSpecs` and `Microsoft.Resources/templateSpecs/versions`. You also need **write** access to any resources deployed by the template spec, and access to `Microsoft.Resources/deployments/*`.
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).
3838

3939
## Why use template specs?
4040

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

Lines changed: 2 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: 01/12/2022
5+
ms.date: 11/10/2022
66
ms.custom: devx-track-azurepowershell, devx-track-azurecli, ignite-2022
77
---
88

@@ -216,7 +216,7 @@ az ts show \
216216

217217
## Deploy template spec
218218

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).
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).
220220

221221
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).
222222

0 commit comments

Comments
 (0)