These Databricks Usage Commit Terms are additional contractual provisions applying to any Order between Databricks and the customer entering into the Order (“Customer” or “you”) which references these Databricks Usage Commit Terms. Please refer to your Order for the definition of any capitalized word or phrase used but not defined in these Databricks Usage Commit Terms. The terms of your Order govern over these Databricks Usage Commit Terms if there is any conflict between such documents.

Overview

The definitions and terms below explain:

• What types of usage commitment may be included in your Order
• How the usage commitment may be satisfied
• What happens if usage exceeds the usage commitment stated in your Order
• What happens if the usage commitment stated in your Order is not satisfied

What are usage commitments in a Databricks Order?

• “Universal Usage Commitment” (also called “UUC”) is the total commitment that you make in your Order for the use of Databricks Platform Services and/or Databricks Powered Services (e.g. Azure Databricks). Your Universal Usage Commitment may be further allocated between Specified Commitment(s), as detailed in your Order.
• “Specified Commitment” means the commitment you make in your Order for the use of a specific value of Databricks Platform Services and/or Databricks Powered Service (e.g. Azure Databricks) on the specific stated platform(s), including one or more of the following, as detailed in your Order:
  • AWS Direct Commit
  • AWS Marketplace Commit
  • GCP Direct Commit
  • GCP Marketplace Commit
  • SAP Commit
  • Azure Commit
  • Flexible Commit - (defined below; Specified Commitments, except for the Flexible Commit, are also referred to as “Original Specified Commitments”)
• If your Order includes a “Flexible Commit”, it means your commitment for the use of an additional stated value of Databricks on any of the platforms for which you have an Original Specified Commitment. A Flexible Commit is a type of Specified Commitment that is incremental to the Original Specified Commitment(s), and can be consumed by usage on any of the Original Specified Commitment platforms. Note that usage on a particular platform will only consume the Flexible Commit after the full consumption of your Original Specified Commitment with respect to such platform.
  
  Example - Assume an Order includes (1) a Specified Commitment value for Databricks on AWS, (2) a Specified Commitment value for Databricks on GCP, and (3) a Flexible Commit value. If the AWS Specified Commitment is fully consumed, additional usage of Databricks on AWS during the Term will then apply to the Flexible Commit (until it is exhausted). A similar calculation applies if/when the usage of Databricks on GCP during the Term exceeds the GCP Specified Commitment. 

How is the usage commitment satisfied?

Your usage commitments are satisfied through consumption by Customer (or End Customer, if applicable) of the full value of each Specified Commitment during your Order’s stated Term, and meeting your related payment/purchase obligations in the Order. How the UUC may be satisfied varies by platform, as described below:

• Platform Services – Databricks on AWS/GCP and SAP Databricks. For these platforms/products, you satisfy your usage commitments through consumption of and payment for the stated Specified Commitment values of such Platform Services during the Term in accordance with your Order.
  • For clarity, only charges attributable to actual usage of SAP Databricks count towards satisfying your Specified Commitment for SAP Databricks. Other fees/usage (such as separately charged compute or other SAP solutions) are not eligible.
• Databricks Powered Services - Azure Databricks. To the extent your Universal Usage Commitment consists of or includes Azure Databricks, you satisfy the UUC through consumption of and payment for the stated Specified Commitment value of Azure Databricks during the Term in accordance with your Order.
  • For clarity, only charges attributable to actual usage of Azure Databricks count towards satisfying your Specified Commitment for Azure Databricks. Other fees/usage (such as separately charged compute or other Microsoft solutions) are not eligible.

What happens if usage exceeds the usage commitment(s) stated in your Order?

• Additional Fees for Burst Usage. The term “Burst Usage” refers to the use of additional Databricks on AWS or Databricks on GCP after the consumption of the Specified Commitment(s) in your Order applicable towards such platform(s). Burst Usage is invoiced monthly in arrears.
  • The use of additional SAP Databricks and Azure Databricks after the consumption of the Specified Commitment(s) in your Order applicable towards such platform(s) will continue to be billed in accordance with the terms of your Order.
• Additional Fees for Support Services. If your Order includes Multicloud Support or Single-Cloud Support, and the fees you owe for such services (based on Support-Eligible Fees and as set forth in your Order) are greater than your scheduled payment(s) for such services, you will be billed monthly in arrears for the difference. “Support-Eligible Fees” means your total fees during the Term for usage pursuant to your Order of Databricks on AWS, Databricks on GCP, and Azure Databricks (as applicable).

What happens if the usage commitment stated in your Order is not satisfied?

You may owe Databricks a “True-up Payment”, i.e. an amount equal to any value of your Universal Usage Commitment which remains unpaid (under the terms of your Order) at the end of your Order’s Term. If you pre-purchase Platform Services or Databricks Powered Services, only the portions of your pre-purchase that are used (or which expire unused) during the Term of the Order count as payment your Specified Commitment.

Last Revised - August 2025