Skip to content

Commit 9f1a753

Browse files
committed
updates based on feedback.
1 parent 8ad3dd4 commit 9f1a753

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/virtual-desktop/faq.yml

Lines changed: 3 additions & 3 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: 12/05/2022
8+
ms.date: 12/06/2022
99
ms.author: helohr
1010
ms.custom: devx-track-azurepowershell
1111
manager: femila
@@ -193,6 +193,6 @@ sections:
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.
194194
195195
- question: |
196-
What happens when you try to add more than 200 VMs to an availability set?
196+
What happens when you try to add more than 200 VMs to an availability set in Azure Virtual Desktop?
197197
answer: |
198-
If you go over the 200 VM limit, the service won't be able to create a new VM. Instead, 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).
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)