Merge branch 'MicrosoftDocs:main' into main

Author: gmndrg

articles/cosmos-db/includes/linux-emulator-instructions.md

@@ -17,7 +17,7 @@
     ```bash
     docker run \
         --publish 8081:8081 \
-        --publish 10251-10254:10251-10254 \
+        --publish 10250-10255:10250-10255 \
         --memory 3g --cpus=2.0 \
         --name=test-linux-emulator \
         --env AZURE_COSMOS_EMULATOR_PARTITION_COUNT=10 \
@@ -33,7 +33,7 @@
     ```bash
     docker run \
         --publish 8081:8081 \
-        --publish 10251-10254:10251-10254 \
+        --publish 10250-10255:10250-10255 \
         --name=test-linux-emulator-mongo \
         --env AZURE_COSMOS_EMULATOR_PARTITION_COUNT=10 \
         --env AZURE_COSMOS_EMULATOR_ENABLE_DATA_PERSISTENCE=true \

articles/cosmos-db/linux-emulator.md

@@ -142,7 +142,7 @@ Use the following steps to run the emulator on Linux:
 
 |Name  |Default  |Description  |
 |---------|---------|---------|
-|  Ports:  `-p`   |         |   Currently, only ports 8081 and 10251-10255 are needed by the emulator endpoint.     |
+|  Ports:  `-p`   |         |   Currently, only ports `8081` and `10250-10255` are needed by the emulator endpoint.     |
 | `AZURE_COSMOS_EMULATOR_PARTITION_COUNT`    |    10     |    Controls the total number of physical partitions, which in return controls the number of containers that can be created and can exist at a given point in time. We recommend starting small to improve the emulator start up time, i.e 3.     |
 |  Memory: `-m`   |         | On memory, 3 GB or more is required.     |
 | Cores:   `--cpus`  |         |   Make sure to allocate enough memory and CPU cores. At least four cores are recommended.      |
@@ -165,9 +165,9 @@ This section provides tips to troubleshoot errors when using the Linux emulator.
 
 - Verify that the specific emulator container is in a running state.
 
-- Verify that no other applications are using emulator ports: 8081 and 10250-10255.
+- Verify that no other applications are using emulator ports: `8081` and `10250-10255`.
 
