Azure Databricks delivers proven business value

Microsoft Azure Databricks delivers the first-party advantage of Databricks on Microsoft—and for customers, that advantage shows up as real, measurable value. It is the same Databricks platform your teams already know, co-engineered with Microsoft and delivered as a native Azure service, so it fits naturally into the Microsoft tools, identity, and governance your organization already runs.

Discover Azure Databricks

The advantage is built-in, not bolted on. Microsoft and Databricks co-engineer the service, share one integration roadmap across the Microsoft data and AI stack, and align go-to-market so you get one motion, one bill, and one support path. For technical teams, that means deeper native integration and stronger performance. For the business, it means lower cost, less risk, and faster time to value.

The strategic partnership drives an accelerated integration roadmap and continuous optimization for improved performance; however, decision-makers constantly ask about what business value all of this translates to. To address this key question, Microsoft commissioned a Forrester Total Economic Impact™ study of Azure Databricks. It found that a composite organization based on interviewed customers realized a three-year 331% return on investment, $58.1 million in net present value, and recovered its investment in less than six months.

331%Return on investment $58.1MNet present value< 6 monthsPayback period

Commissioned study conducted by Forrester Consulting on behalf of Microsoft, June 2026. Results are over three years and represent a composite organization based on interviewed customers and may not be typical; actual results will vary.

What the study found

Forrester interviewed Azure Databricks customers and built a composite organization to model the impact: a $6 billion company in a regulated industry, running about 10 petabytes of data.

Before Azure Databricks, its data estate was fragmented and expensive. It was unreliable at scale and hard to govern. Afterward, the results were clear: $75.6 million in benefits against $17.5 million in cost over three years translating to $58.1 million in net present value.

The value came from four places:

$39.0 million—data and analytics teams’ productivity. Teams handled more work without adding people, with measured gains of 15% to 25%. As a Vice President of data services at a healthcare organization put it: “…we’re doing more work with the same size of the team.”

$19.9 million—lower infrastructure costs. Elastic, pay-as-you-go compute replaced overprovisioned hardware.

$11.4 million—better data platform resiliency. Managed operations meant fewer outages and no custom disaster recovery to build.

$5.4 million—retired legacy software and redeployed DBAs. Consolidating databases and Extract, Load, Transform (ETL) tools eliminated third-party licenses, and managed operations freed database administrators for higher-value work.

Forrester listed more benefits it didn’t put a price on: native Azure services integration, faster insights, wider access to data, and governance through Unity Catalog. That’s where the return starts.

Model your own numbers with the Azure Databricks ROI estimator

Where the value comes from

Those returns come down to one thing. Azure Databricks is a true first-party Azure service, co-engineered by Microsoft and Databricks, it plugs into the tools your teams already use. That removes the extra data copies, tooling, and integration work that raise costs elsewhere.

A great example is the Azure Databricks Genie integration with Microsoft Copilot Cowork. You can add context of your business and build on that intelligence into the tools your teams already use with this integration. Genie lets anyone question the lakehouse in plain language—now inside Microsoft Teams, Microsoft 365 Copilot, and more recently in Copilot Cowork, where it grounds tasks in trusted data through Genie Ontology. Every answer is scoped by Unity Catalog to exactly what each user is permitted to see, so intelligence reaches the flow of work without loosening governance.

The same depth runs across the rest of the platform:

Identity and governance: Automatic Identity Management for Entra ID syncs users into Azure Databricks. Unity Catalog and Microsoft Purview govern the rest. 

Microsoft Power BI and Microsoft 365: Power BI reads your data directly and now writes back to it. A new Excel add-in brings governed data into spreadsheets; a SharePoint connector streams files into Delta tables, and Teams notifications deliver alerts where teams work. Metric views keep business logic consistent across all of them. 

AI and agents: Beyond chatting with your data, Genie connects to Copilot Studio and Microsoft Foundry, and a single Model Context Protocol (MCP) connection lets Copilot Studio and GitHub Copilot agents reason over an entire Azure Databricks workspace. Azure Database Lakebase gives agents a serverless Postgres engine, and serverless workspaces get them started fast. 

Microsoft OneLake: OneLake catalog federation lets Azure Databricks query OneLake data directly, with no pipelines or copies. You can also store Unity Catalog tables in OneLake, alongside Azure Data Lake Storage.

Customer data: CustomerLake, a new Agentic Customer Data platform, builds Customer 360 profiles and runs campaigns inside the lakehouse where the data and governance already live. 

