Generated on: September 10, 2025 Target period: Within the last 24 hours Processing mode: Details Mode Number of updates: 3 items
Published: September 09, 2025 20:45:15 UTC Link: Private Preview: Azure AMD-based Dasv7, Easv7, and Fasv7-series Virtual Machines
Update ID: 500175 Data source: Azure Updates API
Categories: In development, Compute, Linux Virtual Machines, Windows Virtual Machines, Pricing & Offerings, Services
Summary:
What was updated
Azure has introduced a private preview of new AMD-based virtual machines: Dasv7 and Dalsv7 (general purpose), Easv7 (memory-optimized), and Fasv7, Falsv7, Famsv7 (compute-optimized). These VM series come with options for local disk support or without it.
Key changes or new features
These VM families leverage AMD processors to provide cost-effective and performant compute options across general purpose, memory-optimized, and compute-optimized workloads. The preview includes availability in three Azure regions: East US 2, North Europe, and West US 3. The inclusion of local disk support offers flexibility for scenarios requiring temporary storage.
Target audience affected
Developers and IT professionals looking for AMD-based VM options for diverse workload needs, including general compute, memory-intensive applications, and compute-heavy tasks. This is particularly relevant for those aiming to optimize cost and performance or test AMD VM capabilities in preview.
Important notes if any
This offering is currently in private preview, so access requires enrollment and approval. Availability is limited to specific regions. Users should evaluate workload compatibility with AMD architecture and preview limitations before production use. Further updates will follow as the preview progresses.
Reference: https://azure.microsoft.com/updates?id=500175
Details:
The recent Azure update announces the private preview availability of AMD-based Dasv7, Easv7, and Fasv7-series virtual machines (VMs), expanding Azure’s VM portfolio with new general-purpose, memory-optimized, and compute-optimized options that support configurations both with and without local disk storage, currently accessible in East US 2, North Europe, and West US 3 regions.
Background and Purpose:
This update addresses the growing demand for diversified VM options that leverage AMD’s latest EPYC processors, providing enhanced performance and cost-efficiency compared to previous generations. By introducing Dasv7 (general purpose), Easv7 (memory-optimized), and Fasv7 (compute-optimized) series, Azure aims to offer customers more tailored VM choices that balance CPU, memory, and storage performance for varied workloads, while also enabling local disk configurations for scenarios requiring ephemeral storage.
Specific Features and Changes:
Technical Mechanisms and Implementation:
These VM series utilize AMD EPYC 7003 series processors, offering up to 64 vCPUs per VM with improved instructions per cycle (IPC) and energy efficiency. The local disk support leverages NVMe-based ephemeral storage directly attached to the host hardware, providing high IOPS and low latency but without data persistence after VM deallocation or shutdown. Azure’s underlying hypervisor and resource scheduler manage these VMs, ensuring isolation, security, and performance consistency. Integration with Azure Resource Manager (ARM) templates and Azure CLI/PowerShell allows automated provisioning and configuration.
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
These VMs integrate seamlessly with Azure Virtual Network, Azure Load Balancer, and Azure Monitor for networking, scaling, and telemetry. They support Azure Disk Storage for persistent data needs alongside local ephemeral disks. Azure Backup and Azure Site Recovery can be used for data protection, although ephemeral disks require special handling. Additionally, these VMs can be orchestrated via Azure Kubernetes Service (AKS) or Azure Batch for containerized or batch workloads, respectively, leveraging the compute and
Published: September 09, 2025 16:30:49 UTC Link: Generally Available: Multitenant Managed Logging in Container Insights
Update ID: 502561 Data source: Azure Updates API
Categories: Launched, DevOps, Management and governance, Azure Monitor, Features, Management
Summary:
What was updated
The Multitenant Managed Logging feature in Azure Monitor Container Insights for AKS clusters is now generally available.
Key changes or new features
This update enables customers running shared Azure Kubernetes Service (AKS) clusters to segregate container logs by team or tenant. Each team can independently manage and access their own logs without interference, improving security and operational efficiency. The feature supports multitenant environments by isolating log data, simplifying troubleshooting and monitoring for each team.
Target audience affected
Developers and IT professionals managing shared or multitenant AKS clusters who need granular log segregation and access control. This is especially relevant for organizations with multiple teams or departments sharing the same AKS infrastructure.
Important notes if any
The feature requires configuration within Container Insights and may involve role-based access control (RBAC) adjustments to enforce log access segregation. Users should review their logging and monitoring setup to leverage this capability fully. This GA release ensures production readiness and Microsoft support.
For more details, visit: https://azure.microsoft.com/updates?id=502561
Details:
The recent general availability of Multitenant Managed Logging in Azure Monitor Container Insights addresses a critical need for organizations operating shared Azure Kubernetes Service (AKS) clusters by enabling secure and efficient segregation of container logs at the team level. Traditionally, Container Insights aggregates logs from all containers within an AKS cluster into a single workspace, which can complicate log management, access control, and compliance in multiteam or multidepartment environments. This update introduces a structured approach to isolate and manage logs per tenant or team, enhancing operational security and governance.
Background and Purpose
As enterprises increasingly adopt shared AKS clusters to optimize resource utilization and reduce operational overhead, the challenge of providing isolated observability data to multiple teams without cross-access arises. Prior to this update, teams had to rely on complex query filters or separate workspaces per cluster, which could be inefficient and costly. The Multitenant Managed Logging feature is designed to simplify this by enabling native support for multitenancy within a single Container Insights workspace, facilitating granular log segregation and access control.
Specific Features and Detailed Changes
Technical Mechanisms and Implementation Methods
Under the hood, Container Insights leverages Azure Monitor Logs and Log Analytics workspaces. The multitenant feature extends the existing data collection pipeline by injecting tenant metadata into the log records at ingestion time. This is typically achieved by configuring the Azure Monitor Container Insights agent (based on the Azure Monitor for containers solution) to recognize tenant identifiers from Kubernetes metadata such as namespaces, labels, or annotations. The logs are then indexed with these tenant tags, enabling scoped queries. Azure RBAC policies are applied at the workspace or resource level to restrict access, and Azure Monitor workbooks and alerts can be customized per tenant.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
In summary, the general availability of Multitenant Managed Logging in Container Insights significantly enhances
Published: September 09, 2025 11:15:09 UTC Link: Retirement: Microsoft Playwright Testing (Preview) will be retired on March 8, 2026
Update ID: 499860 Data source: Azure Updates API
Categories: Developer tools, DevOps, Web, Microsoft Playwright Testing, Retirements
Summary:
What was updated
Microsoft announced the retirement of Microsoft Playwright Testing (Preview) within Azure App Testing, effective March 8, 2026.
Key changes or new features
Azure App Testing initially combined Azure Load Testing and Microsoft Playwright Testing to provide unified functional and performance testing capabilities. With this update, the Playwright Testing preview will be discontinued, while Azure Load Testing continues as a standalone service. Developers and QA teams will need to transition away from Playwright Testing in Azure App Testing before the retirement date.
Target audience affected
Developers, QA engineers, and IT professionals who use Azure App Testing for browser-based functional testing with Microsoft Playwright will be impacted. Those relying on Playwright Testing in Azure for automated UI testing should plan migration strategies.
Important notes if any
The retirement is scheduled well in advance (March 8, 2026), allowing ample time for customers to adapt. Users should review their testing workflows and consider alternative Playwright testing solutions outside Azure App Testing or other Azure services. Azure Load Testing remains supported for performance testing needs. For more details, refer to the official Azure update link.
Details:
The announced retirement of Microsoft Playwright Testing (Preview) on March 8, 2026, reflects Microsoft’s strategic consolidation of testing services under the unified Azure App Testing platform, which integrates Azure Load Testing and Playwright Testing to streamline functional and performance testing workflows. This update aims to simplify and enhance the developer and QA experience by providing a single, cohesive service for large-scale testing scenarios.
Background and Purpose:
Microsoft Playwright Testing (Preview) was introduced to offer developers and QA teams a cloud-based solution for automated browser testing using the Playwright framework, enabling cross-browser functional testing at scale. However, with the launch of Azure App Testing, Microsoft sought to unify testing capabilities, combining load and functional testing into one service to reduce fragmentation, improve usability, and provide a more integrated testing ecosystem. The retirement announcement signals the full transition towards Azure App Testing as the primary testing platform.
Specific Features and Detailed Changes:
Technical Mechanisms and Implementation Methods:
Azure App Testing supports Playwright scripts by allowing users to upload or author test scripts that run across multiple browsers and devices in the cloud. The service manages infrastructure provisioning, test execution, and result aggregation. It leverages containerized browser instances and scalable compute resources to run tests in parallel, enabling large-scale functional testing. Integration with Azure DevOps and GitHub Actions facilitates CI/CD pipeline incorporation. The unified service also provides detailed analytics, logs, and failure diagnostics to aid in troubleshooting.
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
Azure App Testing integrates seamlessly with Azure DevOps, GitHub Actions, and Azure Monitor, enabling automated test execution within CI/CD pipelines and centralized monitoring of application health. It also complements Azure Load Testing by allowing combined functional and performance testing strategies. Integration with Azure Application Insights provides telemetry correlation between test results and application performance metrics, enhancing root cause analysis.
In summary, the retirement of Microsoft Playwright Testing (Preview) on March 8
This report was automatically generated - 2025-09-10 03:01:58 UTC