Once again this month, I’m back with my recurring series focused on the evolution of Azure management and security services, with a special focus on hybrid and multicloud scenarios enabled by Azure Arc and enhanced by the use of Artificial Intelligence.
This monthly series aims to:
-
Provide an overview of the most relevant updates released by Microsoft;
-
Share operational tips and field-proven best practices to help architects and IT leaders manage complex and distributed environments more effectively;
-
Follow the evolution towards a centralized, proactive, and AI-driven management model, in line with Microsoft’s vision of AI-powered Management.
The main areas addressed in this series, together with the corresponding tools and services, are described in this article.
Security posture across hybrid and multicloud infrastructures
Microsoft Defender for Cloud
File Integrity Monitoring requires MDE agent version 10.8799 or later for legacy Windows systems
Microsoft has announced an important update regarding File Integrity Monitoring (FIM): following a change in the Microsoft Defender for Endpoint (MDE) pipeline, the feature now requires the Defender for Servers Windows client, meaning the MDE agent, version 10.8799 or later in order to function properly on legacy Windows systems. The change specifically affects downlevel systems such as Windows Server 2016, Windows Server 2012 R2, and other legacy clients, where earlier versions of the agent no longer guarantee the correct operation of file integrity monitoring. For organizations that use FIM as part of their strategies for controlling and detecting unauthorized changes, it is therefore essential to verify the deployed agent version and plan an upgrade where necessary.
Support for Kubernetes gated deployment for AKS Automatic
Support for Kubernetes gated deployment for AKS Automatic clusters is now generally available, expanding protection and control options in release processes on Kubernetes environments managed in Azure. To use this feature, the Defender for Containers sensor must be installed via Helm in the
Severity-based risk assignment for “Not evaluated” recommendations
Microsoft Defender for Cloud has introduced a significant change in the way recommendations previously marked as Not evaluated are handled. These recommendations now receive a risk level derived from their associated severity and are therefore prioritized in the overall list according to the assigned risk. The impact of this change is not merely visual or organizational; it also affects the overall recommendation status and the calculation of the Secure Score, because items that previously did not contribute to risk evaluation are now included. For customers that have not enabled Defender Cloud Security Posture Management (CSPM), the Not evaluated status is removed and replaced with a severity-based classification. To obtain a fully contextualized and environment-aware risk assessment, Microsoft continues to recommend enabling Defender CSPM at the subscription level.
Code-to-runtime enrichment for recommendations (preview)
Microsoft Defender for Cloud is introducing in preview the Code-to-runtime enrichment for recommendations feature, designed to provide end-to-end visibility throughout the entire software development lifecycle. The goal is to enable security teams to connect issues detected at runtime to their origin in the source code, while also understanding the actual extent of the impact generated by a vulnerability or an application change. Among the most relevant capabilities is the ability to follow the Software Development Life Cycle (SDLC) chain from source code to pipelines, from registries to runtime environments, so that the full path of a critical issue can be reconstructed. The feature also makes it possible to analyze the so-called blast radius, meaning the number of assets potentially affected by a single code change, and to trace a runtime recommendation back to the original source of the problem. This approach makes remediation more effective because it allows teams to address the issue at its origin, preventing the same problem from reappearing over time in different environments. For teams looking to strengthen collaboration among development, operations, and security, this new capability represents a concrete step toward a more mature DevSecOps posture.
On-demand antimalware scanning for Azure Files in Microsoft Defender for Storage (preview)
Microsoft has extended the preview of the on-demand antimalware scanning capability in Defender for Storage to also include Azure Files. With this enhancement, it is now possible to scan entire Azure Storage accounts containing both blobs and files, significantly expanding the scope of protection compared to previously covered scenarios. Scans can be initiated directly from the Azure portal or through Representational State Transfer (REST) Application Programming Interfaces (APIs), and they can be integrated into automated processes using Azure Logic Apps, Azure Automation runbooks, or PowerShell scripts. The feature is based on Microsoft Defender Antivirus and uses the most up-to-date antimalware definitions available for each scan. A particularly useful operational element is the presence of a cost estimate in the Azure portal before the scan is started, a feature that helps Information Technology (IT) teams plan service usage more effectively. This extension makes Defender for Storage better suited to scenarios where a higher level of verification is required for shared data and file-based repositories, especially in distributed enterprise environments.
New format for individual recommendations in the Azure portal (preview)
Microsoft Defender for Cloud is introducing in preview a new recommendation format in the Azure portal, based on displaying individual findings instead of the previous aggregated model. This change brings a major transformation to the user experience: vulnerabilities, exposed secrets, and misconfigurations that were previously grouped under a parent recommendation are now shown as distinct items. As a result, users may notice a higher number of recommendations in the overall list, not because new issues have emerged, but because the representation has become more detailed and granular. For the time being, the new format coexists with the previous one, which will, however, be deprecated in the coming months. The new individual recommendations are marked with the Preview and New version tags, which highlight their early status and also make them easier to filter; moreover, at this stage these recommendations do not yet affect the Secure Score. This is a natural evolution aligned with Microsoft’s intention to make security governance more precise, transparent, and action-oriented.
Governance and policy management
Azure Policy
Retirement of the login/logout workaround for fast Azure Policy enforcement
Microsoft has improved Azure Policy responsiveness, making the application of new assignments and policy updates in Azure Resource Manager mode effective within 5 minutes. Thanks to optimizations in the cache refresh mechanism, the so-called login/logout workaround can now be retired. This was a procedure historically used by some customers to manually accelerate the propagation of policy changes. Starting April 30, 2026, this workaround will no longer be available. This decision is part of the ongoing evolution of the service and is intended to further improve overall performance and reliability, offering all customers more predictable, consistent, and efficient behavior in the governance of Azure environments.
Monitoring
Azure Monitor
Log Analytics Workspace: summary rules now support manual “Retry bin” (preview)
Microsoft has introduced a new preview capability for summary rules in Log Analytics Workspace, designed to simplify the handling of errors that may occur during batch aggregation processes. Summary rules make it possible to run periodic aggregations on data stored in the workspace and reimport the summarized results into a custom destination table. However, when a single time interval, or bin, is not processed correctly, gaps can appear in the summarized dataset. With the new Retry bin capability, it is now possible to intervene in a targeted way by rerunning only the bin that returned an error, without having to redefine the existing rule or rebuild the destination table. To trigger the retry, it is sufficient to specify the
Managed GPU metrics for AKS in Azure Monitor (preview)
Microsoft has introduced public preview support for managed Graphics Processing Unit (GPU) metrics for Azure Kubernetes Service (AKS) in Azure Monitor, addressing an increasingly common need in environments running GPU-accelerated workloads. In many scenarios, IT and DevOps teams struggle to obtain unified visibility into GPU utilization alongside Kubernetes cluster metrics, especially when they must rely on manual exporter configurations and dedicated tools. With this enhancement, performance and utilization data from node pools enabled with NVIDIA GPUs are automatically exposed within managed environments based on Prometheus and Grafana. In this way, GPU telemetry becomes part of the same observability stack already used to monitor the cluster, simplifying capacity planning, resource optimization, and operational monitoring activities. This is a particularly interesting evolution for organizations adopting Artificial Intelligence (AI) and machine learning models on AKS and requiring more integrated, consistent, and immediate monitoring tools.
OTLP data ingestion in Azure Monitor with OpenTelemetry Collector (preview)
Microsoft has announced public preview support for native ingestion of OpenTelemetry Protocol (OTLP) signals in Azure Monitor, making it easier to directly send metrics, logs, and traces from applications and platforms instrumented with OpenTelemetry. Thanks to this capability, OpenTelemetry Collector can be configured to send data directly to Azure Monitor cloud ingestion endpoints using Microsoft Entra for authentication. Enablement can take place through Application Insights, which is the recommended approach in most cases because it automates the creation of the required resources and provides integrated application performance management capabilities, or through manual configuration based on data collection endpoints, data collection rules, and dedicated workspaces. The ingested OTLP metrics are stored in Azure Monitor Workspaces and can be queried and used for alerts through PromQL, while logs and traces are saved in Log Analytics workspaces according to new OpenTelemetry tables and semantics. This enhancement strengthens Azure Monitor’s alignment with open standards for modern observability and represents an important step toward simplifying the monitoring of distributed, hybrid, and multicloud environments.
Conclusions
The updates introduced in March 2026 confirm ever more clearly the direction Microsoft has taken: building a model for managing and protecting hybrid and multicloud environments that is increasingly centralized, intelligent, and integrated across the entire lifecycle of resources and applications. On the one hand, Microsoft Defender for Cloud is evolving toward security that is more contextualized, granular, and focused on true risk priority, with features that connect code, pipelines, and runtime more closely than ever before. On the other hand, services such as Azure Policy and Azure Monitor continue to improve in terms of speed, reliability, and alignment with modern observability standards. For IT teams, this means that adopting these new capabilities must go hand in hand with an operational review of processes: verifying agent technical prerequisites, preparing for changes in the portal experience, taking advantage of new automation options, and investing in greater convergence among governance, monitoring, and security. In summary, the message that emerges is clear: to manage increasingly distributed and complex infrastructures, it is no longer enough to simply react to events; it is becoming essential to adopt a proactive, continuous approach supported by artificial intelligence.