Skip to content

Commit dfd9dc1

Browse files
Merge pull request #220292 from Heidilohr/work-availability-sets
Adding new question to FAQ.
2 parents d75437f + 9f1a753 commit dfd9dc1

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/virtual-desktop/faq.yml

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ metadata:
55
author: Heidilohr
66
ms.topic: faq
77
ms.service: virtual-desktop
8-
ms.date: 11/07/2022
8+
ms.date: 12/06/2022
99
ms.author: helohr
1010
ms.custom: devx-track-azurepowershell
1111
manager: femila
@@ -191,7 +191,8 @@ sections:
191191
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?
192192
answer: |
193193
If the region you stored your host pool metadata in goes down, Azure Virtual Desktop won't accept new user connections to the session host VMs in that host pool. However, any existing sessions on the session host VMs in that host pool will remain connected and unaffected.
194-
195-
196194
197-
195+
- question: |
196+
What happens when you try to add more than 200 VMs to an availability set in Azure Virtual Desktop?
197+
answer: |
198+
If you try to go over 200 VMs in an availability set in Azure Virtual Desktop, you'll receive an error message that says "Can't create VM because the limit of 200 VMs has already been reached." For more information, see the [Availability sets overview](../virtual-machines/availability-set-overview.md).

0 commit comments

Comments
 (0)