Oracle MOSA vs MCA. The contract vehicles compared.

Oracle MOSA and MCA are two master agreements that govern different halves of the estate, on premises licensing under MOSA and cloud services under MCA, and most enterprises hold both at once.

This guide is for legal and procurement leaders untangling Oracle agreements in 2026. Read it with the cloud licensing policy guide and the Oracle Practice page so the contract structure and the licensing rules line up.

What are the Oracle MOSA and MCA master agreements?

Oracle places enterprise buying under master agreements that set standing terms. Two masters cover most estates, one for on premises licensing and one for cloud. Oracle publishes both in its contracts library.

What does the Oracle MOSA govern?

The Master Oracle Software and Hardware Agreement governs on premises programs, hardware, and support. Every traditional license order sits beneath it as an ordering document.

• Licenses: perpetual and term programs deployed on premises.
• Hardware: engineered systems and servers.
• Support: the technical support tied to those licenses, set by Oracle support policies.

What does the Oracle MCA govern?

The Master Cloud Agreement governs Oracle cloud services. Its terms cover consumption metrics, service levels, and data handling that the on premises master never addresses. Oracle posts the cloud terms under its cloud services contracts page, alongside the wider OCI service catalog.

How do Oracle MOSA and MCA differ in practice?

The split is by estate, not by vendor. What you are buying decides which master applies, and many deals touch both at once.

Why do most enterprises hold both agreements?

Because most run both estates. On premises database and middleware sit under MOSA while OCI and Fusion SaaS sit under MCA, so a single enterprise carries orders under each master.

What happens in a combined cloud and license renewal?

A bundled deal splits. The license lines fall under MOSA and the cloud lines under MCA, so read both masters before signing a combined renewal or you inherit terms you never reviewed.

How do you negotiate Oracle master agreement terms?

The master is where leverage is highest, because it governs years of future orders. The standing terms are negotiable for enterprise buyers, and the time to move them is before volume accrues.

Which master terms matter most to a buyer?

Audit, assignment, and termination language matter most. They decide exposure long after the signing meeting, so settle them at the master, not at the order.

• Audit: notice period, scope, and how findings convert to a bill.
• Assignment: whether licenses move on a merger or divestiture.
• Termination: what survives, and on what notice.

How do audit rights differ between MOSA and MCA?

The MOSA carries the classic on premises audit clause that reviews deployment against entitlements. The MCA leans on consumption telemetry Oracle already meters, so cloud risk is about commitment sizing and unauthorized environments, not seat counts.

What mistakes do buyers make with Oracle MOSA and MCA?

The recurring errors are structural, not technical. They show up at renewal and at audit, long after the master was signed without scrutiny.

• Skipping the master: negotiating the order and ignoring the terms above it.
• Splitting renewals wrong: letting cloud lines drift under MOSA terms or licenses under MCA terms.
• No register: holding masters and orders with no single map of which governs what.

Where the common advice on Oracle master agreements is wrong

The standard Oracle account team line is that the master is boilerplate and the order is where the deal lives. We disagree. In roughly 30 of the 45 Oracle estates Fredrik Filipsson benchmarked between 2023 and 2025, the costly exposure traced back to unread master terms, not to the order pricing. Audit scope, assignment on a merger, and cloud forfeiture all live in the master and govern every order beneath it for years. The buyer side move is to treat the master as the negotiation and the order as the receipt, and to settle audit and assignment language before the first order is ever placed.

45+

Oracle master structures reviewed

2 of 3

Estates hold both masters

1 in 3

Combined renewals split wrong

Source: Redress Compliance advisory engagement file, 2024 to 2025.

Buyers negotiate the order and skip the master that governs it, yet the master sets the audit, assignment, and termination defaults for years of orders.

What to do next

1. Identify which master governs each Oracle agreement you hold.
2. Map every order document to its parent master.
3. Read the audit and assignment terms in each master.
4. Split any combined renewal into its MOSA and MCA lines.
5. Negotiate standing terms before the next order, not after.
6. Keep a single register of masters, orders, and terms.
7. Set a 60 day lead time before any master signature.

Frequently asked questions

What is the difference between Oracle MOSA and MCA?

MOSA governs on premises Oracle software, hardware, and support, while the MCA governs Oracle cloud services such as OCI and SaaS. They cover different halves of the estate, so most enterprises that run both hold both masters at once.

What does the Oracle MOSA cover?

The Master Oracle Software and Hardware Agreement covers perpetual and term licenses for on premises programs, engineered hardware, and the technical support tied to them. Every traditional license order sits beneath it as an ordering document.

What does the Oracle MCA cover?

The Master Cloud Agreement covers Oracle cloud services, including OCI consumption and Fusion SaaS subscriptions. Its terms address service levels, data handling, and consumption metrics that the on premises MOSA never mentions.

Do you need both Oracle MOSA and MCA?

If you run both on premises Oracle and Oracle cloud, you typically hold both masters. The agreement that applies depends on what you are buying, so a single enterprise often carries ordering documents under each at the same time.

Which Oracle agreement governs a cloud commitment?

The MCA governs Oracle cloud commitments, including Universal Credits. When a renewal bundles cloud with on premises licensing, the cloud lines fall under the MCA and the license lines under the MOSA, so read both before signing.

Can you negotiate Oracle master agreement terms?

Yes. Both masters contain terms that are negotiable for enterprise buyers, including audit, assignment, and termination language. The master sets the defaults for every future order, so negotiate it before the first order, not after.

How do audit rights differ between MOSA and MCA?

The MOSA carries the classic on premises audit clause that lets Oracle review deployment against entitlements. The MCA leans on consumption telemetry Oracle already meters, so the cloud audit risk is about commitment sizing and unauthorized environments, not seat counts.

When should a buyer negotiate the Oracle master?

Negotiate the master before the first order beneath it, ideally with 60 days of lead time. Once orders accumulate under a master, the standing terms are far harder to reopen, so the leverage sits at the initial signature.