Merge pull request #314151 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-02 11:00 UTC

Author: learn-build-service-prod[bot]

articles/automation/disable-local-authentication.md

@@ -15,8 +15,7 @@ author: RochakSingh-blr
 # Disable local authentication in Automation
 
 > [!IMPORTANT]
-> - Update Management patching will not work when local authentication is disabled. 
-> - When you disable local authentication, it impacts starting a runbook using a webhook, source control auto sync, Automation Desired State Configuration, and agent-based Hybrid Runbook Workers. For more information, see the [available alternatives](#compatibility).
+> When you disable local authentication, it impacts starting a runbook using a webhook, source control auto sync, and Automation Desired State Configuration. For more information, see the [available alternatives](#compatibility).
 
 Azure Automation provides Microsoft Entra authentication support for all Automation service public endpoints. This critical security enhancement removes certificate dependencies and gives organizations control to disable local authentication methods. This feature provides you with seamless integration when centralized control and management of identities and resource credentials through Microsoft Entra ID is required.
 
@@ -59,7 +58,6 @@ The following table describes the behaviors or features that are prevented from
 |Starting a runbook using a webhook. | Start a runbook job using Azure Resource Manager template, which uses Microsoft Entra authentication. |
 |Using Automation Desired State Configuration.| Use [Azure Policy Guest configuration](../governance/machine-configuration/overview.md).  |
 |Using agent-based Hybrid Runbook Workers.| Use [extension-based Hybrid Runbook Workers](./extension-based-hybrid-runbook-worker-install.md).|
-|Using Automation Update Management |Use [Azure Update Manager](../update-manager/overview.md)|
 
 
 ## Next steps

articles/azure-netapp-files/azure-netapp-files-solution-architectures.md

@@ -8,7 +8,7 @@ ms.custom:
   - linux-related-content
   - build-2025
 ms.topic: concept-article
-ms.date: 03/19/2026
+ms.date: 04/02/2026
 ms.author: anfdocs
 # Customer intent: As a cloud architect, I want to implement Azure NetApp Files to migrate and run mission-critical applications, so that I can ensure high performance, scalability, and security for diverse workloads in the cloud.
 ---
@@ -125,7 +125,7 @@ This section provides references to SAP on Azure solutions.
 * [Manual Recovery Guide for SAP HANA on Azure VMs from Azure NetApp Files snapshot with AzAcSnap](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/manual-recovery-guide-for-sap-hana-on-azure-vms-from-azure/ba-p/3290161)
 * [Azure NetApp Files Backup for SAP Solutions](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/anf-backup-for-sap-solutions/ba-p/3717977)
 * [SAP HANA Disaster Recovery with Azure NetApp Files](https://docs.netapp.com/us-en/netapp-solutions-sap/pdfs/sidebar/SAP_HANA_Disaster_Recovery_with_Azure_NetApp_Files.pdf)
-* [Running SAP Applications on the Microsoft Platform](https://techcommunity.microsoft.com/blog/sapapplications/designing-migrating-and-managing-a-151-node-sap-bw-scale-out-landscape-on-micros/3715003)
+* [Designing, Migrating and Managing a 15+1-Node SAP BW Scale-Out Landscape on Microsoft Azure](https://techcommunity.microsoft.com/blog/sapapplications/designing-migrating-and-managing-a-151-node-sap-bw-scale-out-landscape-on-micros/3715003)
 * [SAP HANA data protection on Azure NetApp Files with SnapCenter](https://techcommunity.microsoft.com/blog/sapapplications/sap-hana-data-protection-on-azure-netapp-files-with-snapcenter/3510031)
 * [SAP System Refresh and Cloning operations on Azure NetApp Files with SnapCenter](https://techcommunity.microsoft.com/blog/sapapplications/sap-system-refresh-and-cloning-operations-on-azure-netapp-files-with-snapcenter/4356389)
 

articles/network-watcher/vnet-flow-logs-overview.md

@@ -64,18 +64,6 @@ In addition to existing support to identify traffic that [network security group
 > 
 > If you enable network security group flow logs on the network security group of a subnet, then you enable virtual network flow logs on the same subnet or parent virtual network, you might get duplicate logging or only virtual network flow logs.
 
-## Platform Rules
-
-#### What is a platform rule in flow logs
-
-In flow logs, a platform rule represents network traffic that is processed by the Azure platform itself rather than by user‑configured rules, such as Network Security Groups (NSGs) or Azure Virtual Network Manager rules. This traffic is handled automatically by the platform and is not the result of an explicit allow or deny rule defined within a deployment. Platform rule entries provide visibility into system‑managed or infrastructure‑level traffic. If analysis is focused only on traffic evaluated by explicitly configured rules, these entries can be filtered out during log analysis.
-
-In some scenarios, traffic associated with you application or workload may appear under a platform rule. This can occur in a limited number of well‑understood cases, such as when load‑balanced connections are recreated as part of normal platform operations, or when return traffic does not require rule evaluation for the response path. In these cases, the traffic is processed as expected, but the flow log may associate it with a platform rule instead of a user‑defined rule.
-
-#### Does the presence of platform rules affect traffic?
-
-No. Platform rules do not change your traffic behavior, connectivity, security posture, or performance. They only affect how certain network flows are represented in flow logs. Platform rule entries are provided for informational purposes. Excluding them from analysis does not impact how traffic is handled. If traffic appears under a platform rule and does not align with the scenarios described above, the behavior can be investigated further. In such cases, reaching out through Azure support channels is recommended so the flow logs can be reviewed in detail.
-
 ## How logging works
 
 Key properties of virtual network flow logs include:
@@ -220,6 +208,18 @@ Here's an example bandwidth calculation for flow tuples from a TCP conversation
 
 For continuation (`C`) and end (`E`) flow states, byte and packet counts are aggregate counts from the time of the previous flow's tuple record. In the example conversation, the total number of packets transferred is 1,021 + 52 + 8,005 + 47 = 9,125. The total number of bytes transferred is 588,096 + 29,952 + 4,610,880 + 27,072 = 5,256,000.
 
+## Platform Rules
+
+#### What is a platform rule in flow logs
+
+In flow logs, a platform rule represents network traffic that is processed by the Azure platform itself rather than by user‑configured rules, such as Network Security Groups (NSGs) or Azure Virtual Network Manager rules. This traffic is handled automatically by the platform and is not the result of an explicit allow or deny rule defined within a deployment. Platform rule entries provide visibility into system‑managed or infrastructure‑level traffic. If analysis is focused only on traffic evaluated by explicitly configured rules, these entries can be filtered out during log analysis.
+
+In some scenarios, traffic associated with you application or workload may appear under a platform rule. This can occur in a limited number of well‑understood cases, such as when load‑balanced connections are recreated as part of normal platform operations, or when return traffic does not require rule evaluation for the response path. In these cases, the traffic is processed as expected, but the flow log may associate it with a platform rule instead of a user‑defined rule.
+
+#### Does the presence of platform rules affect traffic?
+
+No. Platform rules do not change your traffic behavior, connectivity, security posture, or performance. They only affect how certain network flows are represented in flow logs. Platform rule entries are provided for informational purposes. Excluding them from analysis does not impact how traffic is handled. If traffic appears under a platform rule and does not align with the scenarios described above, the behavior can be investigated further. In such cases, reaching out through Azure support channels is recommended so the flow logs can be reviewed in detail.
+
 ## Considerations for virtual network flow logs
 
 ### Storage account

articles/update-manager/arc-enabled-vm-extensions.md

@@ -6,6 +6,7 @@ ms.date: 07/09/2025
 ms.topic: overview
 author: habibaum
 ms.author: v-uhabiba
+ms.update-cycle: 1095-days
 ---
 
 # Release notes for Azure Arc-enabled VM extensions - July 25

articles/update-manager/assessment-options.md

@@ -6,6 +6,7 @@ ms.date: 12/06/2024
 ms.topic: overview
 author: kamalmaini
 ms.author: v-uhabiba
+ms.update-cycle: 1095-days
 # Customer intent: "As an IT administrator, I want to utilize Update Manager to perform periodic and on-demand update assessments on my machines, so that I can ensure they are compliant with the latest updates and manage installations effectively."
 ---
 

articles/update-manager/configure-wu-agent.md

@@ -7,6 +7,7 @@ ms.topic: how-to
 author: habibaum
 ms.author: v-uhabiba
 ms.custom: engagement-fy24
+ms.update-cycle: 1095-days
 # Customer intent: As a system administrator, I want to configure Windows Update settings for Azure Update Manager so that I can keep all Windows servers consistently updated with the latest patches and maintain compliance across the environment.
 ---
 

articles/update-manager/cross-subscription-patching.md

@@ -6,6 +6,7 @@ ms.date: 02/04/2025
 ms.topic: concept-article
 author: habibaum
 ms.author: v-uhabiba
+ms.update-cycle: 1095-days
 # Customer intent: "As an IT operations manager, I want to manage patching across multiple Azure subscriptions from a centralized location, so that I can improve operational efficiency and ensure consistent system reliability by reducing the complexity of patch management."
 ---
 

articles/update-manager/deploy-manage-updates-using-updates-view.md

@@ -7,6 +7,7 @@ ms.author: v-uhabiba
 ms.date: 06/21/2024
 ms.topic: how-to
 ms.custom: sfi-image-nochange
+ms.update-cycle: 1095-days
 # Customer intent: "As an IT administrator, I want to view and manage pending updates for my environment, so that I can ensure all machines are up-to-date and secure from vulnerabilities."
 ---
 

articles/update-manager/deploy-updates.md

@@ -6,6 +6,7 @@ ms.date: 03/07/2025
 ms.topic: how-to
 author: habibaum
 ms.author: v-uhabiba
+ms.update-cycle: 1095-days
 ms.custom:
   - references_regions
   - sfi-image-nochange

articles/update-manager/dynamic-scope-overview.md

@@ -6,6 +6,7 @@ ms.date: 08/21/2025
 ms.topic: concept-article
 author: habibaum
 ms.author: v-uhabiba
+ms.update-cycle: 1095-days
 # Customer intent: "As an IT administrator who manages multiple virtual machines, I want to use dynamic scoping for scheduled patching so that I can efficiently manage and automate updates across various environments without manual intervention."
 ---