Merge pull request #308972 from MicrosoftDocs/main

learn-build-service-prod[bot] · web-flow · commit 1c62221d561b · 2025-12-03T06:15:19.000Z
Auto Publish – main to live - 2025-12-03 06:00 UTC
diff --git a/articles/azure-change-tracking-inventory/change-tracking-inventory-support-matrix.md b/articles/azure-change-tracking-inventory/change-tracking-inventory-support-matrix.md
@@ -2,7 +2,7 @@
 title: Azure Change Tracking and Inventory Support matrix
 description: Get a summary of support settings and limitations for enabling Azure CTI and tracking changes.
 services: automation
-ms.date: 11/06/2025
+ms.date: 12/03/2025
 ms.topic: overview
 ms.service: azure-change-tracking-inventory
 ms.author: v-jasmineme
@@ -12,7 +12,7 @@ author: jasminemehndir
 
 # Support matrix and regions for Azure Change Tracking and Inventory
 
-Azure Change Tracking and Inventory (CTI) monitors changes and provide inventory logs for servers across Azure, on-premises, and other cloud environments. This article summarizes support settings and limitations when you enable Azure CTI and track changes. It also provides information about the supported regions and mappings for Azure CTI using Azure Monitoring Agent.
+Azure Change Tracking and Inventory (CTI) monitors changes and provide inventory logs for servers across Azure, on-premises, and other cloud environments. This article summarizes support settings and limitations when you enable Azure CTI and track changes. It also provides information about the supported regions and mappings for Azure CTI using Azure Monitor Agent.
 
 ## Support matrix
 
@@ -115,7 +115,7 @@ The default collection frequency for Windows services is 30 minutes. To configur
 
 ## Current limitations
 
-Azure CTI using Azure Monitoring Agent doesn't support or has the following limitations:
+Azure CTI using Azure Monitor Agent doesn't support or has the following limitations:
 
 - Recursion for Windows registry tracking
 - Currently, only the HKEY_LOCAL_MACHINE is supported. You will encounter this limitation whenever you manually add the registry key.
@@ -149,7 +149,7 @@ A key capability of Azure CTI is alerting on changes to the configuration state
 |ConfigurationChange <br>&#124; where RegistryKey == @"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\QualityCompat"| Useful for tracking changes to crucial antivirus keys.|
 |ConfigurationChange <br>&#124; where RegistryKey contains @"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy"| Useful for tracking changes to firewall settings.|
 
-## Supported regions and mappings for Change Tracking and Inventory with Azure Monitoring Agent
+## Supported regions and mappings for Change Tracking and Inventory with Azure Monitor Agent
 
 The following table lists the supported regions and mappings:
 
diff --git a/articles/azure-change-tracking-inventory/create-data-collection-rule.md b/articles/azure-change-tracking-inventory/create-data-collection-rule.md
@@ -3,7 +3,7 @@ title: Create Data Collection Rule for Azure Change Tracking and Inventory
 description: Learn how to create a data collection rule (DCR) for Azure Change Tracking and Inventory.
 #customer intent: As a customer, I want to create a Data Collection Rule (DCR) for Azure Change Tracking and Inventory so that I can collect and manage data effectively.
 services: automation
-ms.date: 11/06/2025
+ms.date: 12/03/2025
 ms.topic: how-to
 ms.service: azure-change-tracking-inventory
 ms.author: v-jasmineme
@@ -13,7 +13,7 @@ ms.custom: sfi-image-nochange
 
 # Create data collection rule for Azure Change Tracking and Inventory
 
-When you enable Change Tracking in the Azure portal using the Azure Monitoring Agent (AMA), the process automatically creates a Data Collection Rule (DCR). This rule will appear in the resource group with a name in the format ct-dcr-aaaaaaaaa. After the rule is created, add the required resources.
+When you enable Change Tracking in the Azure portal using the Azure Monitor Agent (AMA), the process automatically creates a Data Collection Rule (DCR). This rule will appear in the resource group with a name in the format ct-dcr-aaaaaaaaa. After the rule is created, add the required resources.
 
 This article explains how to explicitly create a Data Collection Rule for Azure Change Tracking and Inventory (CTI).
 
