Merge remote-tracking branch 'origin/master' into autogenerate

Author: Autogenerator Pipeline

schemas/2014-04-01-preview/deploymentTemplate.json

@@ -2146,6 +2146,10 @@
         "tags": {
           "type": "object",
           "description": "Name-value pairs to add to the resource"
+        },
+        "scope": {
+          "type": "string",
+          "description": "Scope for the resource or deployment. Today, this works for two cases: 1) setting the scope for extension resources 2) deploying resources to the tenant scope in non-tenant scope deployments"
         }
       },
       "required": [

schemas/2015-01-01/deploymentTemplate.json

@@ -2337,6 +2337,10 @@
             "copy": {
               "$ref": "#/definitions/resourceCopy"
             },
+            "scope": {
+              "type": "string",
+              "description": "Scope for the resource or deployment. Today, this works for two cases: 1) setting the scope for extension resources 2) deploying resources to the tenant scope in non-tenant scope deployments"
+            },
             "comments": {
               "type": "string"
             }

schemas/2018-05-01/subscriptionDeploymentTemplate.json

@@ -402,6 +402,10 @@
             "copy": {
               "$ref": "#/definitions/resourceCopy"
             },
+            "scope": {
+              "type": "string",
+              "description": "Scope property to be used to provide scope for a resource or to be used to specify a scope for Management Group or Tenant level deployments."
+            },
             "comments": {
               "type": "string"
             }

schemas/2019-03-01-hybrid/deploymentTemplate.json

@@ -3129,6 +3129,10 @@
             "copy": {
               "$ref": "#/definitions/resourceCopy"
             },
+            "scope": {
+              "type": "string",
+              "description": "Scope for the resource or deployment. Today, this works for two cases: 1) setting the scope for extension resources 2) deploying resources to the tenant scope in non-tenant scope deployments"
+            },
             "comments": {
               "type": "string"
             }

schemas/2019-04-01/deploymentTemplate.json

@@ -1582,6 +1582,10 @@
             "copy": {
               "$ref": "#/definitions/resourceCopy"
             },
+            "scope": {
+              "type": "string",
+              "description": "Scope for the resource or deployment. Today, this works for two cases: 1) setting the scope for extension resources 2) deploying resources to the tenant scope in non-tenant scope deployments"
+            },
             "comments": {
               "type": "string"
             }

schemas/2019-08-01/managementGroupDeploymentTemplate.json

@@ -246,6 +246,10 @@
             "copy": {
               "$ref": "#/definitions/resourceCopy"
             },
+            "scope": {
+              "type": "string",
+              "description": "Scope property to be used to provide scope for a resource or to be used to specify a scope for Management Group or Tenant level deployments."
+            },
             "comments": {
               "type": "string"
             }

schemas/2019-08-01/tenantDeploymentTemplate.json

@@ -366,6 +366,10 @@
             "copy": {
               "$ref": "#/definitions/resourceCopy"
             },
+            "scope": {
+              "type": "string",
+              "description": "Scope property to be used to provide scope for a resource or to be used to specify a scope for Management Group or Tenant level deployments."
+            },
             "comments": {
               "type": "string"
             }