-- Verify that the container port 8081, is mapped correctly and accessible from an environment outside of the container.  
+- Verify that the container port `8081`, is mapped correctly and accessible from an environment outside of the container.  
 
    ```bash
    netstat -lt

articles/event-grid/authenticate-with-active-directory.md

@@ -71,7 +71,7 @@ Following are the prerequisites to authenticate to Event Grid.
 
 - Install the SDK on your application.
    - [Java](/java/api/overview/azure/messaging-eventgrid-readme#include-the-package)
-   - [.NET](/dotnet/api/overview/azure/messaging.eventgrid-readme-pre#install-the-package)
+   - [.NET](/dotnet/api/overview/azure/messaging.eventgrid-readme#install-the-package)
    - [JavaScript](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/eventgrid/eventgrid#install-the-azureeventgrid-package)
    - [Python](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/eventgrid/azure-eventgrid#install-the-package)
 - Install the Azure Identity client library. The Event Grid SDK depends on the Azure Identity client library for authentication. 

articles/update-center/deploy-updates.md

@@ -41,14 +41,16 @@ To install one time updates on a single VM, follow these steps:
 
 1. Select **Install now** to proceed with the one-time updates.
 
-1. In **Install one-time updates**, select **+Add machine** to add the machine for deploying one-time.
+   - In **Install one-time updates**, select **+Add machine** to add the machine for deploying one-time.
 
-1. In **Select resources**, choose the machine and select **Add**. 
+   - In **Select resources**, choose the machine and select **Add**. 
 
 1. In **Updates**, specify the updates to include in the deployment. For each product, select or deselect all supported update classifications and specify the ones to include in your update deployment. If your deployment is meant to apply only for a select set of updates, its necessary to deselect all the pre-selected update classifications when configuring the **Inclusion/exclusion** updates described below. This ensures only the updates you've specified to include in this deployment are installed on the target machine.
 
    > [!NOTE]
-   > Selected Updates shows a preview of OS updates which may be installed based on the last OS update assessment information available. If the OS update assessment information in update center management (preview) is obsolete, the actual updates installed would vary. Especially if you have chosen to install a specific update category, where the OS updates applicable may vary as new packages or KB Ids may be available for the category.
+   > - Selected Updates shows a preview of OS updates which may be installed based on the last OS update assessment information available. If the OS update assessment information in update center management (preview) is obsolete, the actual updates installed would vary. Especially if you have chosen to install a specific update category, where the OS updates applicable may vary as new packages or KB Ids may be available for the category.
+   > - Update management center (preview) doesn't support driver updates. 
+
 
    - Select **+Include update classification**, in the **Include update classification** select the appropriate classification(s) that must be installed on your machines.
 
@@ -83,7 +85,7 @@ To install one time updates on a single VM, follow these steps:
 
 1. Select to **Install now** to proceed with installing updates.
 
-1. In **Install one-time updates** page, the selected machine appears. Choose the machine, select **Next** and follow the procedure from step 6 listed in **From Overview blade** of [Install updates on single VM](#install-updates-on-single-vm).
+1. In **Install one-time updates** page, the selected machine appears. Choose the machine, select **Next** and follow the procedure from step 4 listed in **From Overview blade** of [Install updates on single VM](#install-updates-on-single-vm).
 
    A notification appears to inform you the activity has started and another is created when it's completed. When it is successfully completed, you can view the installation operation results in **History**. The status of the operation can be viewed at any time from the [Azure Activity log](../azure-monitor/essentials/activity-log.md).
 
@@ -93,7 +95,7 @@ To install one time updates on a single VM, follow these steps:
 1. Under **Operations**, select **Updates**.
 1. In **Updates**, select **Go to Updates using Update Center**.
 1. In **Updates (Preview)**, select **One-time update** to install the updates.
-1. In **Install one-time updates** page, the selected machine appears. Choose the machine, select **Next** and follow the procedure from step 6 listed in **From Overview blade** of [Install updates on single VM](#install-updates-on-single-vm).
+1. In **Install one-time updates** page, the selected machine appears. Choose the machine, select **Next** and follow the procedure from step 4 listed in **From Overview blade** of [Install updates on single VM](#install-updates-on-single-vm).
 
 ---
 

articles/update-center/scheduled-patching.md

@@ -65,6 +65,11 @@ To schedule recurring updates on a single VM, follow these steps:
 
 1. In the **Machines** page, select your machine and select **Next** to continue.
 
+1. In the **Updates** page, specify the updates to include in the deployment such as update classification(s) or KB ID/ packages that must be installed when you trigger your schedule.
+
+    > [!Note] 
+	> Update management center (preview) doesn't support driver updates.
+
 1. In the **Tags** page, assign tags to maintenance configurations.
 
 1. In the **Review + Create** page, verify your update deployment options and select **Create**.
@@ -123,6 +128,12 @@ To schedule recurring updates at scale, follow these steps:
 
 1. In the **Machines** page, verify if the selected machines are listed. You can add or remove machines from the list. Select **Next** to continue.
 
+1. In the **Updates** page, specify the updates to include in the deployment such as update classification(s) or KB ID/ packages that must be installed when you trigger your schedule.
+
+    > [!Note] 
+	> Update management center (preview) doesn't support driver updates.
+
+
 1. In the **Tags** page, assign tags to maintenance configurations.
 
 1. In the **Review + Create** page, verify your update deployment options and select **Create**.

articles/update-center/support-matrix.md

@@ -24,6 +24,9 @@ This article details the Windows and Linux operating systems supported and syste
 ### Operating system updates
 Update management center (preview) supports operating system updates for both Windows and Linux.
 
+> [!NOTE]
+> Update management center (preview) doesn't support driver Updates. 
+
 ### First party updates on Windows
 By default, the Windows Update client is configured to provide updates only for Windows. If you enable the **Give me updates for other Microsoft products when I update Windows** setting, you also receive updates for other products, including security patches for Microsoft SQL Server and other Microsoft software. You can configure this option if you have downloaded and copied the latest [Administrative template files](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra) available for Windows 2016 and later.