# Microsoft Azure Security & DevSecOps Brief: Critical Retirements, AI Integration, and Resilience Previews

- Cloud: Microsoft Azure
- Date: 2026-10-08
- Canonical page: https://jonathanglass.cloud/whats-new/azure/2026-10-08.html
- Dataset: https://jonathanglass.cloud/data/azure/daily_summaries.json

# Daily Azure Security & DevSecOps Summary

## Key Updates & IaC Availability

*   **Azure App Service on Azure Stack Hub - Retirement Announcement**: This update details the upcoming retirement of Azure App Service on Azure Stack Hub by September 30, 2029. This is a critical lifecycle announcement requiring organizations to plan migrations to alternative solutions or public Azure App Service to maintain security updates, compliance, and operational stability. Proactively addressing end-of-life services is vital to avoid unsupported software risks. **Terraform Availability**: The `hashicorp/azurerm` provider supports Azure App Service resources. While primarily for public Azure, it can manage App Service on Azure Stack Hub by configuring the 'environment' parameter. Resources like `azurerm_app_service` and `azurerm_app_service_plan` are relevant. Supported since v1.0.0, with current versions like v3.99.0 offering comprehensive support. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/app_service).
*   **Azure Kubernetes Service - Pod Name Dimension Retirement**: Azure Monitor platform metrics for AKS are retiring the pod name dimension for `kube_pod_status_phase` and related counters by September 30, 2027. This change aims to optimize monitoring data, potentially improving performance and cost efficiency. DevSecOps teams must adjust monitoring queries and dashboards to rely on aggregated data, ensuring continued visibility into cluster health without relying on granular pod-level naming in platform metrics, thus maintaining efficient observability. **Terraform Availability**: The `azurerm_kubernetes_cluster` resource in the `hashicorp/azurerm` provider (supported since v2.5.0, latest v4.1.0) manages AKS clusters. While this specific metric dimension change is an operational detail within the service, Terraform manages the underlying AKS cluster where these metrics are collected. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/kubernetes_cluster).
*   **App Service - Java 8, 11, 17 Retirement**: Support for Java 8, 11, and 17 on Azure App Service is retiring on September 1, 2027. This critical lifecycle update necessitates planning migrations to newer, supported Java versions (e.g., Java 21 LTS) to maintain security patches, performance improvements, and access to the latest language features. Running applications on unsupported runtimes poses significant security risks due to unpatched vulnerabilities and compliance challenges. **Terraform Availability**: The `hashicorp/azurerm` provider supports App Service resources like `azurerm_linux_web_app` (supported since v2.50+, latest v4.0+). Terraform can be used to define and manage the `java_version` setting within the `site_config` block for `azurerm_app_service` or `azurerm_linux_web_app` resources, facilitating the transition to newer Java runtimes. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/linux_web_app).
*   **Azure SQL Database - Intel SGX Enclave Retirement**: Intel SGX enclaves for Always Encrypted in Azure SQL Database are retiring by October 31, 2027, with a recommended transition to Virtualization-Based Security (VBS) enclaves. This is a significant security update. VBS enclaves offer a robust, hardware-independent alternative for protecting sensitive data during computation, enhancing the confidentiality and integrity of data. Organizations must update Always Encrypted configurations to use VBS enclaves to maintain the highest level of data protection and compliance for highly sensitive data. **Terraform Availability**: The `hashicorp/azurerm` provider supports Azure SQL Database resources, including `azurerm_sql_database` (supported since v2.99.0, latest v3.90.0). While direct configuration of enclave types might be an in-database setting, Terraform manages the SQL Database itself, allowing for the deployment of databases that can then be configured for VBS enclaves. Future provider versions may expose more granular enclave settings. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/sql_database).
*   **Azure Kubernetes Service - Public Preview: AKS on bare metal now on Ubuntu**: This public preview expands deployment options for AKS, allowing customers to run Kubernetes directly on physical hardware with Ubuntu. This offers greater control, improved performance, and reduced virtualization overhead, particularly beneficial for hybrid cloud and edge computing scenarios. DevSecOps teams gain flexibility for consistent Kubernetes management across diverse environments. Security considerations will involve managing and hardening the bare metal host OS. **Terraform Availability**: The `azurerm_kubernetes_cluster` resource in the `hashicorp/azurerm` provider (supported since v2.50.0, latest v4.1.0) is used to provision AKS clusters. While "AKS on bare metal" is a specific deployment model, Terraform would manage the AKS control plane and potentially integration points. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/kubernetes_cluster).
*   **Azure Automation - Runtime Retirement (Python 2.7, 3.8, PowerShell 7.1, 7.2)**: Support for Python 2.7, 3.8, and PowerShell 7.1, 7.2 in Azure Automation is retiring on September 30, 2026. This is a critical update for maintaining secure and performant automation runbooks. Organizations must migrate runbooks to supported versions (e.g., Python 3.10+, PowerShell 7.x LTS) to ensure access to security patches, bug fixes, and new features, mitigating significant security vulnerabilities and operational risks. **Terraform Availability**: The `hashicorp/azurerm` provider supports `azurerm_automation_account` (supported since v2.0, latest v4.0). While Terraform manages the Automation Account, runbook content and runtime versions are typically managed within the Automation Account itself or via `azurerm_automation_runbook` resources. Terraform helps provision the Automation Account correctly, ready for updated runbooks. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/automation_account).
*   **Azure Web Application Firewall - Public Preview: Exceptions in WAF for Application Gateway and Front Door**: This public preview enhances WAF's flexibility by allowing specific exceptions to WAF rules. This is crucial for reducing false positives for legitimate traffic, ensuring business continuity, and improving operational efficiency. From a security perspective, it enables fine-tuning WAF policies without compromising overall protection, allowing applications with unique traffic patterns to function correctly while still being protected against common web attacks. **Terraform Availability**: The `hashicorp/azurerm` provider supports `azurerm_web_application_firewall_policy` (supported since v2.60.0, latest v3.80.0). As this is a preview feature, direct Terraform support for WAF exceptions might be introduced in future provider versions. Currently, Terraform manages the WAF policy itself. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/web_application_firewall_policy).
*   **Azure Front Door - Public Preview: Azure Front Door edge actions**: This public preview allows for more granular control and customization of traffic processing at the Azure Front Door edge. Edge actions can include URL rewrites, header modifications, and other routing logic, improving performance, SEO, and security by handling requests more efficiently. DevSecOps teams can leverage this for advanced traffic management, A/B testing, and security policy enforcement at the global edge, enhancing application resilience and user experience. **Terraform Availability**: The `hashicorp/azurerm` provider supports `azurerm_cdn_frontdoor_route` (supported since v3.0.0, latest v3.75.0). As this is a preview feature, specific resources or properties for "edge actions" might be added in upcoming provider versions. Terraform currently manages Front Door profiles and routes, providing the foundation for these advanced configurations. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/cdn_frontdoor_route).
*   **Azure Databricks - General Availability of Open AI GPT-5.6**: The General Availability of Open AI GPT-5.6 on Azure Databricks allows customers with Microsoft Foundry purchases to deploy and use GPT-5.6 via Model Serving Endpoints. This significantly enhances Databricks' capabilities for large language model (LLM) operations, providing a secure and managed environment for advanced AI workloads. From a security and compliance standpoint, leveraging a managed service for LLM deployment ensures enterprise-grade security, access control, data governance, and auditing. **Terraform Availability**: The `hashicorp/azurerm` provider supports `azurerm_databricks_workspace` (supported since v2.1.0, latest v3.90.0). Terraform can provision and manage the Databricks workspace, which then hosts the Model Serving Endpoints for GPT-5.6. While the specific model deployment is an in-service configuration, Terraform ensures the secure and compliant provisioning of the underlying platform. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/databricks_workspace).
*   **Chaos Studio - Public Preview: Workspaces and Scenarios**: This public preview introduces Azure Chaos Studio Workspaces and Scenarios for faster, targeted chaos engineering experiments. This empowers organizations to proactively identify and remediate weaknesses in their systems by simulating real-world failures. From a DevSecOps and reliability engineering perspective, this is invaluable for building resilient applications, validating disaster recovery plans, and improving overall system reliability and security posture by discovering vulnerabilities before they impact production. **Terraform Availability**: The `hashicorp/azurerm` provider supports `azurerm_chaos_studio_workspace` (supported since v3.50+, latest v4.0+). Terraform can be used to provision and manage Chaos Studio workspaces, enabling IaC for resilience testing. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/chaos_studio_workspace).

## Announcements in this summary

- [Azure App Service on Azure Stack Hub](https://azure.microsoft.com/updates?id=568178) (Compute)
- [Azure Kubernetes Service](https://azure.microsoft.com/updates?id=570232) (Containers)
- [App Service](https://azure.microsoft.com/updates?id=568585) (Web)
- [Azure SQL Database](https://azure.microsoft.com/updates?id=569236) (Databases)
- [Azure Kubernetes Service](https://azure.microsoft.com/updates?id=573782) (Containers)
- [Azure Automation](https://azure.microsoft.com/updates?id=567556) (Automation)
- [Azure Web Application Firewall](https://azure.microsoft.com/updates?id=567218) (Security)
- [Azure Front Door](https://azure.microsoft.com/updates?id=567402) (Networking)
- [Azure Databricks](https://azure.microsoft.com/updates?id=567431) (Analytics)
- [Chaos Studio](https://azure.microsoft.com/updates?id=567184) (Reliability)
