Microsoft policy pages specify 18+ targeting across restricted categories

What changed

What the evidence shows: rendered Microsoft Ads policy pages for Food Products, Beauty and Cosmetics, Healthcare and Pharmaceutical, Religious Content, Psychics, Tarot Reading and Mediums, People Finder and Research Sites, and Government Services and Products state that advertising must target ages 18+. Each inspected page displays “last updated” metadata of 5 October 2026. Category and country restrictions still apply. This metadata evidences a page revision, not the first introduction of the age requirement, its effective date or an enforcement date. Secondary coverage was published on 16 October.

PMC advertiser perspective: advertisers should treat the wording as a policy-control prompt rather than evidence of an immediate account-wide enforcement event. Age targeting can interact with audience reach, campaign structure, consent choices, creative review and local regulation. The practical task is to identify which campaigns fall into a named restricted category and whether their current targeting configuration supports the policy wording.

For example, a team reviewing a beauty campaign can start by identifying the exact products and destination pages, then consult the beauty policy and applicable country requirements together. For advertising within the scope of the inspected policy, the documented age instruction is 18+. Record the policy category, market, audience settings and review date so that the account decision can be checked against the source. This example does not establish any exception or substitute for the relevant policy.

Proposed checks begin with a campaign inventory: identify relevant products, destination pages, markets and audience settings. Preserve screenshots or exports showing the age configuration and policy text consulted on the review date. Check whether agency, franchise or multi-market account structures apply age settings consistently. Legal and compliance teams should assess local requirements independently, especially where healthcare, government services or personal-information products are involved. If an account receives a rejection or enforcement notice, record the exact policy reference and affected market before changing unrelated campaigns.

Avoid turning the 5 October page metadata into an unsupported deadline. It is sensible to review affected campaigns promptly, but the available evidence does not show that Microsoft first created the rule on that date or that all affected ads began enforcement then. The strongest conclusion is narrower: the inspected policy pages currently state an 18+ targeting requirement for the listed restricted categories.

Why it matters for advertisers

The policy wording may require advertisers in several sensitive categories to validate age-targeting settings, even though the update date does not prove enforcement timing.