Merge pull request #304613 from andreamichaelmsft/andrea-branch-2

Clarify goal state

Author: prmerger-automator[bot]

articles/virtual-network-manager/concept-deployments.md

@@ -43,6 +43,8 @@ When you commit a configuration deployment, the API forms a POST operation. Once
 
 When you commit a deployment of configurations, you describe the goal state of your network manager in the targeted regions. This goal state is enforced during the next deployment. For example, when you commit configurations *Config1* and *Config2* into a region, these two configurations get applied and become the region's goal state. If you decided to commit configurations *Config1* and *Config3* into the same region, *Config2* would then be removed, and *Config3* would be added. To remove all configurations, you would deploy **None** to the regions where you no longer wish to have any configurations applied.
 
+You may have multiple connectivity configurations deployed simultaneously in a given region. The connectivity defined in each configuration is additive. If you modify one configuration, under this goal state model you must still deploy all connectivity configurations you want to take effect in that region. For example, given the *East US* region has *Config1* and *Config2* deployed there, if you modify *Config1*, you must deploy both *Config1* and *Config2* again in *East US* in order for both the changes from *Config1* and the behavior from *Config2* to take effect on the virtual networks in the region.
+
 ## Configuration availability
 
 A network manager is available in a region as long as the region is up and running. Should a region with a network manager go down, the network manager is no longer available to submit new configuration deployments or modify existing configurations. However, the configurations that were deployed to the targeted network groups' virtual networks in the targeted regions are still in effect unless those virtual networks are in the region that went down.