Merge pull request #298 from MicrosoftDocs/main

Merge main to live, 4 AM

articles/virtual-machines/TOC.yml

@@ -514,6 +514,8 @@
           href: ./sizes/gpu-accelerated/nvv4-series.md
         - name: NVadsA10_v5 series
           href: ./sizes/gpu-accelerated/nvadsa10v5-series.md
+        - name: Nvads V710 v-5 series
+          href: ./sizes/gpu-accelerated/nvadsv710-v5-series.md
       - name: Setup NVIDIA GPU drivers
         items:
         - name: Linux

articles/virtual-machines/maintenance-configurations.md

@@ -109,8 +109,8 @@ We recommend the following limits for indicators:
 | Total number of resource associations to a schedule | 3,000 |
 | Resource associations on each dynamic scope    | 1,000 |
 | Number of dynamic scopes per resource group or subscription per region     | 250  |
-| Number of dynamic scopes per schedule   | 30  |
-| Total number of subscriptions attached to all dynamic scopes per schedule   | 30  |
+| Number of dynamic scopes per schedule   | 200  |
+| Total number of subscriptions attached to all dynamic scopes per schedule   | 200  |
 
 We recommend the following limits for each dynamic scope in the guest scope only:
 

articles/virtual-machines/troubleshoot-maintenance-configurations.md

@@ -13,18 +13,6 @@ ms.author: lnagpal
 
 This article outlines common problems and errors that might arise during the deployment or use of Maintenance Configurations for scheduled patching on virtual machines (VMs), along with strategies to address them.
 
-### A VM shuts down and is unresponsive when you use a dynamic scope in guest maintenance
-
-#### Problem
-
-A maintenance configuration doesn't install a scheduled patch on the VMs and gives a `ShutdownOrUnresponsive` error.
-
-#### Resolution
-
-It takes 12 hours to complete the cleanup process for the maintenance configuration assignment. Be sure to keep a buffer of 12 hours before you create a VM with the same name.
-
-If you create a VM with the same name before the cleanup, Maintenance Configurations can't trigger the schedule.
-
 ### A VM shuts down and is unresponsive when you use a static scope in guest maintenance
 
 #### Problem
@@ -96,6 +84,8 @@ After creating a Maintenance Configuration with a repeat value of either week or
 
 The Maintenance Configuration first run occurs on the first recurrence value following the specified start date, not necessarily on the start date itself. For example, if the maintenance configuration starts on January 17th (Wednesday) and is set to recur every Monday, the first run of the schedule will be on the first Monday after January 17th, which is January 22nd.
 
+You can view first 4 instances of the scheduled run when creating a new maintenance configuration from Azure Portal.
+
 ### Creation of a dynamic scope fails
 
 #### Problem
@@ -135,18 +125,6 @@ A maintenance configuration doesn't block the update of a dedicated host, and th
 
 If you re-create a dedicated host with the same name, Maintenance Configurations retains the old dedicated host ID, which prevents it from blocking updates. You can resolve this problem by removing the maintenance configuration and reassigning it. If the problem persists, contact the support team for assistance.
 
-### Patch installation fails for an invalid classification type
-
-#### Problem
-
-Patch installation fails because of an invalid classification type in a maintenance configuration.
-
-A previous bug prevented the system's patch operation from performing validation, and the maintenance configuration contained an invalid classification type.
-
-#### Resolution
-
-The bug is fixed. Update the maintenance configuration and set the correct classification type.
-
 ### A schedule isn't triggered
 
 #### Problem
@@ -175,7 +153,7 @@ Dynamic scope flattening fails because of throttling, and the service can't dete
 
 #### Resolution
 
-Make sure that the number of subscriptions per dynamic scope is less than 30. [Learn more about the service limits of dynamic scoping](../virtual-machines/maintenance-configurations.md#service-limits).
+Make sure that the number of subscriptions per dynamic scope is not more than 200. [Learn more about the service limits of dynamic scoping](../virtual-machines/maintenance-configurations.md#service-limits).
 
 ### Configuration assignment of a dedicated host isn't cleaned up after the host's removal