@@ -48,7 +48,7 @@ To create a DCR, follow these steps:
    :::image type="content" source="media/create-data-collection-rule/deployment-confirmation.png" alt-text="Screenshot of deployment notification.":::
 
 > [!NOTE]
-> After creating the Data Collection Rule using the Azure Monitoring Agent's change tracking schema, ensure that you don't add any Data Sources to this rule. This can cause Azure CTI to fail. You must only add new Resources in this section.
+> After creating the Data Collection Rule using the Azure Monitor Agent's change tracking schema, ensure that you don't add any Data Sources to this rule. This can cause Azure CTI to fail. You must only add new Resources in this section.
 
 ## Next steps
 
diff --git a/articles/azure-change-tracking-inventory/disable-azure-change-tracking-inventory-monitoring-agent.md b/articles/azure-change-tracking-inventory/disable-azure-change-tracking-inventory-monitoring-agent.md
@@ -1,25 +1,25 @@
 ---
-title: Disable Change Tracking and Inventory in Azure using Azure Monitoring Agent
-description: Learn how to disable Change Tracking and Inventory using Azure Monitoring Agent (AMA) from your Azure virtual machines.
+title: Disable Change Tracking and Inventory in Azure using Azure Monitor Agent
+description: Learn how to disable Change Tracking and Inventory using Azure Monitor Agent (AMA) from your Azure virtual machines.
 #customer intent: As a customer, I want to disassociate a Data Collection Rule (DCR) from a virtual machine so that I can disable its association with Change Tracking.
 services: automation
 ms.custom: linux-related-content
-ms.date: 11/06/2025
+ms.date: 12/03/2025
 ms.topic: how-to
 ms.service: azure-change-tracking-inventory
 ms.author: v-jasmineme
 author: jasminemehndir
 ---
 
-# Disable Change Tracking and Inventory with Azure Monitoring Agent
+# Disable Change Tracking and Inventory with Azure Monitor Agent
 
 **Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: Windows Registry :heavy_check_mark: Windows Files :heavy_check_mark: Linux Files :heavy_check_mark: Windows Software
 
 This article describes how to disable change tracking and inventory with AMA.
 
 ## Disable Change Tracking from a VM
 
-To disable change tracking with Azure Monitoring Agent from a virtual machine, you must first disassociate the DCR and then uninstall Azure CTI. Follow these steps:
+To disable change tracking with Azure Monitor Agent from a virtual machine, you must first disassociate the DCR and then uninstall Azure CTI. Follow these steps:
 
 ### Disassociate Data Collection Rule (DCR) from a VM
 
@@ -49,4 +49,4 @@ To uninstall change tracking extension, follow these steps:
 
 ## Next steps
 
-To learn how to migrate from CTI using Log Analytics version to the Azure Monitoring Agent version, see [Migration guidance for Azure CTI](../automation/troubleshoot/change-tracking.md).
+To learn how to migrate from CTI using Log Analytics version to the Azure Monitor Agent version, see [Migration guidance for Azure CTI](../automation/troubleshoot/change-tracking.md).
diff --git a/articles/azure-change-tracking-inventory/enable-change-tracking-at-scale-policy.md b/articles/azure-change-tracking-inventory/enable-change-tracking-at-scale-policy.md
@@ -3,7 +3,7 @@ title: Enable Change Tracking and Inventory at Scale for Azure VMs using Azure P
 description: Learn how to use Azure Policy to enable change tracking and inventory at scale for Windows and Linux VMs, including the Arc-enabled VMs and Azure Virtual Machine Scale Sets.
 #customer intent: As a customer, I want to enable Azure change tracking and inventory for Azure VMs at scale so that I can monitor configuration changes efficiently.
 services: automation
