Merge pull request #203947 from mbender-ms/avnm-deployment

AVNM - Doc Freshness

Author: v-stsavell

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

@@ -5,7 +5,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: virtual-network-manager
 ms.topic: conceptual
-ms.date: 06/09/2022
+ms.date: 07/06/2022
 ms.custom: template-concept, ignite-fall-2021
 ---
 
@@ -20,21 +20,17 @@ In this article, you'll learn about how configurations are applied to your netwo
 
 ## Deployment
 
-*Deployment* is the method Azure Virtual Network Manager uses to apply configurations to your virtual networks in network groups. Configurations won't take effect until they are deployed. Changes to network groups, including events such as removal and addition of a virtual network into a network group, will take effect without the need of re-deployment. When committing a deployment, you select the region(s) to which the configuration will be applied. When a deployment request is sent to Azure Virtual Network Manager, it will calculate the [goal state](#goalstate) of network resources and request the necessary changes to your infrastructure. The changes can take about 15-20 minutes depending on how large the configuration is.
-
-## <a name="deployment"></a>Deployment against network group membership types
-
-Changing the definition of a network group won't have an impact unless the configuration using this network group is deployed. As such, deployment updates are different for static and dynamic group members in a network group. When you have dynamic group membership defined, such as all virtual networks whose name contains "production", Azure Virtual Network Manager will automatically determine if the dynamic members meet the requirements of the configuration and adjust without you needing to deploy the configuration again. This is because you already defined the condition of the membership, and the definition didn't change. However, if you have virtual networks that are added as static members, you'll need to deploy the configuration again for the changes to apply. For example, if you add a new virtual network as a static member, you'll need to deploy the configuration again to take effect.
+*Deployment* is the method Azure Virtual Network Manager uses to apply configurations to your virtual networks in network groups. Configurations won't take effect until they are deployed. Changes to network groups, including events such as removal and addition of a virtual network into a network group, will take effect without the need for re-deployment. For example, if you have a configuration deployed, and a virtual network is added to a network group, it takes effect immediately. When committing a deployment, you select the region(s) to which the configuration will be applied. When a deployment request is sent to Azure Virtual Network Manager, it will calculate the [goal state](#goalstate) of network resources and request the necessary changes to your infrastructure. The changes can take a few minutes depending on how large the configuration is.
 
 ## Deployment status
 
-When you commit a configuration deployment, the API does a POST operation and you won't see the completion of the deployment afterward. Once the deployment request has been made, Azure Virtual Network Manager will calculate the goal state of your networks and request the underlying infrastructure to make the changes. You can see the deployment status on the *Deployment* page of the Virtual Network Manager.
+When you commit a configuration deployment, the API does a POST operation. Once the deployment request has been made, Azure Virtual Network Manager will calculate the goal state of your networks and request the underlying infrastructure to make the changes. You can see the deployment status on the *Deployment* page of the Virtual Network Manager.
 
 :::image type="content" source="./media/tutorial-create-secured-hub-and-spoke/deployment-in-progress.png" alt-text="Screenshot of deployment in progress in deployment list.":::
 
 ## <a name = "goalstate"></a> Goal state model
 
-When you commit a deployment of configuration(s), you're describing the goal state of the configuration you want as an end result. For example, when you commit configurations named *Config1* and *Config2* into a region, these two configurations gets applied. If you decided to commit configuration named *Config1* and *Config3* into the same region, *Config2* would then be removed and *Config3* would be added. To remove all configurations, you would deploy a **None** configuration against the region(s) you no longer wish to have any configurations applied.
+When you commit a deployment of configuration(s), you're describing the goal state of the configuration you want as an end result in the regions you assigned. For example, when you commit configurations named *Config1* and *Config2* into a region, these two configurations get applied  and become the goal of this region. If you decided to commit configuration named *Config1* and *Config3* into the same region, *Config2* would then be removed and *Config3* would be added. To remove all configurations, you would deploy a **None** configuration against the region(s) you no longer wish to have any configurations applied.
 
 ## Next steps
 

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

@@ -5,7 +5,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: virtual-network-manager
 ms.topic: conceptual
-ms.date: 06/09/2022
+ms.date: 07/06/2022
 ms.custom: template-concept, ignite-fall-2021
 ---
 
@@ -34,7 +34,7 @@ Dynamic membership gives you the flexibility of selecting multiple virtual netwo
 
 When you create a network group, an Azure policy is created so that Azure Virtual Network Manager gets notified about changes made to virtual network membership. The policies defined are available for you to see, but they are not editable by users today. Creating, changing, and deleting Azure policy definitions and assignments for network groups is only possible through the Azure Network Manager today. 
 
-To create an Azure policy initiative definition and assignment for Azure Network Manager resources, create and deploy a network group with the necessary configurations. To update an existing Azure policy initiative definition or corresponding assignment, you'll need to change and deploy changes to the network group within the Azure Virtual Network Manager resource. To delete an Azure policy initiative definition and assignment, you'll need to undeploy and delete the Azure Virtual Network Manager resources associated with your policy. This may include undeploying a configuration, deleting a configuration, and deleting a network group. For more information on deletion, review the Azure Virtual Network Manager [checklist for removing components](concept-remove-components-checklist.md).  
+To create an Azure policy initiative definition and assignment for Azure Network Manager resources, create and deploy a network group with the necessary configurations. To update an existing Azure policy initiative definition or corresponding assignment, you'll need to change and deploy changes to the network group within the Azure Virtual Network Manager resource. To delete an Azure policy initiative definition and assignment, you'll need to undeploy and delete the Azure Virtual Network Manager resources associated with your policy. This may include removing a configuration, deleting a configuration, and deleting a network group. For more information on deletion, review the Azure Virtual Network Manager [checklist for removing components](concept-remove-components-checklist.md).  
 
 ## Next steps
 

articles/virtual-network-manager/overview.md

@@ -5,15 +5,15 @@ services: virtual-network-manager
 author: mbender-ms
 ms.service: virtual-network-manager
 ms.topic: overview
-ms.date: 11/02/2021
+ms.date: 07/06/2022
 ms.author: mbender
 ms.custom: references_regions, ignite-fall-2021
 #Customer intent: As an IT administrator, I want to learn about Azure Virtual Network Manager and what I can use it for.
 ---
 
 # What is Azure Virtual Network Manager (Preview)?
 
-Azure Virtual Network Manager is a management service that enables you to group, configure, deploy, and manage virtual networks globally across subscriptions. With Virtual Network Manager, you can define network groups to identify and logically segment your virtual networks. Then you can determine the connectivity and security configurations you want and apply them across all the selected virtual networks in network groups at once. 
+Azure Virtual Network Manager is a management service that enables you to group, configure, deploy, and manage virtual networks globally across subscriptions. With Virtual Network Manager, you can define network groups to identify and logically segment your virtual networks. Then you can determine the connectivity and security configurations you want and apply them across all the selected virtual networks in network groups at once.
 
 > [!IMPORTANT]
 > Azure Virtual Network Manager is currently in public preview.
@@ -38,7 +38,7 @@ A connectivity configuration enables you to create a mesh or a hub-and-spoke net
 
 * Highly scalable and highly available service with redundancy and replication across the globe.
 
-* Ability to create global network security rules that override network security group rules.
+* Ability to create network security rules that override network security group rules.
 
 * Low latency and high bandwidth between resources in different virtual networks using virtual network peering.