# Azure Security & DevSecOps Daily Brief: WAF Enhancements, Confidential Compute, and IaC Updates

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

## Daily Azure Security & IaC Update

### Compute

*   **Azure Container Apps**: Migration of logging destination from Log Analytics (legacy) to Azure Monitor for Azure Container Apps environments. This enhances observability, centralizes logging, and improves compliance by leveraging Azure Monitor's advanced features for log ingestion, analysis, and alerting. It provides a more robust and scalable logging solution, crucial for security monitoring and incident response. **Terraform Availability**: Supported by `azurerm_container_app_environment` in `hashicorp/azurerm` provider versions `1.0+` to `3.0+`. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/container_app_environment).

*   **Azure Confidential VMs**: Generally Available: Large OS Disk Encryption for Azure Confidential VM migrations. This enhances the security and compliance posture for confidential workloads by ensuring that even large OS disks remain encrypted throughout their lifecycle, including during migration. This is crucial for protecting sensitive data in use and at rest, meeting stringent regulatory requirements, and maintaining data confidentiality even in highly sensitive environments. **Terraform Availability**: Supported by `azurerm_linux_virtual_machine` (and implicitly `azurerm_windows_virtual_machine` for Windows Confidential VMs) in `hashicorp/azurerm` provider versions `3.0+` to `4.0+`. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/linux_virtual_machine).

### Networking

*   **Azure Front Door Premium**: Generally Available: HTTP DDoS ruleset for Azure Front Door Premium WAF. This significantly strengthens the security posture of web applications by providing advanced protection against volumetric and protocol-based DDoS attacks at the edge. It allows for fine-grained control over HTTP traffic, mitigating common attack vectors and ensuring application availability and resilience. **Terraform Availability**: Supported by `azurerm_cdn_frontdoor_firewall_policy` in `hashicorp/azurerm` provider versions `3.0.0` to `4.0.0`. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/cdn_frontdoor_firewall_policy).

*   **Azure Front Door**: Generally Available: Profile and route-level WAF policies for Azure Front Door Premium. This significantly improves flexibility and scalability for WAF deployments. Security architects can now define a baseline WAF policy for an entire Front Door profile and apply specific, granular WAF policies to individual routes. This allows for tailored protection based on application requirements, enhancing the security posture by applying the right level of defense where needed, and simplifying management of complex WAF rulesets. **Terraform Availability**: Supported by `azurerm_cdn_frontdoor_firewall_policy` in `hashicorp/azurerm` provider versions `2.90.0` to `3.90.0`. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/cdn_frontdoor_firewall_policy).

### Databases

*   **Azure SQL Database**: Support for database-level managed identity (including FIC) in CREATE DATABASE SCOPED CREDENTIAL T-SQL. This enhances security by allowing Azure SQL Databases to authenticate to other Azure services (like Azure Storage or Key Vault) using a managed identity, eliminating the need for hardcoded credentials or connection strings. This reduces the risk of credential leakage and simplifies credential management, aligning with least privilege principles. **Terraform Availability**: Supported by `azurerm_mssql_database` in `hashicorp/azurerm` provider versions `3.0+` to `4.0+`. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/mssql_database).

### AI + Machine Learning

*   **Azure MCP Server**: The core update is the general availability of Azure MCP Server 3.0, which expands the interaction capabilities for AI agents and developer tools within Azure through the open Model Context Protocol. A key highlight is the explicit mention of enhanced 'Infrastructure as code: Azure Terraform' support, indicating improved automation and deployment options for services and components that utilize MCP Server 3.0. This facilitates secure, repeatable deployments of AI-driven solutions. **Terraform Availability**: Direct resource support for Azure MCP Server is not currently available in the `hashicorp/azurerm` provider.

### Storage

*   **Azure Storage**: The core feature update is the increase in the default limit of Azure Storage accounts with standard endpoints per region, per subscription. Previously capped at 250, this limit has now been raised to 1,000. While not a direct security feature, this update enables greater scalability and consolidation of storage resources. From a security and governance perspective, it allows for more granular resource organization within a single subscription, potentially simplifying policy enforcement and access management by reducing the need to spread storage across multiple subscriptions. **Terraform Availability**: Supported by `azurerm_storage_account` in `hashicorp/azurerm` provider versions `1.0.0` to `3.90.0`. [Documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/storage_account).

*   **Azure Backup**: The new Cross-Tenant Restore (CTR) feature enables the restoration of Azure VM backups from a source tenant to a completely separate, target Azure tenant. This functionality is designed to provide an isolated recovery environment, crucial for disaster recovery and cyberattack scenarios where the primary tenant might be compromised. It utilizes existing backup copies, streamlining the recovery process and reducing the need for additional infrastructure or complex data transfer mechanisms between tenants. **Terraform Availability**: While `azurerm_backup_vault` exists, direct Terraform support for configuring the Cross-Tenant Restore *feature* itself is not explicitly available in the `hashicorp/azurerm` provider. This is typically an operational action rather than a resource configuration.

## Announcements in this summary

- [Azure Container Apps](https://azure.microsoft.com/updates?id=577689) (Compute)
- [Azure Front Door Premium](https://azure.microsoft.com/updates?id=578681) (Networking)
- [Azure SQL Database](https://azure.microsoft.com/updates?id=577491) (Databases)
- [Azure MCP Server](https://azure.microsoft.com/updates?id=578662) (AI + Machine Learning)
- [Azure Storage](https://azure.microsoft.com/updates?id=578358) (Storage)
- [Azure Front Door](https://azure.microsoft.com/updates?id=578153) (Networking)
- [Azure Backup](https://azure.microsoft.com/updates?id=577117) (Storage)
- [Azure Confidential VMs](https://azure.microsoft.com/updates?id=578850) (Compute)
