[RecoveryServices.backup] changing number of VMs from 100 to 1000 (Azure#12816)

* changing number of VMs from 100 to 1000

* adding description inside changelog.md

Author: hiaga

src/RecoveryServices/RecoveryServices.Backup.Models/Properties/Resources.resx

@@ -572,7 +572,7 @@ Please contact Microsoft for further assistance.</value>
     <value>RetentionDuration in Days should be from 7 - 9999</value>
   </data>
   <data name="ProtectedItemsCountExceededException" xml:space="preserve">
-    <value>Cannot configure backup for more than 100 VMs per policy</value>
+    <value>Cannot configure backup for more than 1000 VMs per policy</value>
   </data>
   <data name="SoftdeleteNotImplementedException" xml:space="preserve">
     <value>Undo-deletion is only supported for AzureVMs. This method is not supported for other workloads.</value>

src/RecoveryServices/RecoveryServices.Backup.Providers/Providers/IaasVmPsBackupProvider.cs

@@ -986,7 +986,7 @@ public void RegisterContainer()
 
         private void ValidateProtectedItemCount(AzureVmPolicy azureVmPolicy)
         {
-            if (azureVmPolicy.ProtectedItemsCount > 100)
+            if (azureVmPolicy.ProtectedItemsCount > 1000)
             {
                 throw new ArgumentException(Resources.ProtectedItemsCountExceededException);
             }

src/RecoveryServices/RecoveryServices/ChangeLog.md

@@ -20,6 +20,7 @@
 ## Upcoming Release
 * Azure Backup added a new cmdlet Copy-AzRecoveryServicesVault for DS move feature.
 * Get-AzRecoveryServicesBackupJob cmdlet now supports operation type 'BackupDataMove'.
+* Modifying the configure backup per policy limit for VMs from 100 to 1000.
 
 ## Version 2.11.1
 * Improved the Azure Backup container/item discovery experience.