Period: today · Items: 4 · Source: Azure official updates RSS
Today stands out for both serverless runtime updates and stronger default security. Azure Functions expands developer options with Python 3.14 GA and PowerShell 7.6 Preview, while AKS and PostgreSQL clearly reflect a shift toward “looking beyond performance alone to also make encryption in transit and security assessments part of the baseline.” From a practical perspective, it’s a great day to review runtime upgrade strategy, Kubernetes storage security, and database security posture management (CSPM) all at once.
· Python 3.14 on Azure Functions — the key takeaway that even serverless apps require attention to latest language runtime support cycles and security patches
· PowerShell 7.6 on Functions — the idea that infrastructure automation and operational scripts can also be placed on an event-driven execution model with Functions
· Defender CSPM for PostgreSQL Flexible Server — the concept that database security should be managed not just through firewall settings, but through a continuous assessment approach
· Encryption in Transit for Azure Files NFS on AKS — the trend that, even for container storage, encryption matters not only “at rest” but also “in transit”
· Azure File CSI Driver — the point that the CSI driver is the key path for extending functionality when attaching external storage in AKS
2 items
· Azure Functions now generally supports Python 3.14.
· You can develop function apps locally with Python 3.14 and deploy them to Linux-based Azure Functions plans.
· The update emphasizes improved security, a longer support lifecycle, and continued compatibility with Azure Functions as key reasons to upgrade.
· Because falling behind on runtime versions increases security and operational burden even for serverless apps, this update means more than simply adding another version.
What it is: This update brings official support for Python 3.14 in Azure Functions. It allows function apps based on earlier Python versions to move to the latest runtime while aligning with changes in the language ecosystem and Azure’s support lifecycle.
Why it matters: If you run Python-based APIs, event processing, or batch jobs on Functions, you can now plan a more proactive runtime upgrade roadmap. In particular, this is a strong reminder that even in serverless, not only the “code” but also runtime lifecycle management is an important learning point.
Try it: Install Python 3.14 in your local development environment, create a simple HTTP trigger Azure Functions app, and verify whether it can be deployed to a Linux plan.
Source: https://azure.microsoft.com/updates?id=567646
· Azure Functions now supports PowerShell 7.6 in public preview.
· You can develop PowerShell 7.6-based apps locally and deploy them to Azure Functions plans.
· This enables experimentation with a newer PowerShell runtime for operations automation, administrative tasks, and event-driven scripting on Functions.
· The update also recommends reviewing what’s new in PowerShell 7.6 and the Azure Functions PowerShell version documentation as related references.
What it is: This preview announcement adds PowerShell 7.6 to the runtime options for PowerShell-based Azure Functions. It lets you test the latest PowerShell capabilities when building infrastructure operations scripts or management automation on a serverless execution model.
Why it matters: Many teams still rely heavily on PowerShell for operational automation. This update shows that PowerShell continues to evolve beyond being just an “administrative shell” into an event-driven cloud automation runtime.
Try it: Create a sample PowerShell-based Timer trigger Function, run it locally with 7.6, and compare it with your current production scripts to check for compatibility differences.
Source: https://azure.microsoft.com/updates?id=567651
1 item
· CSPM security assessments in Microsoft Defender for Cloud are now generally available for Azure Database for PostgreSQL Flexible Server.
· You can continuously assess the security posture of PostgreSQL Flexible Server environments.
· The key point is an operating model where security state is continuously checked against standards, rather than relying on individuals to manually review each setting.
· The message is strong: the data layer, like infrastructure, must now be treated as something whose “configuration state should be assessed and improved.”
What it is: This capability enables Defender for Cloud to provide security assessments for Azure PostgreSQL Flexible Server. It helps you systematically review security configuration status and manage database resources from a CSPM perspective.
Why it matters: Many engineers tend to think of database security only in terms of network access control, but in real-world operations, continuously measuring security posture is becoming more important. It’s also a good example in Azure security learning that the step after “resource deployment” is “continuous assessment and improvement.”
Try it: In Defender for Cloud, check how security recommendations or assessment items related to PostgreSQL Flexible Server are surfaced, and summarize which improvement points apply to the database resources in your current test subscription.
Source: https://azure.microsoft.com/updates?id=567527
1 item
· Encryption in Transit (EiT) is now generally available for Azure Files NFS v4.1 volumes in AKS.
· This capability is provided through the Azure File CSI driver.
· When EiT is enabled, data in transit between AKS workloads and Azure Files NFS shares is encrypted with TLS.
· In other words, even when using NFS-based shared storage, you can address not only “storage encryption itself” but also protection for the network transmission path.
· This is an especially important option for AKS workloads with high security requirements or in regulated environments.
What it is: This feature allows you to encrypt data in transit when mounting Azure Files NFS storage in AKS. It strengthens network-path protection by another level while keeping the Kubernetes storage consumption model unchanged.
Why it matters: In container environments, teams often focus on app deployment and autoscaling first and only look at storage security later. This feature is a good opportunity to learn both CSI driver-based storage integration and in-transit encryption together.
Try it: If you have a test workload using Azure Files NFS in AKS, follow the documentation for Azure File CSI driver configuration and EiT enablement to see how the configuration options differ.
Source: https://azure.microsoft.com/updates?id=567787
There are no retirement items in today’s list.