Microsoft today switched on bulk editing and appeals for disapproved assets across all advertising accounts, a change that lets teams fix or contest rejected text and image creative in batches rather than one item at a time. Performance Max campaigns are excluded from this version.

The update was disclosed by Navah Hopkins, Microsoft Ads Liaison, in a post published today on LinkedIn. "Thrilled to share that Microsoft Advertising just made it easier to adjust/appeal assets with Bulk edit disapproved assets!" Hopkins wrote. "This is live in all accounts and works for text and image assets."

The reasoning given for the change was operational rather than strategic. "We heard you that it can be tedious to make changes and appeal assets one at a time," according to Hopkins. That description matches how asset-level moderation has worked on Microsoft Advertising until now: a responsive search ad carrying fifteen headlines and four descriptions could accumulate a scattering of individual rejections, each requiring its own edit or its own appeal submission.

Supporting documentation on Microsoft Learn, last updated on 06/27/2026, sets out the mechanics in more detail than the announcement itself, and also marks the boundaries of what the first release covers.

An asset grid with a policy status column

The feature is built around the asset grid, the tabular view of individual creative components inside an ad or ad group. According to the documentation, advertisers add a Policy status column to that grid to surface when an asset carries one of two states: Disapproved, or Approved (limited). Both appear when an asset fails editorial review.

From there, the workflow is a small sequence. An advertiser opens the asset grid at ad group or ad level, selects the disapproved asset, chooses Edit on the ribbon, and edits the text in a side panel. The panel requires updated content to replace the rejected copy. A final step determines the blast radius of the change: the edit can be applied to all associations, or to a single association. Updates are then reviewed on the Bulk edit page under Tools.

A product screenshot circulated with the announcement shows what that side panel contains in practice. Selecting a long headline reading "Savor the unique citrus and chocolate notes in our top-selling espresso blend" opens an Edit headline pane carrying two notices. The first states that the headline is used in five ads across three campaigns. The second is a policy warning stating that the asset does not meet Microsoft Advertising policies, with a link to the disapproved reason, in this case a food products restriction applied to Vietnam.

That second notice is the more instructive of the pair. Microsoft's documentation states plainly that policies may vary depending on the country or region where an ad is displayed. A single headline can therefore be perfectly compliant across most of an advertiser's footprint and rejected in one market, and the rejection propagates to every ad and campaign that shares the asset. The screenshot's five-ads-across-three-campaigns notice quantifies exactly that exposure before an edit is committed.

The same toolbar carries a second option alongside Edit asset: Request exception. Selecting multiple assets and choosing that path opens the appeal flow rather than the editing flow.

Appeals have to cover every disapproved asset in an ad

The most consequential technical constraint in the announcement concerns how appeals are scoped. "Because we conduct editorial review at the asset level, appeals must be done for all disapproved assets in an ad," according to Hopkins. "This is what allows approved assets to serve while the appeal is underway if the final url is still approved."

The trade-off embedded in that sentence deserves unpacking. Because moderation happens per asset rather than per ad, an ad with three rejected headlines and twelve approved ones does not stop serving. The approved components continue to run, provided the final URL itself has cleared review. The price of that continuity is that appeals cannot be filed selectively within an ad: contesting one rejection means contesting all of them.

The documentation reflects this in the interface options. When requesting an exception from the asset grid, advertisers choose either Selected asset(s) or All assets in this ad. Separate entry points exist at ad level, where the option reads Request an exception for all assets in this ad, and at ad group level, where an equivalent covers every disapproved asset in the group. Each path ends at a free-text box requesting the reason behind the exception.

Image edits require a replacement file

Text and images behave differently under the new tool. "If you're editing images, you'll need to replace the image with a new one," according to Hopkins. There is no in-panel cropping, resizing, or adjustment path. A rejected image asset can only be substituted.

That distinction has practical weight for teams whose rejections stem from format-level criteria rather than content. The asymmetry is not unique to Microsoft. Google Ads set out disapproval criteria for blurred, distorted and poorly cropped image assets in documentation published in July 2026, alongside a note that image asset requirements are more restrictive than the requirements applied to other Google surfaces, meaning a rejected image may still run elsewhere on the network.

Appeals may be the faster route than edits

Hopkins framed the appeal path as frequently preferable to creative surgery. "Requesting an exception (appeal) can make more sense than adjusting the creative," according to the post. "Note: you can request up to 5000 ad exceptions."

Microsoft's documentation confirms that ceiling and describes the account-wide route that reaches it. Advertisers open the Ads and extensions view, apply a filter for the not eligible delivery status through Add filter, Attributes and Delivery, then select all, choose Edit, and select Request exception. The documented cap is 5,000 ads per request.

For advertisers running large accounts, that number sets a hard boundary on how much enforcement can be contested in a single operation. It also implies that Microsoft expects appeals at that volume to occur, which is consistent with the platform's own published enforcement figures.

Enforcement volumes give the tool its context

The scale of moderation on the platform is documented. Microsoft removed or restricted more than one billion advertisements that violated its policies during 2024 and suspended more than 475,000 accounts. In the same period, the company rejected close to 245,000 ads and 5,000 accounts in response to roughly 70,000 complaints, and overturned more than 1.5 million ad rejections and 20,000 account actions in response to about 72,000 appeals.

That last figure is the relevant one. Overturns substantially outnumbered the appeals filed, which indicates that successful appeals frequently restored multiple items at once, and that a meaningful share of enforcement was reversed on review. The documentation acknowledges the same dynamic from another angle, noting that Microsoft's team performs periodic spot checks on editorial rejections and occasionally reverses them without any advertiser action.

