Period: last 7 days · Items: 6 · Source: Azure official updates RSS
Today’s Azure updates show two very clear themes. One is a OneLake-centered data architecture that reads and writes directly without moving data, and the other is Copilot/VS Code experiences that improve large-scale modernization and developer productivity. Add network diagnostics (ICMP on NAT Gateway) and log cost/performance optimization (Summary Rules), and it’s a day full of features that are immediately useful in real-world operations.
· Zero-copy analytics — A pattern for analyzing data directly from a shared storage layer without duplicating it.
· OneLake + Unity Catalog — A look at how Databricks governance and the Microsoft Fabric data layer come together.
· Application modernization at scale — A flow that connects Azure Migrate portfolio assessments with GitHub Copilot-based code analysis.
· Outbound ICMP on NAT Gateway — A chance to understand what simple but powerful network diagnostics like ping mean for architectural operability.
· Log summarization — An operational pattern that optimizes performance, cost, and reporting with summary tables instead of only accumulating raw logs.
3 items
· Azure Databricks now supports native read access to data stored in Microsoft OneLake through Unity Catalog.
· You can query and analyze data directly without copying or moving it to another storage location.
· This helps reduce data duplication and shorten the time to start analytics.
· For organizations using both Databricks and OneLake, this points toward a simpler data layer.
What it is: A capability that allows Azure Databricks to treat OneLake not as a separate external replication target, but as a data source it can read directly. The key idea is zero-copy analytics, where you no longer need to load data into multiple storage systems as before.
Why it matters: From an engineering perspective, this creates a practical option for the question, “Can we keep one storage layer even if we use multiple analytics platforms?” In particular, it can lead to design approaches that reduce data silos, replication costs, and duplicated governance.
Try it: Follow the documentation for integrating OneLake with Azure Databricks/Unity Catalog, and start by mapping out the architecture diagram for how data access works without replication.
Source: https://azure.microsoft.com/updates?id=565733
· This time, beyond reading, Azure Databricks can natively store managed Delta tables in OneLake.
· You can use OneLake as a unified storage layer without directly managing a separate storage account.
· This moves toward a simpler storage design for Databricks workloads.
· It suggests a model where OneLake is used not just for access, but as an actual operational data lake layer.
What it is: A preview feature that allows Azure Databricks to write managed Delta tables directly to OneLake. In other words, the connection between the Databricks compute engine and the OneLake storage layer has become deeper.
Why it matters: In data platform design, combinations like “Databricks for compute, OneLake for storage” become realistic options. If your team uses both Fabric and Databricks, this is a good time to reassess storage duplication and operational complexity.
Try it: Review where managed Delta tables are currently stored in your Databricks workloads, and compare in a table what operational aspects would change if you moved to OneLake-based storage.
Source: https://azure.microsoft.com/updates?id=565706
· The new Azure Portal experience for Log Analytics Summary Rules is now GA.
· You can periodically aggregate high-volume logs and store them in summary tables.
· The focus is on better query performance, optimized reporting, and more efficient data usage.
· It helps shift operations away from only “retaining raw logs as-is for a long time” toward aggregation-centered operations.
What it is: Summary Rules are a feature for periodically aggregating large volumes of logs and storing them in separate summarized tables. This GA update is primarily an experience improvement that makes the feature easier to configure and operate in the Azure Portal.
Why it matters: In observability, there comes a point where how you store data and how you query it matters more than simply collecting it. As operational log volume grows, teams need practical ways to manage both cost and performance, and this feature addresses exactly that.
Try it: In your Log Analytics workspace, choose one high-frequency log source and first design which aggregation dimensions—such as time, resource, or status code—would be most useful for dashboards and reports.
Source: https://azure.microsoft.com/updates?id=562027
2 items
· Azure Migrate now integrates with GitHub Copilot Modernization to support large-scale code assessments.
· It combines Azure Migrate’s portfolio-level discovery/assessment with Copilot’s context-aware code analysis.
· The focus is on making application-by-application analysis more systematic for organizations with many modernization targets.
· The flow of “inventory → assessment → code insights” stands out here.
What it is: A preview that connects Azure Migrate’s large-scale asset assessment data with GitHub Copilot Modernization’s code analysis capabilities in application modernization projects. It goes beyond simple infrastructure discovery and extends into actual code-level modernization decisions.
Why it matters: Modernization usually does not stop at “moving a few servers”; it ultimately gets into code, frameworks, and dependencies. This feature has the potential to reduce the gap between infrastructure teams and development teams, enabling faster portfolio-scale decision-making.
Try it: Based on the list of legacy applications currently known in your organization or personal environment, create your own three-step checklist for Discovery → Assessment → Code insights.
Source: https://azure.microsoft.com/updates?id=566145
· A new preview Create New Project experience has been added to the Azure Functions extension for VS Code.
· Instead of the previous multi-step Quick Pick flow, it now uses a visual template gallery.
· You can search and filter templates, lowering the barrier to starting a project.
· For learners, it makes the Functions app creation flow easier and more intuitive to understand.
What it is: An update that refreshes the Azure Functions project creation UX inside VS Code. The core change is not the feature set itself, but that it is now much easier to explore which template to use when starting a serverless app.
Why it matters: In serverless development, the speed of “just building one to try it” matters. Especially for beginners or engineers who want to compare multiple languages and triggers, template discoverability directly improves learning productivity.
Try it: After updating the Azure Functions extension in VS Code, compare and capture how language and trigger templates are categorized in the new project creation screen.
Source: https://azure.microsoft.com/updates?id=562497
1 item
· Azure Standard V2 NAT Gateway now supports Outbound ICMP Echo Request/Reply.
· Workloads behind the NAT Gateway can now perform ping-based connectivity checks.
· This makes basic network troubleshooting and connectivity validation easier.
· It may look like a small change, but it is a very welcome update from an operational convenience perspective.
What it is: A GA capability that enables ICMP echo traffic in Standard V2 NAT Gateway environments. In other words, one of the most familiar tools for quickly validating outbound paths is now officially supported.
Why it matters: When dealing with network issues, teams often start with simple connectivity checks before looking at complex logs. In real operations, whether these “fundamental tools” are available can significantly change operational difficulty.
Try it: If you have a test subnet using NAT Gateway, write down operational scenarios where ICMP-based checks are faster than your existing diagnostic methods.
Source: https://azure.microsoft.com/updates?id=565487
There are no separate (Retirement) items in this input list.
read and write paths differ in an Azure Databricks and Microsoft OneLake combination, using Unity Catalog as the reference point