> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/extensions/microsoft-cloud-solution-provider/products-and-programs/microsoft-customer-agreement-mca.md).

# Microsoft Customer Agreement (MCA)

The Microsoft Customer Agreement (MCA) is Microsoft's contract for purchasing and using cloud services. It defines the terms and conditions that govern Microsoft cloud subscriptions and services.

### MCA acceptance requirements

Customers purchasing Microsoft cloud services through the Cloud Solution Provider (CSP) program must accept the MCA before subscriptions or services can be provisioned. &#x20;

This requirement applies to:

* Organizations purchasing Microsoft cloud services, such as Azure, Microsoft 365, Dynamics 365, and more, for the first time through a CSP partner must also accept the MCA.
* Existing CSP customers who haven't previously accepted the MCA must also accept it.&#x20;
* Customers whose CSP partner accepted the MCA on their behalf before 1 April 2023 and who are required to reaccept the agreement under Microsoft's updated requirements.

### MCA validation in Marketplace Platform

Marketplace Platform automatically checks whether the MCA has been accepted when processing orders.

* If the MCA has been accepted, order processing continues.
* If acceptance is required, the order enters a **Querying** status, and processing is paused until the MCA is reviewed and accepted.

### Review and accept the MCA

To review and accept the MCA:

1. Sign in to the [Microsoft 365 Admin Center](https://admin.microsoft.com/AdminPortal/Home?ref=/BillingAccounts/agreement) using your Global Administrator credentials.
2. Navigate to **Billing** or **Account**.
3. Read the terms and conditions of the agreement.
4. Select the checkbox to confirm that you have read and accept the terms and conditions.
5. Select **Accept**.&#x20;

<div data-with-frame="true"><figure><img src="https://1674205915-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ5DNbniz33mXCZoO62Rm%2Fuploads%2FYXfNNMyXWNLvLHrknwGd%2Fimage.png?alt=media&amp;token=4c05c35e-eaa9-43d1-995b-a1073233d471" alt=""><figcaption><p>Accept the Microsoft Customer Agreement in the Microsoft 365 Admin Center.</p></figcaption></figure></div>

### Resume order processing

After you accept the MCA and Microsoft confirms your acceptance, your Marketplace order automatically changes from **Querying** to **Processing**.

If the order doesn't automatically change to Processing after accepting the MCA, select **Process** on the order details page to update the status manually. For details, see [Change status from Querying to Processing](/modules-and-features/marketplace/orders/set-an-order-to-processing.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform.softwareone.com/extensions/microsoft-cloud-solution-provider/products-and-programs/microsoft-customer-agreement-mca.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
