Connect Microsoft and Bing Ads to Claude

Prepare the Microsoft account and environment

For local use, you need a Microsoft Advertising developer token and an Entra app configured as a public or native client with the local redirect URI http://localhost. The local PKCE sign-in does not require a client secret. Your Microsoft identity must have accepted access to the advertiser or manager account.

Choose sandbox or production in the connection wizard. These environments use separate credentials and advertisers. Tenant policy may require administrator consent. Microsoft documents developer tokens and user authorization in its API getting-started guide. Do not interpret an identity sign-in as permission to inspect every advertiser managed by that identity.

Connect Bing Ads through the Microsoft provider

The open-source setup uses the same provider command for Microsoft Advertising and Bing Ads:

npm install -g adport
adport connect microsoft
adport doctor
adport accounts --provider microsoft

claude mcp add --transport stdio adport -- adport mcp

The wizard opens Microsoft sign-in and stores the resulting grant. Match the returned account ID to the intended advertiser before opening a broad campaign review in Claude Code. Use /mcp to inspect whether Adport is connected.

For Cloud, connect Microsoft in the chosen project where available, save the intended accounts, enable agent access, and register the hosted server:

claude mcp add --transport http --scope user adport https://app.adport.dev/mcp

Complete Adport authorization for that project. The shared Claude Code setup guide explains connection scope. Use separate, clearly named connections when reviewing different client projects.

Request a report and allow for asynchronous generation

Microsoft reports are generated asynchronously. Adport submits the report, waits for readiness, and reads the result. If generation is still pending or fails, ask Claude to report that state rather than substituting cached assumptions or treating missing rows as zero performance.

Check one known campaign against the platform report with the same dates and account. If a report does not contain conversion value, it cannot support a trustworthy ROAS comparison. Keep unavailable fields visibly unavailable.

Compare Microsoft and Google without losing context

A shared report shape makes it easier to inspect both search platforms, but it does not make the attribution settings identical. Compare equal periods, preserve currency, and record what each provider counts as a conversion. Avoid combining spend from different currencies into a single total.

Ask Claude to compare each platform's campaign mix and measurement before suggesting reallocation. A lower reported CPA may reflect different conversion actions or delayed reporting. The next useful task can be reconciling those definitions rather than immediately moving budget. Use the Google Ads and Claude guide for the other half of the setup.

Inspect shared budgets before requesting an adjustment

Read the campaign and current budget arrangement before asking for a change. The Microsoft connector rejects its ordinary campaign budget update when the campaign uses a shared budget. That prevents a campaign-level request from silently affecting a different shared-budget scope.

For a supported change, specify the exact account, campaign, and requested daily amount. Ask Claude to show a preview with the current value, proposed value, currency, and budget effect. Applying requires the matching pending operation and unchanged arguments. An approved preview still needs the provider to accept the operation.

Read back the campaign after applying. Record the reason and a follow-up period that fits the account's conversion delay. Immediate provider verification proves the setting changed, not that efficiency improved.

Troubleshoot the connection before judging the account

If no accounts appear, check the Microsoft identity, accepted account access, developer token, and selected environment. If a report fails after discovery, examine the provider error and reporting permissions. Cloud users should also check the saved account selection and agent-access switches in the authorized project.

The Microsoft Ads MCP integration page lists prerequisites and supported operations. For an existing campaign, a read-only delivery review is a useful first task. Request a campaign change only once the account, report period, and decision are clear enough to review.