Merge pull request #251267 from SnehaSudhirG/13June-AUMFastFollow1

PMEds28 · web-flow · commit 448133c35873 · 2023-09-20T10:36:37.000+01:00
Removed preview for Dynamic scope and customer managed schedules
diff --git a/articles/update-center/dynamic-scope-overview.md b/articles/update-center/dynamic-scope-overview.md
@@ -41,7 +41,7 @@ For Dynamic Scoping and configuration assignment, ensure that you have the follo
 
 ## Service limits
 
-The following are the Dynamic scope (preview) limits for **each dynamic scope**.
+The following are the Dynamic scope limits for **each dynamic scope**.
 
 | Resource    | Limit          |
 |----------|----------------------------|
@@ -50,7 +50,7 @@ The following are the Dynamic scope (preview) limits for **each dynamic scope**.
 | Number of Resource Group filters    | 50 |
 
 > [!NOTE]
-> The above limits are for Dynamic scope (preview) in the Guest scope only.
+> The above limits are for Dynamic scope in the Guest scope only.
 
 ## Next steps
 
diff --git a/articles/update-center/guidance-migration-automation-update-management-azure-update-manager.md b/articles/update-center/guidance-migration-automation-update-management-azure-update-manager.md
@@ -33,11 +33,11 @@ Guidance to move various capabilities is provided in table below:
 1 | Patch management for Off-Azure machines. | Could run with or without Arc connectivity. | Azure Arc is a prerequisite for non-Azure machines. | 1. [Create service principal](../app-service/quickstart-php.md#1---get-the-sample-repository) </br> 2. [Generate installation script](../azure-arc/servers/onboard-service-principal.md#generate-the-installation-script-from-the-azure-portal) </br> 3. [Install agent and connect to Azure](../azure-arc/servers/onboard-service-principal.md#install-the-agent-and-connect-to-azure) | 1. [Create service principal](../azure-arc/servers/onboard-service-principal.md#azure-powershell) <br> 2. [Generate installation script](../azure-arc/servers/onboard-service-principal.md#generate-the-installation-script-from-the-azure-portal) </br> 3. [Install agent and connect to Azure](../azure-arc/servers/onboard-service-principal.md#install-the-agent-and-connect-to-azure) |
 2 | Enable periodic assessment to check for latest updates automatically every few hours. | Machines automatically receive the latest updates every 12 hours for Windows and every 3 hours for Linux. | Periodic assessment is an update setting on your machine. If it's turned on, the Update Manager fetches updates every 24 hours for the machine and shows the latest update status. | 1. [Single machine](manage-update-settings.md#configure-settings-on-a-single-vm) </br> 2. [At scale](manage-update-settings.md#configure-settings-at-scale) </br> 3. [At scale using policy](periodic-assessment-at-scale.md) | 1. [For Azure VM](../virtual-machines/automatic-vm-guest-patching.md#azure-powershell-when-updating-a-windows-vm) </br> 2.[For Arc-enabled VM](/powershell/module/az.connectedmachine/update-azconnectedmachine?view=azps-10.2.0) |
 3 | Static Update deployment schedules (Static list of machines for update deployment). | Automation Update management had its own schedules. | Azure Update Manager creates a [maintenance configuration](../virtual-machines/maintenance-configurations.md) object for a schedule. So, you need to create this object, copying all schedule settings from Automation Update Management to Azure Update Manager schedule. | 1. [Single VM](scheduled-patching.md#schedule-recurring-updates-on-single-vm) </br> 2. [At scale](scheduled-patching.md#schedule-recurring-updates-at-scale) </br> 3. [At scale using policy](scheduled-patching.md#onboarding-to-schedule-using-policy) | [Create a static scope](manage-vms-programmatically.md) |
-4 | Dynamic Update deployment schedules (Defining scope of machines using resource group, tags, etc. which is evaluated dynamically at runtime).| Same as static update schedules. | Same as static update schedules. | [Add a dynamic scope](manage-dynamic-scoping.md#add-a-dynamic-scope-preview) | [Create a dynamic scope]( tutorial-dynamic-grouping-for-scheduled-patching.md#create-a-dynamic-scope) |
+4 | Dynamic Update deployment schedules (Defining scope of machines using resource group, tags, etc. which is evaluated dynamically at runtime).| Same as static update schedules. | Same as static update schedules. | [Add a dynamic scope](manage-dynamic-scoping.md#add-a-dynamic-scope | [Create a dynamic scope]( tutorial-dynamic-grouping-for-scheduled-patching.md#create-a-dynamic-scope) |
 5 | Deboard from Azure Automation Update management. | After you complete the steps 1, 2, and 3, you need to clean up Azure Update management objects. | | 1. [Remove machines from solution](../automation/update-management/remove-feature.md#remove-management-of-vms) </br> 2. [Remove Update Management solution](../automation/update-management/remove-feature.md#remove-updatemanagement-solution) </br> 3. [Unlink workspace from Automation account](../automation/update-management/remove-feature.md#unlink-workspace-from-automation-account) </br> 4. [Cleanup Automation account](../automation/update-management/remove-feature.md#cleanup-automation-account) | NA |
 6 | Reporting | Custom update reports using Log Analytics queries. | Update data is stored in Azure Resource Graph (ARG). Customers can query ARG data to build custom dashboards, workbooks etc. | The old Automation Update Management data stored in Log analytics can be accessed, but there's no provision to move data to ARG. You can write ARG queries to access data that will be stored to ARG after virtual machines are patched via Azure Update Manager. With ARG queries you can, build dashboards and workbooks using following instructions: </br> 1. [Log structure of Azure Resource graph updates data](query-logs.md) </br> 2. [Sample ARG queries](sample-query-logs.md) </br> 3. [Create workbooks](manage-workbooks.md) | NA |
 7 | Customize workflows using pre and post scripts. | Available as Automation runbooks. | We recommend that you use Automation runbooks once they are available. | | |
-8 | Create alerts based on updates data for your environment | Alerts can be set up on updates data stored in Log Analytics. |We recommend that you use alerts once thy are available. | | |
+8 | Create alerts based on updates data for your environment | Alerts can be set up on updates data stored in Log Analytics. |We recommend that you use alerts once they are available. | | |
 
 
  
diff --git a/articles/update-center/includes/dynamic-scope-prerequisites.md b/articles/update-center/includes/dynamic-scope-prerequisites.md
@@ -29,7 +29,7 @@ Register-AzProviderFeature -ProviderNamespace Microsoft.Maintenance -FeatureName
 
 #### [Azure VMs](#tab/avms)
 
-- Patch Orchestration must be set to Customer Managed Schedules (Preview). This sets patch mode to AutomaticByPlatform and the **BypassPlatformSafetyChecksOnUserSchedule** = *True*.
+- Patch Orchestration must be set to Customer Managed Schedules. This sets patch mode to AutomaticByPlatform and the **BypassPlatformSafetyChecksOnUserSchedule** = *True*.
 - Associate a Schedule with the VM.
              
 #### [Arc-enabled VMs](#tab/arcvms)
diff --git a/articles/update-center/index.yml b/articles/update-center/index.yml
@@ -75,7 +75,6 @@ landingContent:
         links:
           - text: Check and install on-demand updates
             url: quickstart-on-demand.md
-
   - title: Dynamic Scoping
     linkLists:     
       - linkListType: concept
@@ -84,9 +83,9 @@ landingContent:
             url: dynamic-scope-overview.md
       - linkListType: tutorial
         links:
-          - text: Schedule updates on Dynamic scopes (preview)
+          - text: Schedule updates on Dynamic scopes 
             url: tutorial-dynamic-grouping-for-scheduled-patching.md
       - linkListType: how-to-guide
         links:
-          - text: Manage dynamic scope (preview) operations
+          - text: Manage dynamic scope operations
             url: manage-dynamic-scoping.md      
diff --git a/articles/update-center/manage-dynamic-scoping.md b/articles/update-center/manage-dynamic-scoping.md
@@ -12,11 +12,11 @@ ms.topic: how-to
 
 **Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: On-premises environment :heavy_check_mark: Azure Arc-enabled servers.
 
-This article describes how to view, add, edit and delete a dynamic scope (preview).
+This article describes how to view, add, edit and delete a dynamic scope.
 
 [!INCLUDE [dynamic-scope-prerequisites.md](includes/dynamic-scope-prerequisites.md)]
 
-## Add a Dynamic scope (preview)
+## Add a Dynamic scope
 To add a Dynamic scope to an existing configuration, follow these steps:
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to **Azure Update Manager**. 
@@ -29,27 +29,26 @@ To add a Dynamic scope to an existing configuration, follow these steps:
    > [!NOTE]
    > The list of machines may be different at run time.
 1. In the **Configure Azure VMs for schedule updates** page, select any one of the following options to provide your consent:
-    1. **Change the required options to ensure schedule supportability** - this option confirms that you want to update the patch orchestration from existing option to *Customer Managed Schedules (Preview)*: This updates the following two properties on your behalf:
+    1. **Change the required options to ensure schedule supportability** - this option confirms that you want to update the patch orchestration from existing option to *Customer Managed Schedules*: This updates the following two properties on your behalf:
     
        - *Patch mode = AutomaticByPlatform*
        - *Set the BypassPlatformSafetyChecksOnUserSchedule = True*.
-   1. **Continue with supported machines only** - this option confirms that you want to proceed with only the machines that already have patch orchestration set to *Customer Managed Schedules (Preview)*.
+   1. **Continue with supported machines only** - this option confirms that you want to proceed with only the machines that already have patch orchestration set to *Customer Managed Schedules*.
    
     > [!NOTE]
-    > In the **Preview of machines based on above scope** page, you can view only the machines that don't have patch orchestration set to *Customer Managed Schedules (Preview)*.
+    > In the **Preview of machines based on above scope** page, you can view only the machines that don't have patch orchestration set to *Customer Managed Schedules*.
 
 1. Select **Save** to go back to the Dynamic scopes tab. In this tab, you can view and edit the Dynamic scope that you have created.
 
-## View Dynamic scope (preview)
-
-To view the list of Dynamic scopes (preview) associated to a given maintenance configuration, follow these steps:
+## View Dynamic scope
+To view the list of Dynamic scopes associated to a given maintenance configuration, follow these steps:
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to **Azure Update Manager**.
 1. Select **Machines** > **Browse maintenance configurations** > **Maintenance configurations**.
 1. In the **Maintenance configurations** page, select the name of the maintenance configuration for which you want to view the Dynamic scope.
 1. In the given maintenance configuration page, select **Dynamic scopes** to view all the Dynamic scopes that are associated with the maintenance configuration.
 
-## Edit a Dynamic scope (preview)
+## Edit a Dynamic scope
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to **Azure Update Manager**. 
 1. Select **Machines** > **Browse maintenance configurations** > **Maintenance configurations**. 
@@ -60,14 +59,14 @@ To view the list of Dynamic scopes (preview) associated to a given maintenance c
    > Subscription is mandatory for the creation of dynamic scope and you can't edit it after the dynamic scope is created.
 1. Select **Save**.
 
-## Delete a Dynamic scope (preview)
+## Delete a Dynamic scope
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to **Azure Update Manager**. 
 1. Select **Machines** > **Browse maintenance configurations** > **Maintenance configurations**. 
 1. In the **Maintenance configurations** page, select the name of the maintenance configuration for which you want to edit an existing Dynamic scope. 
 1. In the given maintenance configuration page > select **Dynamic scopes** and select the scope you want to delete. Select **Remove dynamic scope** and then select **Ok**.
 
-## View patch history of a Dynamic scope (preview)
+## View patch history of a Dynamic scope
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to **Azure Update Manager**. 
 1. Select **History** > **Browse maintenance configurations** > **Maintenance configurations** to view the patch history of a dynamic scope.
@@ -94,7 +93,7 @@ Obtaining consent to apply updates is an important step in the workflow of dynam
 
 #### [From Schedule updates tab](#tab/sc)
 
-1. Follow the steps from 1 to 5 listed in [Add a Dynamic scope (preview)](#add-a-dynamic-scope-preview).
+1. Follow the steps from 1 to 5 listed in [Add a Dynamic scope](#add-a-dynamic-scope).
 1. In **Machines** tab, select **Add machine**, In **Select resources** page, select the machines and select **Add**
 1. In **Configure Azure VMs for schedule updates**, select **Continue  to schedule updates** option to confirm that:
 
diff --git a/articles/update-center/scheduled-patching.md b/articles/update-center/scheduled-patching.md
@@ -13,18 +13,17 @@ ms.author: sudhirsneha
 **Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: On-premises environment :heavy_check_mark: Azure Arc-enabled servers.
 
 > [!IMPORTANT]
-> - For a seamless scheduled patching experience, we recommend that for all Azure VMs, you update the patch orchestration to **Customer Managed Schedules (Preview)** by **30th June 2023**. If you fail to update the patch orchestration by **30th June 2023**, you can experience a disruption in business continuity because the schedules will fail to patch the VMs.[Learn more](prerequsite-for-schedule-patching.md).
-
+> - For a seamless scheduled patching experience, we recommend that for all Azure VMs, you update the patch orchestration to **Customer Managed Schedules** by **30th June 2023**. If you fail to update the patch orchestration by **30th June 2023**, you can experience a disruption in business continuity because the schedules will fail to patch the VMs.[Learn more](prerequsite-for-schedule-patching.md).
 
 You can use Update Manager in Azure to create and save recurring deployment schedules. You can create a schedule on a daily, weekly or hourly cadence, specify the machines that must be updated as part of the schedule, and the updates to be installed. This schedule will then automatically install the updates as per the created schedule for single VM and at scale.
 
 Update Manager uses maintenance control schedule instead of creating its own schedules. Maintenance control enables customers to manage platform updates. For more information, see [Maintenance control documentation](/azure/virtual-machines/maintenance-control).
 
 ## Prerequisites for scheduled patching
 
-1. See [Prerequisites for Azure Update Manager](./overview.md#prerequisites)
-1. Patch orchestration of the Azure machines should be set to **Customer Managed Schedules (Preview)**. For more information, see [how to enable schedule patching on existing VMs](prerequsite-for-schedule-patching.md#enable-schedule-patching-on-azure-vms). For Azure Arc-enabled machines, it isn't a requirement.
 
+1. See [Prerequisites for Update Manager](./overview.md#prerequisites)
+1. Patch orchestration of the Azure machines should be set to **Customer Managed Schedules**. For more information, see [how to enable schedule patching on existing VMs](prerequsite-for-schedule-patching.md#enable-schedule-patching-on-azure-vms). For Azure Arc-enabled machines, it isn't a requirement.
 	> [!Note]
 	> If you set the patch mode to Azure orchestrated (AutomaticByPlatform) but do not enable the **BypassPlatformSafetyChecksOnUserSchedule** flag and do not attach a maintenance configuration to an Azure machine, it is treated as [Automatic Guest patching](../virtual-machines/automatic-vm-guest-patching.md) enabled machine and Azure platform will automatically install updates as per its own schedule. [Learn more](./overview.md#prerequisites).
 
@@ -237,7 +236,7 @@ You can create a new Guest OS update maintenance configuration or modify an exis
 The Azure update Manager allows you to target a group of Azure or non-Azure VMs for update deployment via Azure Policy. The grouping using policy, keeps you from having to edit your deployment to update machines. You can use subscription, resource group, tags or regions to define the scope and use this feature for the built-in policies which you can customize as per your use-case.
 
 > [!NOTE]
-> This policy also ensures that the patch orchestration property for Azure machines is set to **Customer Managed Schedules (Preview)** as it is a prerequisite for scheduled patching. 
+> This policy also ensures that the patch orchestration property for Azure machines is set to **Customer Managed Schedules** as it is a prerequisite for scheduled patching. 
 
 
 ### Assign a policy
diff --git a/articles/update-center/toc.yml b/articles/update-center/toc.yml
@@ -30,7 +30,7 @@
     href: prerequsite-for-schedule-patching.md
   - name: Assessment options
     href: assessment-options.md
-  - name: Dynamic scope (preview)
+  - name: Dynamic scope
     href: dynamic-scope-overview.md
   - name: Query resources with Azure Resource Graph
     href: query-logs.md 
@@ -62,7 +62,7 @@
       href: deploy-updates.md
     - name: Schedule updates
       href: scheduled-patching.md
-    - name: Manage dynamic scope (preview)
+    - name: Manage dynamic scope
       href: manage-dynamic-scoping.md
     - name: Manage update settings
       href: manage-update-settings.md
diff --git a/articles/update-center/tutorial-dynamic-grouping-for-scheduled-patching.md b/articles/update-center/tutorial-dynamic-grouping-for-scheduled-patching.md
@@ -1,5 +1,5 @@
 ---
-title: Schedule updates on Dynamic Scoping.
+title: Schedule updates on Dynamic scoping.
 description: In this tutorial, you learn how to group machines, dynamically apply the updates at scale.
 ms.service: azure-update-manager
 ms.date: 09/18/2023
@@ -9,7 +9,7 @@ ms.author: sudhirsneha
 #Customer intent: As an IT admin, I want dynamically apply patches on the machines as per a schedule.
 ---
 
-# Tutorial: Schedule updates on Dynamic scopes (preview)
+# Tutorial: Schedule updates on Dynamic scopes
 
 **Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: On-premises environment :heavy_check_mark: Azure VMs :heavy_check_mark: Azure Arc-enabled servers.
  
@@ -35,7 +35,7 @@ To create a dynamic scope, follow these steps:
 1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to **Azure Update Manager**.
 1. Select **Overview** > **Schedule updates** > **Create a maintenance configuration**.
 1. In the **Create a maintenance configuration** page, enter the details in the **Basics** tab and select **Maintenance scope** as *Guest* (Azure VM, Arc-enabled VMs/servers).
-1. Select **Dynamic Scopes** and follow the steps to [Add Dynamic scope](manage-dynamic-scoping.md#add-a-dynamic-scope-preview). 
+1. Select **Dynamic Scopes** and follow the steps to [Add Dynamic scope](manage-dynamic-scoping.md#add-a-dynamic-scope). 
 1. In **Machines** tab, select **Add machines** to add any individual machines to the maintenance configuration and select **Updates**.
 1. In the **Updates** tab, select the patch classification that you want to include/exclude and select **Tags**.
 1. Provide the tags in **Tags** tab.
diff --git a/articles/update-center/updates-maintenance-schedules.md b/articles/update-center/updates-maintenance-schedules.md
diff --git a/articles/update-center/whats-new.md b/articles/update-center/whats-new.md
