Generated on: January 23, 2026 Target period: Within the last 24 hours Processing mode: Details Mode Number of updates: 3 items
Published: January 22, 2026 22:30:50 UTC Link: Generally Available: Deployment safeguards – pod security standard support in AKS
Update ID: 548101 Data source: Azure Updates API
Categories: Launched, Compute, Containers, Azure Kubernetes Service (AKS)
Summary:
What was updated
Azure Kubernetes Service (AKS) Deployment Safeguards now generally supports Pod Security Standards (PSS).
Key changes or new features
AKS Deployment Safeguards can enforce Pod Security Standards policies centrally across multiple clusters. This enables organizations to apply consistent pod security configurations aligned with Kubernetes community-defined standards (Privileged, Baseline, Restricted) during workload deployment. The integration helps prevent non-compliant pods from being deployed, enhancing cluster security posture and governance.
Target audience affected
Developers and IT professionals managing Kubernetes workloads on AKS, especially those responsible for security compliance, cluster governance, and DevOps automation.
Important notes if any
This feature simplifies enforcement of pod security policies without manually configuring admission controllers per cluster. It supports scalable, centralized security policy management, reducing risks of misconfiguration and improving operational efficiency in multi-cluster environments. Users should review their existing pod security requirements and align them with supported PSS profiles to leverage this capability effectively.
Link: https://azure.microsoft.com/updates?id=548101
Details:
The recent Azure update announces the general availability of Pod Security Standards support within Deployment Safeguards for Azure Kubernetes Service (AKS), addressing the critical need for consistent and centralized enforcement of pod security configurations across Kubernetes clusters.
Background and Purpose
Kubernetes workloads require stringent security controls to prevent misconfigurations that could lead to vulnerabilities such as privilege escalation, container breakout, or unauthorized access. While Kubernetes offers Pod Security Policies (PSPs), their deprecation and complexity have driven the community toward standardized Pod Security Standards (PSS), which define baseline, restricted, and privileged security profiles. Organizations managing multiple AKS clusters need a scalable, uniform mechanism to enforce these standards at deployment time, ensuring compliance and reducing operational risk. This update integrates PSS enforcement into AKS Deployment Safeguards, enabling centralized policy management and automated validation during workload deployment.
Specific Features and Detailed Changes
Technical Mechanisms and Implementation Methods
Deployment Safeguards operates as a gatekeeper in the AKS deployment pipeline. It intercepts deployment requests and validates pod specifications against the selected Pod Security Standard profiles. This validation checks key security settings such as privilege escalation, host network access, volume types, and capabilities. The enforcement is implemented through admission control mechanisms integrated into the AKS control plane, ensuring that non-compliant pods are rejected before they are scheduled. Configuration of these safeguards is managed via Azure Portal, CLI, or ARM templates, where administrators specify the desired PSS level for targeted clusters or namespaces.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
Published: January 22, 2026 17:30:31 UTC Link: Generally Available: StandardV2 NAT Gateway with zone-redundancy and StandardV2 public IPs
Update ID: 547772 Data source: Azure Updates API
Categories: Launched, Networking, Azure NAT Gateway
Summary:
What was updated
Azure StandardV2 NAT Gateway and StandardV2 Public IP addresses and prefixes are now generally available.
Key changes or new features
StandardV2 NAT Gateway offers enhanced resiliency with built-in zone-redundancy, improved performance, and supports dual-stack (IPv4 and IPv6) connectivity. These improvements come at the same price point as the original Standard SKU. Additionally, StandardV2 Public IPs and prefixes provide better integration and scalability for outbound connectivity scenarios.
Target audience affected
Developers and IT professionals managing Azure virtual networks, especially those implementing NAT Gateway for outbound internet connectivity, load balancing, or requiring high availability and dual-stack support.
Important notes if any
Migrating to StandardV2 NAT Gateway enables zone-redundancy, reducing downtime risks from zone failures. Dual-stack support facilitates modern application requirements for IPv6. Pricing remains unchanged from Standard SKU, allowing cost-effective upgrades. Users should review compatibility and plan for migration to leverage these enhancements fully.
For more details, visit: https://azure.microsoft.com/updates?id=547772
Details:
The recent general availability of the StandardV2 NAT Gateway and StandardV2 Public IP addresses in Azure introduces significant enhancements in network resiliency, performance, and dual-stack (IPv4 and IPv6) support, all while maintaining cost parity with the previous Standard SKU. This update addresses the growing demand for robust, scalable, and highly available outbound connectivity solutions in cloud-native and hybrid environments.
Background and Purpose
Azure NAT Gateway is a critical service that provides outbound internet connectivity for virtual networks without exposing individual VMs to inbound traffic. The original Standard SKU NAT Gateway, while reliable, had limitations in zone redundancy, IP performance, and lacked native dual-stack support. As enterprises increasingly adopt multi-zone architectures and require IPv6 alongside IPv4, Microsoft developed the StandardV2 SKU to meet these evolving networking needs, ensuring higher availability and scalability.
Specific Features and Detailed Changes
Technical Mechanisms and Implementation Methods
StandardV2 NAT Gateway leverages Azure’s underlying zone-redundant infrastructure to distribute outbound SNAT (Source Network Address Translation) sessions across multiple zones. It integrates with StandardV2 Public IP addresses and prefixes, which are themselves zone-redundant, ensuring that IP addresses remain available even if a zone becomes unavailable. The dual-stack functionality is implemented by allowing simultaneous binding of IPv4 and IPv6 addresses to the NAT Gateway, enabling seamless outbound connectivity for both protocols. Deployment is managed via Azure Portal, CLI, PowerShell, or ARM templates, with options to specify zone redundancy and associate StandardV2 Public IPs or prefixes.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
StandardV2 NAT Gateway integrates seamlessly with Azure Virtual Networks, Virtual Machine Scale Sets, Azure Kubernetes Service (AKS), and Azure Firewall to provide consistent outbound
Published: January 22, 2026 17:00:03 UTC Link: Generally Available: Reporting in Playwright Workspaces (part of Azure App Testing)
Update ID: 550379 Data source: Azure Updates API
Categories: Launched, Developer tools, DevOps, Azure Load Testing
Summary:
What was updated
Reporting capabilities in Playwright Workspaces, part of Azure App Testing, have reached general availability.
Key changes or new features
The update introduces an integrated and flexible reporting experience directly within Playwright Workspaces. It enables collaborative test result analysis, making debugging more streamlined and efficient. Developers can now view detailed test reports, track failures, and share insights easily within the workspace environment, reducing the time to identify and resolve issues.
Target audience affected
Developers using Playwright for automated testing and IT professionals involved in test management and quality assurance within Azure App Testing environments.
Important notes if any
This enhancement is designed to improve productivity by consolidating test reporting and collaboration in one place, supporting faster iteration cycles. Users should explore the new reporting UI and collaboration features to maximize debugging efficiency. No additional setup is required to start using the reporting features in Playwright Workspaces.
Details:
The recent general availability of Reporting in Playwright Workspaces, part of Azure App Testing, introduces a robust, integrated reporting framework aimed at enhancing the test debugging and analysis workflow for developers and QA engineers using Playwright for end-to-end testing. This update addresses the need for a more collaborative and insightful testing environment by embedding comprehensive reporting directly within the Playwright Workspaces interface.
Background and Purpose:
Playwright Workspaces provide a cloud-based environment for developing, running, and managing Playwright tests. Prior to this update, while Playwright offered powerful cross-browser automation capabilities, the reporting and debugging process often required external tools or manual aggregation of test results, which could slow down diagnosis and resolution of test failures. The purpose of this update is to streamline test result visualization and collaboration, thereby reducing the feedback loop in continuous integration/continuous deployment (CI/CD) pipelines and improving overall test reliability.
Specific Features and Detailed Changes:
Technical Mechanisms and Implementation Methods:
The reporting system leverages Azure’s scalable cloud infrastructure to capture and store extensive test metadata and artifacts securely. Test executions within Playwright Workspaces automatically generate structured logs and media files, which are indexed and rendered in the reporting UI using a combination of Azure Blob Storage for artifact storage and Azure Cosmos DB or Azure SQL for metadata management. The UI is built with React and integrates tightly with the Playwright test runner APIs to fetch real-time updates. Authentication and access control are managed via Azure Active Directory to ensure secure collaboration.
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
In summary, the GA release of Reporting in Playwright Workspaces significantly
This report was automatically generated - 2026-01-23 03:02:05 UTC