Microsoft Synthetic Ad Disclosure Rules: A Practical Workflow

Your designer used generative fill, your editor replaced a voice segment, or your campaign team built an image from an AI prompt. Now you need to decide whether the ad can run on Microsoft Advertising, whether it needs a disclosure, and what evidence you should keep.

Make that decision before the final export. A disclosure added at the upload screen cannot recover missing permission, removed provenance data, or a misleading depiction. The workable approach is to review AI involvement, accuracy, authorization, disclosure, and provenance as separate controls.

Start with AI involvement, not whether the ad looks artificial

Microsoft Advertising places AI-generated, AI-manipulated, and other synthetic content within its policy scope. When AI helped create or materially alter an ad, the audience may need to be told.

That does not mean every use of AI automatically receives the same label. It means every use should receive a disclosure determination. If your media buyer first learns about the AI work after receiving the finished asset, the review has started too late.

Add these questions to the creative brief:

• Did AI generate any copy, image, video, audio, voice, person, product, setting, or event shown in the ad?
• Did AI materially change recorded or photographed material, even if the original was real?
• Could the finished creative make a viewer believe that a real person said, did, endorsed, or experienced something?
• Does it reproduce or simulate an identifiable person’s likeness or voice?
• Which countries or regions will receive the campaign?
• Does the working file contain watermarks, metadata, or other provenance information that must survive production?

For an internal materiality test, ask whether the AI work could change what a reasonable viewer believes about a person, product, place, claim, or event. A background cleanup is not operationally equivalent to fabricating a product demonstration or making a person appear to deliver a statement. This is a practical escalation test, not a universal legal definition. When the answer is unclear and the campaign carries rights or regulatory exposure, have counsel qualified in the relevant market review it.

Treat compliance as four separate approval gates

The common mistake is to treat an “AI-generated” label as a complete compliance solution. It is only one control. Your ad should pass four gates independently.

1. Accuracy and eligibility

Review the people, products, places, claims, and events depicted in the creative. Microsoft expects advertisers to check that those elements are accurate before submission. A disclosure explains how content was made; it does not make a false claim, prohibited deepfake, or deceptive demonstration acceptable.

Run the review against the finished ad, not just the prompt. Generative systems can introduce details that nobody explicitly requested, so prompt approval is not creative approval. Compare the final asset with the real product, approved claim language, authorized spokesperson material, and the event or location it purports to show.

2. Authorization

Confirm that you have any permission required to use a person’s likeness or voice. Advertisers remain responsible for applicable laws in every market where a campaign appears, including requirements involving consent, permissions, disclosures, likenesses, and voices.

Do not infer authorization from access to a photograph, recording, stock asset, or previous campaign file. Document what was authorized, for which media and markets, and whether synthetic alteration or voice replication falls within that authorization. If the permission does not clearly cover the planned use, pause the ad rather than relying on a label to fill the gap.

3. Consumer disclosure

Determine whether a visible or audible disclosure is required for that asset, format, and market. When notice is required, it must be clear and positioned close to the content it explains. Permission from the depicted person does not eliminate a separate disclosure obligation.

4. Machine-readable provenance

Preserve watermarks, metadata, and other available signals identifying how synthetic content was created. These signals support provenance, but they are not necessarily visible to a consumer. Passing the provenance gate therefore does not mean you have passed the disclosure gate.

Approve the ad only when all four gates pass. That structure prevents a reviewer from answering one narrow question – “Does it have a label?” – while missing the reason the ad should not run at all.

Put the disclosure where the consumer encounters the synthetic content

An AI note in a production ticket, file name, landing-page footer, or internal media plan is not a consumer-facing disclosure. When disclosure is required, Microsoft recommends embedding it directly in image and video assets. Microsoft Advertising’s disclaimer feature can also be used with formats that support it.

Use this placement process:

1. Add the approved disclosure to the asset master, not only to one exported placement.
2. Keep it close to the synthetic element or claim it qualifies. Do not make the viewer search another screen for the explanation.
3. Match the disclosure mode to the experience. Image and video disclosures need to be visible; audio-led creative may also require an audible notice.
4. Export every required size and format, then inspect the actual output. Cropping, compression, scaling, captions, and interface overlays can make a disclosure unreadable or separate it from the relevant content.
5. Where the Microsoft Advertising disclaimer feature is supported, decide whether it should supplement or deliver the required notice for that format. Do not assume feature availability removes the need to inspect the consumer-facing result.
6. Record the approved wording, placement, disclosure mode, markets, formats, and approver so later adaptations do not silently change the decision.