Timing is documented as well. Most editorial reviews complete within 48 hours, according to Microsoft, and content still carrying an Under Review delivery status after two business days is directed to Support.

How rejections are classified

The documentation separates detection from decision. The mode of detection records how an ad was flagged before receiving a Disapproved or Approved Limited status, with three values: System, meaning the platform's own evaluation; User, meaning one or more people who saw the ad reported it; and Legal order, meaning a regulatory body specifically requested removal.

Rejection is recorded separately, with two values: System, where the platform's evaluation made the call, and Manual, where a human reviewer did. The pairing means an ad can be flagged by a member of the public and then rejected by an automated system, or flagged automatically and rejected by a person.

Advertisers who lose an appeal encounter a distinct status, Disapproved, exception denied, which the documentation defines as Microsoft having reviewed the exception request and determined the item still fails policy. Edits made after that point trigger automatic re-review, and a new delivery status appears if the revised content passes.

What the first version does not cover

Several boundaries are set out explicitly. Supported scope for the asset grid policy status column is currently the ad group level and the ad level. Campaign and account level support is described as coming in a future release. Performance Max is not included in this version, and the All assets in this ad option is separately noted as unavailable for Performance Max campaigns.

That exclusion is notable given how central the campaign type has become to Microsoft's roadmap. The platform raised the search theme limit to 50 per Performance Max campaign in January 2026, added customer acquisition goals and autogenerated assets for responsive search ads later that month, and switched on its Ad Preview Hub inside Performance Max on July 28, 2026. Performance Max is also the campaign type where creative assembly is handed to Microsoft's systems, which mix uploaded assets across search, native and display placements, making per-asset rejections harder to trace by hand.

Other components sit outside the bulk tool entirely. Disapproved asset groups require contacting Support to appeal. Keywords cannot be edited at all; the documented remedy is adding a replacement keyword and deleting the rejected one, with the new keyword entering editorial review on save. Ad extensions are handled through their own Edit an extension flow, ad customizers require Support, disclaimers carry a dedicated Request an exception for disclaimer option, and disapproved feed items must be corrected at source and re-uploaded through business data feeds.

Why this matters for the marketing community

Policy remediation is unglamorous work that consumes disproportionate agency hours, and the two largest search platforms are moving in visibly different directions on it.

Google narrowed its appeal window in July 2026, ending the option to appeal policy decisions made more than six months earlier directly from an account. Under Google's documented rules, each ad can be appealed three times before further submissions require contacting support, and filing too many unique appeals within 24 hours triggers a temporary processing suspension. Microsoft's change runs the other way, raising throughput rather than restricting it, though the 5,000-ad cap and the all-or-nothing scoping rule are their own form of limit.

The update also fits a pattern of bulk operations arriving steadily across the Microsoft interface. The platform introduced centralised website exclusion management with a 10,000-domain capacity per list in August 2025, and has been consolidating campaign management into the web product since retiring its mobile application in January 2026. Programmatic access is being consolidated too, with the legacy SOAP API losing access to new features from October 1, 2026 and reaching full deprecation on January 31, 2027.

Commercial context frames the effort. Microsoft's search advertising revenue excluding traffic acquisition costs grew 10 percent year over year in the fourth quarter of fiscal 2026, or 9 percent in constant currency, down from 12 percent in the preceding quarter and well below the 21 percent rates recorded through fiscal 2025. Tooling that returns rejected creative to circulation faster addresses revenue that is already committed but not currently serving, which is a different problem from acquiring new demand.

The announcement continues a run of feature disclosures routed through the Ads Liaison role, created when Microsoft appointed Hopkins to the position in June 2025 with direct reporting into product teams. Recent items surfaced the same way include Product explorer for United States retailers on June 16, 2026, and job seniority filtering within LinkedIn profile targeting on June 15, 2026.

Timeline

Summary

Who: Microsoft Advertising, with the release disclosed by Navah Hopkins, Microsoft Ads Liaison. The change affects advertisers, agencies and in-house teams managing creative assets on the platform, particularly those operating across multiple countries where policy treatment varies.

What: Bulk edit disapproved assets, a capability allowing multiple rejected text and image assets to be edited or appealed in a single operation. Edits are made through a side panel in the asset grid and applied either to all associations of the asset or to a single association. Appeals must cover every disapproved asset within an ad, a consequence of editorial review operating at asset level, which in turn allows approved assets to keep serving during an appeal when the final URL remains approved. Image assets cannot be adjusted in place and must be replaced. Account-wide exception requests are capped at 5,000 ads.

When: Announced today, August 6, 2026, through a LinkedIn post. Supporting Microsoft Learn documentation was last updated on June 27, 2026. Most editorial reviews complete within 48 hours, with items still under review after two business days directed to Support.

Where: Live in all Microsoft Advertising accounts. The asset grid policy status column is supported at ad group and ad level, with campaign and account level support described as arriving in a future release. Performance Max is not included in this version, and disapproved asset groups require contacting Support.

Why: According to Hopkins, editing and appealing assets one at a time had become tedious for advertisers. The platform's own enforcement disclosures show more than 1.5 million ad rejections overturned in 2024 against roughly 72,000 appeals, indicating substantial volumes of remediation work. The release lands as Microsoft search advertising growth slows to 10 percent year over year in the fourth quarter of fiscal 2026, making faster restoration of already-committed creative a measurable revenue question rather than a purely administrative one.