Enterprise systems: SAP Business Data Cloud Connect brings SAP data into the lakehouse. It’s the same model helping industries like industries like telecom turn AI into returns. 

These are the integrations that Forrester valued but didn’t price separately however, they are critical factors driving productivity and cost benefits that were quantified.

Backed by independent benchmarks

Value also depends on speed, and that’s been tested. Principled Technologies, an independent firm, ran an industry-standard, TPC-DS-like decision-support benchmark on a 10-terabyte dataset. Azure Databricks completed a single query stream in up to 21.1% less time than Databricks on AWS (with autoscale disabled) and ran four concurrent query streams more than nine minutes faster.

What it means for you

Choosing a data and AI platform is a long-term decision, and with Azure Databricks the pieces reinforce each other. The integration drives the savings Forrester measured. The performance keeps those gains steady as usage grows. And it all rests on one foundation: a first-party partnership that puts Microsoft and Databricks engineering, roadmap, and support behind your data estate. The value isn’t a claim, it’s been measured: a three-year 331% return, with payback in under six months. It’s why so many teams choose to run their lakehouse on Azure Databricks.

Get started with Azure Databricks

Explore further

The full Forrester TEI study, plus the ROI calculator to model your own numbers.

The Principled Technologies benchmark.

Azure Databricks at Data + AI Summit 2026, and how it uses OneLake as a shared data foundation.

Build AI apps and agents with Azure Databricks, Copilot Studio, and GitHub Copilot.

Stay current on the Azure Databricks Tech Community blog and the official release notes.

Related blog posts: Differentiated synergy and Databricks runs best on Azure.

For the full set of Databricks Data + AI Summit 2026 announcements, see Azure Databricks at Data + AI Summit 2026.

Learn more about Azure Databricks

Build Intelligent Solutions with Azure Databricks

Empower teams to develop AI-powered applications and gain deeper insights with a unified data and AI platform.

Learn More

The post Azure Databricks delivers proven business value appeared first on Microsoft Azure Blog.
Quelle: Azure

Amazon RDS now supports up to four storage modifications in 24 hours

Amazon RDS now allows up to four storage modifications per database instance within a rolling 24-hour window. These modifications let you increase the size, change the type, and adjust the performance of your RDS storage volumes. You can start a new modification right after storage optimization for the previous modification is complete without having to wait for the six-hour cool-off period to complete.
This enhancement improves operational agility for scaling storage capacity or adjusting performance during sudden data growth or unexpected workload spikes. With RDS storage modifications, you can modify your volumes without downtime, keeping applications running with minimal performance impact.
The feature is automatically enabled on all Amazon RDS for PostgreSQL, Amazon RDS for MariaDB, Amazon RDS for MySQL, Amazon RDS for Db2, Amazon RDS for Oracle, and Amazon RDS for Microsoft SQL Server instances in all commercial AWS Regions and the AWS GovCloud (US) Regions. To learn more, refer the Amazon RDS User Guide.
Quelle: aws.amazon.com

Amazon RDS and Aurora now support R8g and M8g database instances in additional AWS Regions

AWS Graviton4-based R8g database instances are now generally available for Amazon Aurora (MySQL and PostgreSQL compatibility) and Amazon RDS for PostgreSQL, MySQL, and MariaDB in Asia Pacific (Hyderabad, Melbourne, Malaysia), Europe (London, Paris, Zurich), AWS GovCloud (US-East), South America (Sao Paulo), and Mexico (Central) regions. Additionally, M8g instances are now supported for Amazon RDS for PostgreSQL, MySQL, and MariaDB in US West (N. California), Asia Pacific (Mumbai, Sydney, Hong Kong, Seoul, Malaysia, Singapore), Canada West (Calgary), Europe (Zurich, Milan, Paris), South America (Sao Paulo) and Africa (Cape Town) regions.  AWS Graviton4-based instances provide up to 40% performance improvement and up to 29% price/performance improvement for on-demand pricing over Graviton3-based instances of equivalent sizes on Amazon Aurora and Amazon RDS databases, depending on database engine, version, and workload. Built on the AWS Nitro System, the new R8g database instances introduce 24xlarge and 48xlarge sizes, delivering up to 192 vCPUs, an 8:1 ratio of memory to vCPU with the latest DDR5 memory, up to 50Gbps enhanced networking bandwidth, and up to 40Gbps of bandwidth to Amazon Elastic Block Store (Amazon EBS). You can easily launch R8g or M8g database instances through the Amazon RDS Management Console or by using the AWS Command Line Interface (CLI). For detailed information about specific engine versions that support these database instance types, please refer to the Aurora and RDS documentation. For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page. 
Quelle: aws.amazon.com

