Paused campaign and ad creation on Microsoft Advertising

Microsoft Advertising: Prepare a native campaign, group and ad with read-back validation while keeping delivery paused.

Recipe, Microsoft Advertising

Intent Prepare a native campaign, group and ad with read-back validation while keeping delivery paused.

When to use it

Use it when

The user requests paused campaign and ad creation for a selected Microsoft Advertising account.

Do not use it when

Inferring delivery or account eligibility from a successful configuration alone.

Preconditions

Connect Microsoft Advertising and explicitly select an authorized account. Writes require an eligible paid plan and confirmation.
Read bing_get_setup_guide and use only the capabilities enabled for this account.
The account is among the chosen accounts, confirmed via list_accounts.

Evidence every conclusion must carry

Inputs
Input	Required	What it is
`window`		Analysis window.Default: last 30 days.

In order. Every tool named is one the gateway ships, and links to its reference.

Steps

Read native setup and write schemas for the requested entities and validate account eligibility.bing_get_setup_guidebing_get_write_schema
Preview the campaign, then apply only after confirmation; read back its ID and paused status.bing_create_campaignbing_get_campaigns
Use the returned campaign ID to preview and confirm a paused group with native targeting.bing_create_ad_groupbing_get_ad_groups
Use the returned group and validated creative IDs to preview and confirm a paused ad, then read it back.bing_create_adbing_get_ads

The observable condition, what it lets you conclude, and what takes the conclusion back.

When A preview succeedsConclude It proves only local preparation; wait for provider acceptance and read-back before claiming creation.
When A write times out or returns an uncertain resultConclude Search for the created object before retrying to prevent duplicates.
When The requested objective or format is not validated for this accountConclude State the limitation and stop dependent writes; do not substitute an objective silently.

The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

The cases where the analysis is wrong and still looks right. Read them before trusting a number.

Creation requires a plan with writes and explicit confirmation for each proposed mutation.
Keep parent campaigns and groups paused; this workflow does not activate advertising.
Changes made on a real advertising account are real, even during a test.