# Azure Security & Identity: Cosmos DB Key Rotation Insights and Entra ID MFA Flexibility

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

### Daily Azure Security & DevSecOps Briefing: Key Updates & IaC Availability

As your Azure Security Architect and DevSecOps Lead, here's a summary of today's critical Azure updates, focusing on their security implications and current Terraform `hashicorp/azurerm` provider support.

---

#### Azure Cosmos DB: Safe Key Rotation

*   **Feature & Security Summary**: This vital update introduces 'Safe Key Rotation' for Azure Cosmos DB, providing administrators with precise timestamp metadata indicating the last usage of each account key. This feature was introduced to mitigate the risk of accidental service outages or access issues during key management. By enabling informed decision-making, organizations can confidently rotate or retire only inactive or unused keys, significantly enhancing their security posture by reducing the attack surface from potentially compromised active keys and ensuring compliance with key rotation policies.
    *   **Terraform Availability**: Currently, direct management of this 'Safe Key Rotation' feature via the `hashicorp/azurerm` provider is **not supported**. While the `azurerm_cosmosdb_account` resource (latest version: N/A, first version: N/A) manages the Cosmos DB account itself, this specific key rotation metadata feature is not exposed for IaC configuration. Refer to the [AzureRM Cosmos DB Account documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/cosmosdb_account) for existing capabilities.

#### Microsoft Entra ID: Choose Your Own Telephony (CYOT) for MFA

*   **Feature & Security Summary**: Microsoft Entra ID is introducing 'Choose Your Own Telephony' (CYOT) for third-party SMS and voice authentication, with availability slated for October 30, 2026. This feature empowers organizations to integrate their preferred third-party SMS and voice providers for multi-factor authentication (MFA) delivery. The primary driver for this introduction is to offer greater flexibility, potential cost optimization, and enhanced control over MFA mechanisms. From a security and compliance perspective, CYOT allows organizations to tailor their MFA solutions to specific regional telephony regulations or corporate policies, potentially improving the reliability and security of MFA delivery by leveraging trusted, specialized providers.
    *   **Terraform Availability**: This 'Choose Your Own Telephony' feature for Entra ID MFA is a future capability and is **not yet supported** by the `hashicorp/azuread` provider. There are no specific resources (latest version: N/A, first version: N/A) within the provider that directly manage this upcoming tenant-level configuration. For general Entra ID resources, consult the [AzureAD Provider documentation](https://registry.terraform.io/providers/hashicorp/azuread/latest/docs).

## Announcements in this summary

- [Azure Cosmos DB](https://azure.microsoft.com/updates?id=576716) (Databases)
- [Microsoft Entra ID](https://azure.microsoft.com/updates?id=577273) (Identity and Access Management)