Amazon RDS and Aurora expand R8gd and M8gd to additional Regions

Amazon Relational Database Service (RDS) now supports R8gd database instances in 12 additional regions and and M8gd database instances in 6 additional Regions with Optimized Reads for Amazon Aurora PostgreSQL, RDS for PostgreSQL, RDS for MySQL, and RDS for MariaDB. R8gd and M8gd instances deliver up to 165% better throughput and up to 120% better price-performance over R6g instances for Aurora PostgreSQL. Optimized Reads uses local NVMe-based SSD block storage to store ephemeral data such as temporary tables, reducing network storage access and improving query latency. The result is improved query performance for complex queries and faster index rebuild operations. Aurora PostgreSQL Optimized Reads instances using the I/O-Optimized configuration also use the local storage to extend their caching capacity. Database pages that are evicted from the in-memory buffer cache are cached in local storage to speed subsequent retrieval of that data. Customers can get started with Optimized Reads through the AWS Management Console, CLI, and SDK by modifying their existing Aurora and RDS databases or creating a new database using R8gd or M8gd instances. R8gd instances are available in the following additional regions: Europe (Ireland), Asia Pacific (Seoul), Asia Pacific (Malaysia), Europe (London), US West (N. California), Asia Pacific (Sydney), Canada (Central), Asia Pacific (Jakarta), Africa (Cape Town), Canada West (Calgary), South America (Sao Paulo) and Asia Pacific (Hong Kong). M8gd instances are available in the following additional regions: Europe (Ireland), Asia Pacific (Malaysia), Europe (London), Asia Pacific (Sydney), South America (Sao Paulo) and Canada (Central). For complete information on pricing and regional availability, please refer to the pricing page. For information on specific engine versions that support these DB instance types, please see the Aurora and RDS documentation.
Quelle: aws.amazon.com

Amazon MSK Express Brokers adds support for Apache Kafka version 4.2

Amazon Managed Streaming for Apache Kafka (Amazon MSK) Express Brokers now supports Apache Kafka version 4.2. This release includes Eligible Leader Replicas (ELR) enhancements that strengthen availability with improved leader election correctness. It also introduces a new consumer rebalance protocol that helps ensure smoother and faster group rebalances, and a new Streams Rebalance Protocol that extends broker coordination capabilities to Kafka Streams for optimized task assignments. For a complete list of improvements and bug fixes, please refer to the Apache Kafka release notes for version 4.2. MSK Express Brokers are designed to deliver up to three times more throughput per broker, scale up to 20 times faster, and reduce recovery time by 90 percent. This launch brings the latest open-source reliability and performance improvements to MSK Express. To get started, simply select version 4.2.x when creating a new cluster with Express Brokers via the AWS Management Console, AWS CLI, or AWS SDKs. You can also upgrade existing MSK Express Brokers with an in-place rolling update. Amazon MSK orchestrates broker restarts to maintain availability and protect your data during the upgrade. Kafka version 4.2 support is available today across all AWS regions where Amazon MSK Express Brokers is offered. To learn how to get started, see the Amazon MSK Developer Guide.
Quelle: aws.amazon.com

Amazon MQ now supports configurable storage for RabbitMQ brokers

Amazon MQ now allows you to configure the EBS Disk storage size for RabbitMQ brokers independently of instance type. When creating or updating a broker, you can define a custom storage size, allowing you to right-size storage independently of your instance size to match your specific messaging workload requirements. Configurable storage is available for RabbitMQ M7g brokers on version 4.2 or later using cluster deployments only.
With configurable storage, you can choose a storage size from the default value on M7g to the maximum allowed value depending on your instance size in increments of 5 GB. You can specify the Storage Size using the using the AWS Console, AWS CloudFormation, AWS Command Line Interface (CLI), or the AWS Cloud Development Kit (CDK). Storage changes are applied during the next broker reboot. 
Standard Amazon MQ storage pricing applies based on the disk size as per Amazon MQ pricing. Configurable storage is available in all commercial AWS Regions where Amazon MQ for RabbitMQ is offered. To learn more, see the Amazon MQ Developer Guide.
Quelle: aws.amazon.com