Skip to content

Commit 74406f1

Browse files
authored
Merge pull request #114289 from mumian/0507-security-center
add workspacesettings
2 parents e9b71fe + a19dd2f commit 74406f1

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

articles/azure-resource-manager/templates/deploy-to-subscription.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Deploy resources to subscription
33
description: Describes how to create a resource group in an Azure Resource Manager template. It also shows how to deploy resources at the Azure subscription scope.
44
ms.topic: conceptual
5-
ms.date: 04/30/2020
5+
ms.date: 05/07/2020
66
---
77

88
# Create resource groups and resources at the subscription level
@@ -30,6 +30,7 @@ You can deploy the following resource types at the subscription level:
3030
* [scopeAssignments](/azure/templates/microsoft.managednetwork/scopeassignments)
3131
* [supportPlanTypes](/azure/templates/microsoft.addons/supportproviders/supportplantypes)
3232
* [tags](/azure/templates/microsoft.resources/tags)
33+
* [workspacesettings](/azure/templates/microsoft.security/workspacesettings)
3334

3435
### Schema
3536

@@ -91,11 +92,11 @@ For subscription-level deployments, there are some important considerations when
9192
* Use the [subscriptionResourceId()](template-functions-resource.md#subscriptionresourceid) function to get the resource ID for resources that are deployed at subscription level.
9293

9394
For example, to get the resource ID for a policy definition, use:
94-
95+
9596
```json
9697
subscriptionResourceId('Microsoft.Authorization/roleDefinitions/', parameters('roleDefinition'))
9798
```
98-
99+
99100
The returned resource ID has the following format:
100101

101102
```json

0 commit comments

Comments
 (0)