> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/primer-support-legacy/troubleshooting-connections/other/error-microsoft-customer-list-terms-and-conditions-not-accepted.md).

# Error: Microsoft "Customer List Terms And Conditions Not Accepted"

The error **"CustomerListTermsAndConditionsNotAccepted"** occurs when the **Customer Match Terms and Conditions** for using customer lists in Microsoft Advertising have not been accepted. To resolve this issue, follow these steps:

#### Steps to Resolve:

* **Log in** to the [Microsoft Advertising web application](https://ads.microsoft.com/).
* **Create a customer list audience** (this audience does not need to contain any data).
* When prompted, select **"I ACCEPT"** to agree to the Customer Match Terms and Conditions.

#### Important Note:

The **Customer Match Terms and Conditions** must be accepted within the Microsoft Advertising UI. This step is mandatory before creating or managing customer list data via the **Campaign Management API**.

For additional assistance, visit the [Microsoft Advertising support page](https://ads.microsoft.com/support) or contact their support team.


---

# 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://support.sayprimer.com/primer/primer-support-legacy/troubleshooting-connections/other/error-microsoft-customer-list-terms-and-conditions-not-accepted.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.