Do not invent a single global font size, duration, or phrase and treat it as universally sufficient. The governing requirement is that the disclosure be clear, close to the relevant content, and compliant wherever the campaign runs. If a local rule or approval imposes more specific wording or presentation, carry that requirement into the asset specification.

Localization deserves a new review. Translated wording can become longer, a resized layout can push the label out of view, and a newly added market can change the applicable requirement. Treat each of those changes as a controlled version, not a harmless derivative.

Protect provenance and permission records throughout production

Images, audio, and video created with Microsoft AI tools can contain machine-readable provenance data, metadata, and imperceptible watermarks indicating AI involvement. Because those signals may not be apparent to the audience, you may still need a separate visible or audible disclosure.

Your production workflow should preserve both the technical evidence and the human approval record:

• Keep the original AI output before retouching, resizing, or re-encoding.
• Retain the working file and submitted export so reviewers can trace what changed.
• Do not deliberately remove a watermark, metadata field, or provenance signal merely to make the file look cleaner.
• Check whether your export process retained the provenance information present in the source asset.
• Store documented likeness and voice authorization with the creative record, including any limits relevant to synthetic alteration.
• Keep the market-by-market disclosure decision with the exact asset version it covers.
• Save evidence of how the consumer-facing disclosure appears in the final format.

This record is useful only if versioning is disciplined. A later editor should be able to tell whether a new crop, translated label, revised voice track, or altered product scene reopened one of the four approval gates. “Approved” should never float free of a specific file and campaign scope.

Interfering with machine-readable provenance information is not a harmless optimization. Along with prohibited deepfakes, impersonation, unauthorized use of a likeness or voice, and omitted required disclosures, it can contribute to an ad being rejected, restricted, or removed.

Use a repeatable approval workflow before every submission

Build the review into campaign operations instead of asking the media buyer to reconstruct the creative history at launch. The following workflow is specific enough to assign owners and flexible enough to use across image, video, audio, and copy-led ads.

1. Inventory AI involvement. Record which portions of the ad were generated or materially altered and retain the original outputs.
2. Map distribution. List the markets, languages, Microsoft Advertising formats, and derivative sizes planned for the campaign.
3. Challenge accuracy. Verify every depicted person, product, place, claim, and event against approved factual material.
4. Clear rights. Confirm that any likeness or voice use has the authorization required for the specific synthetic use, media, and market.
5. Screen for stop conditions. Do not submit deceptive creative, prohibited deepfakes, impersonation, or unresolved unauthorized use merely because a disclosure can be added.
6. Make the disclosure decision. Determine the required wording, visible or audible treatment, proximity, and market coverage. Escalate unresolved legal questions to qualified counsel.
7. Build the notice into production. Embed it in image or video assets when required and configure the platform disclaimer feature where supported and appropriate.
8. Run final-output quality assurance. Confirm that the disclosure remains clear and close to the relevant content and that provenance information has not been stripped.
9. Approve a specific version. Store the decision, evidence, permissions, asset identifier, formats, markets, and approver together. Reopen review after any material creative or distribution change.

If an ad fails because its underlying depiction is deceptive or unauthorized, rebuild or withdraw it. Relabeling is not remediation. Microsoft is allowing AI-assisted advertising, but an AI disclosure does not make deceptive creative acceptable.

Key takeaways

• Route every AI-generated or materially altered ad through review, even when the synthetic work is difficult to notice.
• Assess accuracy, authorization, disclosure, and provenance separately; success in one area does not cure failure in another.
• When disclosure is required, make it clear, close to the relevant content, and part of the asset where appropriate.
• Preserve metadata, watermarks, and other provenance signals, but do not mistake them for consumer-facing notice.
• Do not use a label to justify a deepfake, impersonation, deceptive claim, or unauthorized likeness or voice.
• Repeat the determination for each market, format, language, and materially changed creative version.

Your next move is concrete: add five required fields to the creative intake form – AI involvement, likeness or voice use, target markets, disclosure decision, and provenance status. Assign an owner to each field before the asset enters paid-media production. That small change moves compliance from a last-minute label request to a reviewable part of how the ad is made.

References

• Search Engine Land – Microsoft Advertising sets rules for AI-generated ads