Skip to content

Commit be0e33b

Browse files
committed
Minor updates for writing style
1 parent c64d561 commit be0e33b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-desktop/faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -188,7 +188,7 @@ sections:
188188
- question: |
189189
If I store my host pools and VMs in different regions, what would happen in a disaster scenario where the host pool region goes down but the VM region stays online?
190190
answer: |
191-
Metadata for a host pool is replicated within a geography for resiliency, therefore if the region you stored your host pool metadata in goes down there will be a failover to a secondary replica. During this failover period Azure Virtual Desktop won't accept new user connections to the session host VMs in that host pool until the failover has completed. However, any existing sessions on the session host VMs in that host pool will remain connected and unaffected. To learn more on how service resilience is implemented for Azure Virtual Desktop, see [Azure Virtual Desktop service architecture and resilience](../virtual-desktop/service-architecture-resilience.md)
191+
Metadata of a host pool is replicated within a geography for resiliency. If the region your host pool is in goes down, it fails over to its replica. During this failover period, Azure Virtual Desktop doesn't accept new user connections to the session host VMs in that host pool until the failover has completed. Any existing sessions on the session host VMs in that host pool remain connected and unaffected. To learn more about how service resilience is implemented for Azure Virtual Desktop, see [Azure Virtual Desktop service architecture and resilience](../virtual-desktop/service-architecture-resilience.md).
192192
193193
- question: |
194194
What happens when you try to add more than 200 VMs to an availability set in Azure Virtual Desktop?

0 commit comments

Comments
 (0)