-ms.date: 11/06/2025
+ms.date: 12/03/2025
 ms.topic: how-to
 ms.service: azure-change-tracking-inventory
 author: jasminemehndir
@@ -22,7 +22,7 @@ Before you enable Azure CTI, ensure you [Create a data collection rule (DCR)](cr
 
 ## Enable Azure Change Tracking and Inventory at scale
 
-Using the Deploy if not exist (DINE) policy, you can enable Change tracking with Azure Monitoring Agent at scale and in the most efficient manner.
+Using the Deploy if not exist (DINE) policy, you can enable Change tracking with Azure Monitor Agent at scale and in the most efficient manner.
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and select **Change Tracking and Inventory**.
 
diff --git a/articles/azure-change-tracking-inventory/extension-version-details.md b/articles/azure-change-tracking-inventory/extension-version-details.md
@@ -3,7 +3,7 @@ title: Azure Change Tracking extension version details and known issues
 description: This article describes the Change Tracking extension version details and the known issues.
 #customer intent: As a customer, I want to learn about the fixed vulnerabilities in recent extension updates so that I can maintain a secure environment.
 services: automation
-ms.date: 11/06/2025
+ms.date: 12/03/2025
 ms.topic: overview
 ms.service: azure-change-tracking-inventory
 ms.author: v-jasmineme
@@ -79,7 +79,7 @@ After you migrate from FIM based on AMA to ChangeTracking based on AMA, the memo
 
 #### Issue fixed
 
-The **SvcName** or **SoftwareName** are displayed as garbled string for Japanese or Chinese language VMs. The issue is fixed in latest version of AMA windows (1.24.0). We recommend that you upgrade to Azure Monitoring Agent.
+The **SvcName** or **SoftwareName** are displayed as garbled string for Japanese or Chinese language VMs. The issue is fixed in latest version of AMA windows (1.24.0). We recommend that you upgrade to Azure Monitor Agent.
 
 #### Known issues
 
@@ -95,7 +95,7 @@ For Windows, **SvcDescription** field is coming as base64 encoded string. As a w
 
 #### Issues fixed
 
-**SvcName** or **SoftwareName** are displayed as garbled string for Japanese or Chinese language VMs. The issue is fixed in latest version of AMA windows (1.24.0). We recommend that you upgrade to Azure Monitoring Agent.
+**SvcName** or **SoftwareName** are displayed as garbled string for Japanese or Chinese language VMs. The issue is fixed in latest version of AMA windows (1.24.0). We recommend that you upgrade to Azure Monitor Agent.
 For Windows **SvcDescription** is coming as base64 encoded string. As a workaround, use base64_decode_tostring() kql function.
 
 **OS-specific issues:**
diff --git a/articles/azure-change-tracking-inventory/overview-monitoring-agent.md b/articles/azure-change-tracking-inventory/overview-monitoring-agent.md
@@ -1,9 +1,9 @@
 ---
-title: Azure Change Tracking and Inventory overview using Azure Monitoring Agent
-description: Learn about Change Tracking and Inventory feature using Azure monitoring agent, which helps you identify software and Microsoft service changes in your environment.
+title: Azure Change Tracking and Inventory overview using Azure Monitor Agent
+description: Learn about Change Tracking and Inventory feature using Azure monitor agent, which helps you identify software and Microsoft service changes in your environment.
 #customer intent: As a customer, I want to evaluate the compatibility of Azure Change Tracking and Inventory with my existing infrastructure so that I can ensure seamless integration.
 services: automation
-ms.date: 12/02/2025
+ms.date: 12/03/2025
 ms.topic: overview
 ms.service: azure-change-tracking-inventory
 ms.author: v-jasmineme
diff --git a/articles/azure-change-tracking-inventory/quickstart-monitor-changes-collect-inventory-azure-change-tracking-inventory.md b/articles/azure-change-tracking-inventory/quickstart-monitor-changes-collect-inventory-azure-change-tracking-inventory.md
@@ -2,7 +2,7 @@
 title: Quickstart - Enable Azure Change Tracking and Inventory for single and multiple machines from the portal
 description: In this quickstart, learn how to enable Azure Change Tracking and Inventory for single and multiple machines from the portal.
 services: automation
-ms.date: 11/06/2025
+ms.date: 12/03/2025
 ms.topic: quickstart
 #Customer intent: As a customer, I want to enable Azure Change Tracking and Inventory so that I can further use the CTI services.
 ms.service: azure-change-tracking-inventory
@@ -98,7 +98,7 @@ To enable Azure CTI for multiple Azure VMs using portal, follow these steps:
    > [!NOTE]
    > You can enable CTI on up to 250 virtual machines at a time.
 
-1. On the **Enable Change Tracking** pane, select the banner at the top of the pane, **Click here to try new change tracking and inventory with Azure Monitoring Agent (AMA) experience**.
+1. On the **Enable Change Tracking** pane, select the banner at the top of the pane, **Click here to try new change tracking and inventory with Azure Monitor Agent (AMA) experience**.
 
    :::image type="content" source="media/create-data-collection-rule/enable-change-tracking-multiple-virtual-machines-inline.png" alt-text="Screenshot showing how to select enable change tracking for multiple Virtual Machines from the portal." lightbox="media/create-data-collection-rule/enable-change-tracking-multiple-virtual-machines-expanded.png":::
 
diff --git a/articles/azure-netapp-files/configure-cache-volumes.md b/articles/azure-netapp-files/configure-cache-volumes.md
@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: netapp-manishc
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 11/26/2025
+ms.date: 12/03/2025
 ms.author: anfdocs
 ms.custom: sfi-image-nochange
 # Customer intent: As a cloud administrator, I want to create a cache volume in Azure NetApp Files, so that I can leverage scalable storage solutions and reduce cost.
@@ -26,7 +26,6 @@ Write-back allows the write to be committed to stable storage at the cache and a
 * You should ensure that the protocol type is the same for the cache volume and origin volume. The security style and the Unix permissions are inherited from the origin volume. For example, creating a cache volume with NFSv3 or NFSv4 when origin is UNIX, and SMB when the origin is NTFS.
 * You should enable encryption on the origin volume.
 * The source cluster must be running ONTAP 9.15.1 or later version.
-* The minimum supported ONTAP version without write-back is 9.12.1 or later version.
 * You should configure an Active Directory (AD) or LDAP connection within the NetApp account to create an LDAP-enabled cache volume.
 * You can't move a cache volume to another capacity pool.
 * The `globalFileLocking` parameter value must be the same on all cache volumes that share the same origin volume. Global file locking can be enabled when creating the first cache volume by setting `globalFileLocking` to true. The subsequent cache volumes from the same origin volume must have this setting set to true. To change the global file locking setting on existing cache volumes, you must update the origin volume first. After updating the origin volume, the change propagates to all the cache volumes associated with that origin volume. The `volume flexcache origin config modify -is-global-file-locking-enabled` command should be executed on the source cluster to change the setting on the origin volume.
diff --git a/articles/backup/azure-data-lake-storage-backup-support-matrix.md b/articles/backup/azure-data-lake-storage-backup-support-matrix.md
@@ -27,7 +27,7 @@ Vaulted backups of Azure Data Lake Storage are available in the following region
 | Availability type | Region |
 | --- | --- |
 | **General availability** | Central US, East Asia, France South, Germany West Central, Southeast US, Switzerland North, Switzerland West, UAE North, UK West, West India. |
-| **Preview** | Australia East, Central India, Central US, East US, East US 2, Germany West Central, North Central US, North Europe, South India, Southeast Asia, West Central US, West US, West US 2, West US 3. |
+| **Preview** | Australia East, Central India, Central US, East US, East US 2, North Central US, North Europe, South India, Southeast Asia, West Central US, West US, West US 2, West US 3. |
 
 ## Supported storage accounts
 
diff --git a/articles/governance/policy/concepts/policy-for-kubernetes.md b/articles/governance/policy/concepts/policy-for-kubernetes.md
@@ -610,6 +610,12 @@ Finally, to identify the AKS cluster version that you're using, follow the linke
 
 ### Add-on versions available per each AKS cluster version
 
+#### 1.15.3
+Patch CVE-2025-47914, CVE-2025-58181, CVE-2025-58187, CVE-2025-22872
+- Released Dec 2025
+- Kubernetes 1.27+
+- Gatekeeper 3.20.1-2
+
 #### 1.15.1
 
 - Released Nov 2025
diff --git a/articles/logic-apps/set-up-deployment-slots.md b/articles/logic-apps/set-up-deployment-slots.md
@@ -3,10 +3,10 @@ title: Set Up Deployment Slots for Zero Downtime
 description: Learn to set up deployment slots to enable zero downtime for Standard workflows in Azure Logic Apps. 
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, wsilveira, azla
+ms.reviewers: estfan, wsilveira, azla
 ms.topic: how-to
 ms.custom: sfi-image-nochange
-ms.date: 10/10/2025
+ms.date: 12/02/2025
 #Customer intent: As an integration developer working with Azure Logic Apps, I want to set up deployment slots on my Standard logic app resource so I can deploy with zero downtime.
 ---
 
@@ -40,16 +40,28 @@ With deployment slots, you can achieve continuous delivery and improve the quali
   - Product verification testing before slot swapping
   - A/B testing
 
-- If your storage is private, complete the following steps:
+- Private storage account
+
+  If your storage account is private, complete the following steps:
   
   1. After you create the slot, go to the deployment slot. On the slot menu, under **Settings**, select **Environment variables**.
   1. On the **App settings** tab, find the file share value for the app setting named **WEBSITE_CONTENTSHARE**.
   1. Go to the storage account and manually create a file share that uses the same name.
   1. On each slot, add an app setting named **WEBSITE_OVERRIDE_STICKY_DIAGNOSTICS_SETTINGS**, and set the value to **0**.
 
+- Terraform with Standard logic app and secured storage account
+  
+  If your Standard logic app uses an Azure storage account secured by a firewall where access is allowed only through private endpoints for Azure Blob, Azure File, Azure Table, and Azure Queue, use a Bicep or ARM template to set up your deployment slots and configure the following app settings:
+
+  | App setting | Task |
+  |-------------|------|
+  | **WEBSITE_CONTENTSHARE** | Set this value to the file share name, but make sure that you create the file share folder before you deploy. |
+  | **AzureFunctionsWebHost_hostid** | Set this value to a unique host ID value. |
+  | **WEBSITE_OVERRIDE_STICKY_DIAGNOSTICS_SETTINGS** | Set this value to `0` for all environments. |
+
 ## Prerequisites
 
-- An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+- An Azure account and subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
 - To work in Visual Studio Code with the Azure Logic Apps (Standard) extension, you need to meet the prerequisites described in [Create Standard workflows with Visual Studio Code](create-single-tenant-workflows-visual-studio-code.md#prerequisites). You also need a Standard logic app project that you want to publish to Azure.
 
@@ -134,7 +146,7 @@ Unavailable at this time. Follow the steps for Visual Studio Code or Azure CLI t
    1. Enter and select the name for your Standard logic app.
    1. Select the name for your deployment slot.
 
-1. In the message box that appears, confirm that you want to deploy the current code in your project to the selected slot , and select **Deploy**. This action overwrites any existing content in the selected slot.
+1. In the message box that appears, confirm that you want to deploy the current code in your project to the selected slot, and select **Deploy**. This action overwrites any existing content in the selected slot.
 
 1. After deployment completes, you can update any settings, if necessary, by selecting **Upload settings** in the message box that appears.
 
