Merge pull request #264677 from mbender-ms/avnm-ado205650

virtual network manager - Update for BCDR clarification

Author: prmerger-automator[bot]

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

@@ -38,14 +38,20 @@ Virtual network manager applies the configuration to the virtual networks in the
 
 ## Deployment status
 
-When you commit a configuration deployment, the API does a POST operation. Once the deployment request has been made, Azure Virtual Network Manager calculates the goal state of your networks in the deployed regions 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 is made, Azure Virtual Network Manager calculates the goal state of your networks in the deployed regions 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 your network manager in that region. This goal state is enforced during the next deployment. For example, when you commit configurations named *Config1* and *Config2* into a region, these two configurations get applied and become the region's goal state. 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.
 
+## Configuration availability
+
+A virtual network manager instance is available in a region as long as the region is up and running. Should a region with a virtual network manager go down, the virtual network manager instance is no longer available for deploying new configurations or editing current configurations. However, the configurations that were deployed to the virtual networks in the network group are still in effect unless those virtual networks are in the region that went down.
+
+For example, if an Azure Virtual Network Manager instance is created in region A and programs the VNets in region B, the configurations are still in effect even if region A goes down. However, if region B goes down, the configurations are no longer in effect. Also, you can't create new configurations or edit current configurations for virtual networks in region B.
+
 ## Next steps
 
 - Learn how to [create an Azure Virtual Network Manager instance](create-virtual-network-manager-portal.md) in the Azure portal.

articles/virtual-network-manager/faq.md

@@ -5,7 +5,7 @@ services: virtual-network-manager
 author: mbender-ms
 ms.service: virtual-network-manager
 ms.topic: article
-ms.date: 11/07/2023
+ms.date: 01/30/2024
 ms.author: mbender
 ms.custom:
   - references_regions
@@ -89,7 +89,7 @@ You can view Azure Virtual Network Manager settings under **Network Manager** fo
 
 ### What happens when all zones are down in a region with a virtual network manager instance?
 
-Should a regional outage occur, all configurations applied to current resources managed persist, and you can't modify existing configurations, or create new configuration.
+Should a regional outage occur, all configurations applied to current managed virtual network resources will remain intact during the outage. You can't create new configurations or modify existing configurations during the outage. Once the outage is resolved, you can continue to manage your virtual network resources as before.
 
 ### Can a virtual network managed by Azure Virtual Network Manager be peered to a non-managed virtual network?