Included as Microsoft's paid-search and audience-media operations surface, with first-party services for manager and advertiser accounts, campaign management, high-volume bulk transfer, conversion configuration, and asynchronous reporting.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Customers or manager accounts, advertiser accounts, users and customer roles, client links, campaigns, ad groups, ads, keywords, budgets, audiences, UET tags, conversion goals, ad extensions, merchant and product-ad entities, bulk files and jobs, and report requests and files.
Read customers, linked accounts, effective user roles, campaign hierarchy, budgets, ads, keywords, audiences, UET and conversion configuration, recommendations, and performance data; download high-volume entity snapshots through Bulk and submit then poll asynchronous Reporting jobs.
Create or update supported campaigns, ad groups, ads, keywords, budgets, audiences, UET tags, conversion goals, and extensions through Campaign Management or Bulk; manage selected customer links, invitations, accounts, or billing objects only when the authenticated role and service operation allow it; submit report-generation jobs.
Use a Microsoft OAuth or Google OAuth 2.0 access token in AuthenticationToken plus a Microsoft Advertising DeveloperToken on every API request; include CustomerId and AccountId where the operation requires them. The access token represents the user's account permissions, and the developer token does not grant additional account access.
Resolve and log the effective customer, advertiser account, user role, client-link path, and CustomerId or AccountId for every action. Separate campaign mutations from billing, user, and customer-link administration, and retain Bulk job results and change history for partial or high-volume writes.
New Microsoft Advertising API features move to REST on 2026-10-01 and SOAP is scheduled for full deprecation on 2027-01-31. Service operations and entities have their own request and hierarchy limits, which may vary by account. Reporting is asynchronous and a report request ID expires after one day. Roles and client-link permissions can restrict writes even when the same identity can reach multiple customers.
First-party access
Agent access
Support: No official MCP server located
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: The first-party surface defines AuthenticationToken and DeveloperToken headers but does not establish an MCP authentication scheme. A customer-built adapter would carry a user token from Microsoft OAuth or Google OAuth together with a developer token and the required customer or account identifiers.
Approval boundary: Confirm the target customer and account before campaign, budget, audience, UET, conversion, or Bulk writes. Treat user invitations, client links, billing, and account administration as separate privileged approvals, not campaign-management actions.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Microsoft ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
First-party API reference or API overview recorded for this platform.
Targeted first-party core-access review
Current overview documents REST migration from 2026-10-01 and scheduled SOAP deprecation on 2027-01-31.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Microsoft OAuth or Google OAuth 2.0 may supply the access token; a Microsoft Advertising developer token remains required.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
