Period: today · Items: 5 · Source: Azure official updates RSS
Today is interesting to look at as “a day when operational automation and security capabilities are evolving together.” With Azure Automation now generally supporting PowerShell 7.6 runbooks, the barrier to modernizing scripts has been lowered, and with symmetric keys entering preview in Azure Key Vault Premium, the set of options for key management architectures has expanded. On top of that, features like support for SMB Oplocks settings in Azure NetApp Files are immediately useful for infrastructure performance and file workload tuning, so today offers a rich set of very practical learning opportunities.
· PowerShell 7.6 Runtime Environment — The concept of moving the execution environment for automation runbooks to the latest supported version to secure script compatibility and operational longevity
· Symmetric keys in Key Vault Premium — An update that helps clarify why HSM-based symmetric key (AES) management matters and how its use cases differ from asymmetric keys
· SMB Opportunistic Locking (Oplocks) — A learning point for understanding how client caching and locking behavior affect file share performance optimization
· Regional availability — What new region expansion for Azure Database for PostgreSQL flexible server means for latency, data governance, and DR design
· Reservations vs Savings Plans — A perspective for understanding the differences between commitment models in Azure cost optimization and anticipating future operational policy changes
2 items
· Azure Automation now generally supports PowerShell 7.6 runbooks and the Runtime Environment.
· This announcement helps teams naturally upgrade older scripts to a supported runtime version.
· The announcement also mentions Azure CLI command support, broadening how automation tasks can be expressed.
· The move toward separately managing the “runtime environment” can be read as a step beyond simply running scripts, toward explicitly managing the automation execution foundation itself.
What it is: This is an update that modernizes the PowerShell version and runtime environment in which Azure Automation runbooks execute. The key point is not just that “old scripts still run,” but that teams can move to an execution foundation with lower end-of-support risk.
Why it matters: Many teams still rely heavily on PowerShell for operational automation. So a runtime upgrade is not just a feature addition; it is much closer to improving the maintainability and security responsiveness of automation assets.
Try it: In your Azure Automation account, review the runtime environment settings for a new or existing runbook, then create one simple test runbook based on PowerShell 7.6 and run a basic Azure resource query task.
Source: https://azure.microsoft.com/updates?id=568102
· Microsoft has announced that starting February 1, 2027, Reservation exchange will no longer be available for services covered by Savings Plans.
· As of the time of the announcement, this includes compute-related services.
· Rather than a new feature announcement, this is more of an operations/FinOps change that requires Azure cost optimization strategies to be revisited.
· Even if the immediate impact is limited, it is worth understanding in advance for teams designing long-term commitment purchasing policies.
What it is: This is an announcement of a policy change affecting reservation exchange for certain service groups within Azure’s cost optimization model, where Reservations and Savings Plans coexist. In other words, it changes the rules around “how a commitment purchase can later be changed or exchanged.”
Why it matters: Engineers now need to understand cost structures to make more accurate architecture decisions. Especially if you operate VM- or compute-centric workloads, this is a good example of how technical design and purchasing strategy are no longer separate concerns.
Try it: Review how Reservations and Savings Plans are currently applied to compute workloads such as Azure Virtual Machines in your team, and classify which workloads are long-term fixed versus variable.
Source: https://azure.microsoft.com/updates?id=568514
1 item
· Symmetric keys are now available in public preview in Azure Key Vault Premium.
· The announcement mentions support for the oct-HSM key type and AES (Advanced Encryption Standard).
· This means scenarios that require HSM-backed symmetric key handling can now be evaluated in Azure Key Vault Premium.
· It is a useful update for learning the differences in use cases by key type, moving one step beyond a traditional focus on certificates, secrets, and asymmetric keys.
What it is: This is an enhancement that extends Azure Key Vault Premium so it can manage HSM-backed keys for symmetric encryption. If previous Key Vault learning was focused mainly on secrets or RSA/EC keys, the scope can now be expanded to include AES-based symmetric key management.
Why it matters: When designing a security architecture, “what keys are managed, where, and how” is critically important. In environments with performance, regulatory, or HSM requirements, support for symmetric keys can significantly change the available design options.
Try it: Start by organizing the differences between symmetric and asymmetric keys based on the Azure Key Vault Premium documentation, then review the preview support scope and the key types you can create in a test Key Vault Premium instance.
Source: https://azure.microsoft.com/updates?id=566746
1 item
· Public preview is now available for Oplocks configuration on SMB and dual-protocol volumes in Azure NetApp Files.
· Oplocks (Opportunistic Locks) improve SMB client caching performance and are enabled by default.
· The update notes that settings can now be changed not only when creating new volumes, but also for existing volumes.
· This is an option worth watching for teams handling file server migrations, legacy applications, or high-performance SMB workloads.
What it is: This is a feature that enables configuration of Oplocks, a core element of SMB locking and caching behavior, in Azure NetApp Files. Depending on file access patterns, it can improve performance, while for certain applications its behavior characteristics may need to be tuned carefully.
Why it matters: Cloud file storage becomes much more interesting when it moves beyond “just a shared folder” into the realm of protocol tuning. Especially in SMB-based enterprise application migrations, these detailed options can become the key to avoiding issues or improving performance.
Try it: If you use Azure NetApp Files, check the Oplocks-related options in the SMB volume settings and document the default behavior and any scenarios where tuning may be needed for your test workloads.
Source: https://azure.microsoft.com/updates?id=568396
1 item
· Azure Database for PostgreSQL flexible server is now generally available in the India South Central region.
· You can now deploy a managed PostgreSQL database directly in that region.
· Region expansion means more than simply “more places to deploy”; it has real significance for latency, data residency, and regulatory response.
· This is a very practical update for teams operating global services or designing region-specific architectures.
What it is: This update expands the supported regions for Azure Database for PostgreSQL flexible server to include India South Central. PostgreSQL flexible server is a managed PostgreSQL service that reduces operational burden while still providing flexible configuration options.
Why it matters: Databases are often more heavily affected by regional strategy than applications are. Knowing which regions are now available affects thinking around network latency, user experience, disaster recovery topology, and even data sovereignty.
Try it: Open the PostgreSQL flexible server creation screen in the Azure portal, confirm India South Central in the list of supported regions, and compare it with your current primary region and DR region strategy.
Source: https://azure.microsoft.com/updates?id=568334
Based on today’s input list, there are no separate service retirement announcements.