> 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/additional-resources/faqs/what-is-mca-policy-enforcement.md).

# What is MCA policy enforcement?

Starting 7 October 2025, Microsoft is implementing a policy requiring customers to review and accept the latest version of the Microsoft Customer Agreement (MCA).&#x20;

This acceptance is necessary for customers whose CSP partners attested to the MCA on their behalf before 1 April 2023.

While existing online services remain uninterrupted, customers who don't accept the updated MCA cannot make new purchases, modify license quantities, or change their billing plan. To learn more about this update, see the official [Microsoft announcement](https://learn.microsoft.com/en-us/partner-center/announcements/2025-august#action-required-microsoft-customer-agreement-reacceptance).

### Complying with Microsoft’s updated MCA policy

To comply with this Microsoft policy, Marketplace automatically processes MCA acceptance when the order is placed. The method depends on the tenant type and the individual who is placing the order.

**For self-consumption tenants**

* **Client-placed orders** – If you are a SoftwareOne client placing an order directly, the MCA is automatically accepted using the details of the individual who placed the order. This applies to both new purchases and change orders.
* **Orders placed by SoftwareOne associates**
  * **Purchase orders** – The MCA is signed automatically using the Primary Contact details provided at the time of placing the order.
  * **Change orders** – You must accept the updated MCA via [Microsoft 365 Admin Center](https://admin.microsoft.com/AdminPortal/Home?ref=/BillingAccounts/agreement), using Global Administrator credentials.&#x20;

**For resale tenants**

* **Purchase orders** – The MCA is automatically signed using the Primary Contact details provided when the order was placed.&#x20;
* **Change orders** – Your end customer must accept the updated MCA through the [Microsoft 365 Admin Center](https://admin.microsoft.com/AdminPortal/Home?ref=/BillingAccounts/agreement), using Global Administrator credentials.&#x20;

Orders requiring MCA acceptance remain querying until the latest version of the MCA is accepted.

### Accepting the revised MCA

To accept the revised 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. Review and accept the updated MCA.

For specific steps, see [Review and accept the MCA](/extensions/microsoft-cloud-solution-provider/products-and-programs/microsoft-customer-agreement-mca.md#review-and-accept-the-mca). After accepting, your Marketplace order automatically moves from **Querying** to **Processing**.

If you need assistance with your order, [contact support](/help-and-support/contact-support.md). For legal inquiries, including questions about MCA terms, consult your legal team or Microsoft directly.


---

# 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/additional-resources/faqs/what-is-mca-policy-enforcement.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.
