Here's your daily summary of key Azure updates, focusing on security, DevSecOps implications, and Terraform Infrastructure-as-Code (IaC) availability.* Azure Migrate: On-Prem NAS Share Discovery & Assessment (Public Preview) This public preview enables discovery and assessment of on-premises NAS shares (Dell PowerScale, NetApp ONTAP) using the Azure Migrate appliance. This is crucial for organizations looking to modernize their file storage by migrating to Azure Files, Azure NetApp Files, or other Azure storage solutions. From a security perspective, it enables a comprehensive inventory of sensitive data residing on NAS, facilitating a secure migration strategy, identifying potential compliance gaps (e.g., data residency, access controls), and ensuring that security policies are applied consistently post-migration. It helps in planning for data encryption, access management, and network security for migrated data. *Terraform Support: Supported via azurerm_migrate_project (first 3.0+, latest 4.0+). Provider Documentation Azure Storage Actions: Automatic Propagation, Execution Controls, Case-Sensitive Matching (GA)** This GA release enhances Azure Storage Actions, a serverless framework for executing common data operations on Azure Storage. Automatic propagation of task definition updates ensures consistency, while execution controls offer granular management over task runs. Case-sensitive matching improves precision in targeting specific blobs or containers. From a security and compliance perspective, these features enable more robust data lifecycle management, ensuring that security policies (e.g., immutability, encryption, access tiering for sensitive data) are consistently and automatically applied across storage accounts. This helps in maintaining compliance with data retention policies, minimizing data exposure risks by automating cleanup, and enforcing data governance at scale. *Terraform Support: Supported via azurerm_storage_account (first 3.80.0, latest 4.0.0). Provider Documentation Microsoft Defender for IoT: Retirement of OT Security Component** This is a significant announcement regarding the *retirement* of the operational technology (OT) security component of Microsoft Defender for IoT by October 2029. This means organizations relying on this specific capability for monitoring and securing their OT environments will need to plan a transition. From a security and DevSecOps perspective, this requires immediate attention for risk assessment, identifying alternative solutions (e.g., third-party OT security platforms, or leveraging other Defender capabilities if applicable), and developing migration strategies. It's crucial to ensure continuous security monitoring and protection for critical OT infrastructure during and after this transition to avoid security gaps and maintain compliance. *Terraform Support: Supported for the broader service via azurerm_iot_security_solution (first 2.1.0, latest 3.99.0). Provider Documentation Azure Database for PostgreSQL Flexible Server: Private Endpoint Capable Network Configuration (GA)** This GA update signifies a shift from virtual network integration to a private endpoint capable network configuration for Azure Database for PostgreSQL Flexible Server. This is a critical security enhancement. Private Endpoints provide a private IP address for the database within your virtual network, effectively bringing the Azure service into your private network. This eliminates exposure to the public internet, significantly reducing the attack surface. It ensures that all traffic to the database traverses the Azure backbone network privately, enhancing data confidentiality and integrity. For compliance, this helps meet requirements for private connectivity and data isolation, which are often mandated in regulated industries. *Terraform Support: Supported via azurerm_postgresql_flexible_server (first 3.80.0, latest 4.0.0). Provider Documentation Azure Fluid Relay: Upcoming Retirement** This announcement details the upcoming *retirement* of the Azure Fluid Relay service by February 2, 2027. This is a deprecation, not a new feature. Organizations utilizing this service for real-time collaborative experiences must plan for migration to alternative solutions or direct use of the open-source Fluid Framework. From a DevSecOps perspective, this requires a clear deprecation strategy, identifying all dependent applications, assessing alternative technologies, and planning a secure transition. It's vital to ensure that any data stored or processed by Fluid Relay is securely migrated and that new solutions adhere to existing security and compliance policies. *Terraform Support: Supported for the service via azurerm_fluid_relay_server (first 2.99.0, latest 3.99.0). Provider Documentation Azure Service Bus: Geo-Replication on Partitioned Namespaces for Premium (GA)** This GA update introduces Geo-Replication for partitioned namespaces in Azure Service Bus Premium. Geo-replication provides disaster recovery capabilities by replicating metadata and messages across different Azure regions. For security and compliance, this is a significant enhancement for business continuity and disaster recovery (BCDR) strategies. It ensures high availability and resilience for critical messaging infrastructure, minimizing data loss and downtime in the event of a regional outage. This helps meet stringent RPO/RTO requirements and compliance mandates for data durability and availability, especially for mission-critical applications. *Terraform Support: Supported via azurerm_servicebus_namespace (first 3.0+, latest 4.0+). Provider Documentation Azure Site Recovery: Support for Azure Local (GA)** This update announces the General Availability of Azure Site Recovery (ASR) support for Azure Local environments. This means customers can now use ASR to protect Windows and Linux virtual machines deployed within Azure Local, providing a robust and simplified disaster recovery solution. From a security and compliance standpoint, this extends critical BCDR capabilities to edge or on-premises Azure deployments, ensuring data resilience and application availability even in localized outages. It allows organizations to maintain consistent disaster recovery policies and automation across their hybrid cloud estate, simplifying compliance audits and reducing operational overhead for DR planning and execution. *Terraform Support: Supported via azurerm_recovery_services_vault (first 2.0.0, latest 3.90.0). Provider Documentation Azure SQL Database: Portal-based Restart/Failover Operations** This update introduces the ability for users to perform restart or failover operations on Azure SQL Databases directly through the Azure portal. This functionality covers various database types, including standalone single databases, Hyperscale databases, and databases configured within elastic pools. While primarily an operational convenience, this has indirect security and DevSecOps implications. It simplifies incident response and recovery procedures, allowing authorized personnel to quickly initiate failovers or restarts in response to performance issues or potential security incidents, thus minimizing downtime and impact. From a DevSecOps perspective, it provides a more accessible and standardized operational control, potentially reducing reliance on custom scripts or API calls, which can sometimes introduce configuration drift or security vulnerabilities if not properly managed. However, it's crucial to ensure proper RBAC is in place to restrict who can perform these critical operations. *Terraform Support: Not directly supported for this operational feature. The underlying azurerm_sql_database resource is available (first N/A, latest N/A). Provider Documentation*}