> 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-review/section-connections/integrations/connecting-a-destination/microsoft-ads.md). # Microsoft Ads Microsoft Ads is a beta destination available on request. > **Beta** — opened on request. Contact to request access. Microsoft Ads is a beta destination. It won't appear in your destination picker until support enables it for your organization. Once enabled, you connect your Microsoft Ads account and sync a Ready audience to it like any other destination. * **Minimum audience size:** 300 records. ## Accept the Customer List terms in Microsoft Microsoft requires you to accept its **Customer List terms of service** before it will accept an uploaded list. If a sync fails because those terms haven't been accepted, sign in to Microsoft Advertising, accept the Customer List / Customer Match terms for your account, then rerun the sync from Primer. ## Customer Lists take up to 48 hours to build After a successful sync, Microsoft takes **up to 48 hours** to build the Customer List and report its matched size. Until then the list shows no size — that's expected, not a failure. Check back after Microsoft finishes building it; see Finding your synced audience for where the list appears. --- # 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-review/section-connections/integrations/connecting-a-destination/microsoft-ads.md?ask=&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.