Update articles/cosmos-db/role-based-access-control.md

kanshiG · SnehaGunda · web-flow · commit 6585b3753713 · 2020-04-29T12:55:23.000-07:00
Co-Authored-By: Sneha Gunda &lt;sngun@microsoft.com&gt;
diff --git a/articles/cosmos-db/role-based-access-control.md b/articles/cosmos-db/role-based-access-control.md
@@ -57,7 +57,7 @@ The Cosmos resource provider can be locked down to prevent any changes to resour
     }
 }
 ```
-Simple way to update this seeting is to use Azure CLI. If you are doing an ARM deployment. Those are complete replacements, so if all  values are not included, they will be reset to default. 
+If you export an existing Resource Manager template and update it with this property, it can completely replace the functionality of your template. So if all values are not included, they will be reset to default. Another way to disable the key-based metadata write access is by using Azure CLI as shown in the following command:
 
 ```cli
 az cosmosdb update  --name CosmosDBAccountName --resource-group ResourceGroupName  --disable-key-based-metadata-write-access true

Original file line number	Diff line number	Diff line change
`@@ -57,7 +57,7 @@ The Cosmos resource provider can be locked down to prevent any changes to resour`
`57`	`57`	`}`
`58`	`58`	`}`
`59`	`59`	```
`60`		`-Simple way to update this seeting is to use Azure CLI. If you are doing an ARM deployment. Those are complete replacements, so if all values are not included, they will be reset to default.`
	`60`	`+If you export an existing Resource Manager template and update it with this property, it can completely replace the functionality of your template. So if all values are not included, they will be reset to default. Another way to disable the key-based metadata write access is by using Azure CLI as shown in the following command:`
`61`	`61`
`62`	`62`	```cli
`63`	`63`	`az cosmosdb update --name CosmosDBAccountName --resource-group ResourceGroupName --disable-key-based-metadata-write-access true`