Merge pull request #267360 from gabesmsft/patch-3

Update deploy.md

Author: prmerger-automator[bot]

articles/azure-functions/start-stop-vms/deploy.md

@@ -12,7 +12,7 @@ ms.custon: subject-rbac-steps
 
 Perform the steps in this article in sequence to install the Start/Stop VMs v2 feature. After completing the setup process, configure the schedules to customize it to your requirements.
 
-## Permissions considerations
+## Permissions and Policy considerations
 
 Keep the following considerations in mind before and during deployment:
 
@@ -22,6 +22,9 @@ Keep the following considerations in mind before and during deployment:
 
 + When managing a Start/Stop v2 solution, you should consider the permissions of users to the Start/Stop v2 solution, particularly when whey don't have permission to directly modify the target virtual machines.
 
++ When you deploy the Start/Stop v2 solution to a new or existing resource group, a tag named **SolutionName** with a value of **StartStopV2** is added to resource group and to its resources that are deployed by Start/Stop v2. Any other tags on these resources are removed. If you have an Azure policy that denies management operations based on resource tags, you must allow management operations for resources that contain only this tag.
+
+
 ## Deploy feature
 
 The deployment is initiated from the [Start/Stop VMs v2 GitHub organization](https://github.com/microsoft/startstopv2-deployments/blob/main/README.md). While this feature is intended to manage all of your VMs in your subscription across all resource groups from a single deployment within the subscription, you can install another instance of it based on the operations model or requirements of your organization. It also can be configured to centrally manage VMs across multiple subscriptions.