Microsoft has quietly rewritten a chunk of the rulebook that governs every game sold through the Xbox Store, and the clock on compliance is almost up. Xbox Store Policy 7.20, published on September 15, 2026, takes effect on October 22, 2026, roughly five weeks after Microsoft first posted it to its developer documentation. The update adds three brand-new sections covering cross-device consistency, cross-platform commerce, and localization metadata, while tightening existing rules on age ratings and user-generated content. None of it rewrites the core Xbox requirements for Xbox games, but it does turn several soft expectations into hard certification gates.
The timing matters. Policy 7.20 lands less than a week after a separate push in Washington, the Power to the Players Act, put digital game ownership and server-shutdown protections in front of Congress. Microsoft’s update does not touch resale rights or offline modes, but it does expand how much control the company exerts over entitlements, purchases, and content that moves across Xbox console, PC, and companion apps. For developers already juggling certification checklists, the next five weeks bring a genuinely new set of boxes to tick before October 22.
Don't miss new tech stories on Google
Add Shattered once in the Google app and our stories show up in your news suggestions.
What Xbox Store Policy 7.20 Actually Changes
Microsoft’s published change history for Xbox Store Policy 7.20 identifies five specific areas of change: three entirely new sections and two updated ones. The first cosmetic shift is a rebrand, with “Xbox” capitalized to “XBOX” throughout the document to match the company’s current style guide. That alone changes nothing functionally, but it signals Microsoft treated this as a full-document pass rather than a patch note.
The substantive changes sit in section 10.13, which governs technical requirements for games distributed under a shared product code, and sections 11.11 and 11.12, which cover age ratings and user-generated content. Here is the breakdown Microsoft has published so far.
| Section | Topic | What Changed | Status |
|---|---|---|---|
| 10.13.12 | Support Across XBOX Devices | New section. Games sharing a product code across XBOX devices must match primary input, game saves, online multiplayer, and game modes. | New in 7.20 |
| 10.13.13 | Cross Platform Digital Game Entitlements and Commerce | New section covering roaming entitlements, purchases, commerce, progress, and companion apps tied to XBOX Network services. | New in 7.20 |
| 10.13.14 | Required Metadata and In-Game Localization | New section requiring metadata and in-game language support across seven listed languages where applicable. | New in 7.20 |
| 11.11 | Age Ratings | Updated to require accurate, lifecycle-long ratings, including whenever a new rating arrives from any authority. | Updated in 7.20 |
| 11.12 | User-Generated Content | Expanded reporting and moderation expectations for titles integrating third-party mod or UGC platforms. | Updated in 7.20 |
Microsoft’s change-history page describes the age-ratings update directly: “Updated 11.11, Age Ratings, requires accurate and updated product age rating throughout a product’s lifecycle or when a new age rating is received from any rating authority,” according to the Microsoft Store Policies change history. That single line turns age-rating compliance from a one-time submission checkbox into an ongoing obligation developers have to actively maintain.
Section 10.13.12: One Product Code, Consistent Experience Everywhere
The new section 10.13.12 targets games that use the same product code across multiple XBOX devices, a category that has grown fast since Microsoft leaned harder into its hybrid console-and-handheld strategy. Under the new rule, any title using a shared code must deliver matching support for primary input methods, game saves, online multiplayer, and game modes no matter which device a player picks up. In practice, that closes a gap where a game might ship full-featured on console but arrive on a handheld missing multiplayer or half its game modes while still carrying the same listing.
This isn’t an abstract concern. The current wave of Xbox-branded handhelds, including devices compared directly against Valve’s hardware in our ROG Xbox Ally X20 vs Steam Deck breakdown, has made cross-device parity a real purchasing consideration rather than a theoretical one. If a shopper buys a game expecting console-equivalent functionality on a handheld, and it under-delivers, that is now a certification failure rather than just a bad review.
Microsoft’s own developer documentation frames the broader cross-device vision through Xbox Play Anywhere, the program built to let a single purchase travel across the ecosystem. XBOX Play Anywhere (XPA) is described as “the only program that enables players to move back and forth effortlessly across the XBOX ecosystem on console, PC, and more,” per Microsoft’s Xbox Play Anywhere documentation. Section 10.13.12 effectively codifies the baseline experience XPA was designed to deliver, and extends the expectation beyond just save syncing into input, multiplayer, and mode parity.
Section 10.13.13: Entitlements, Purchases, and Cross-Platform Commerce
The biggest structural addition is section 10.13.13, Cross Platform Digital Game Entitlements and Commerce. It covers games that share or roam digital content, including entitlements, purchases, commerce, progress, cross-platform play, cross-network play, and companion apps, whenever a title integrates with XBOX Network services. Microsoft’s developer documentation defines the core concept plainly: “An entitlement represents the customer’s right to access and use a digital product, including games, subscriptions, and add-ons,” according to Xbox Developer Documentation.
Xbox Play Anywhere materials spell out how that plays out for buyers today: “Players purchase the console or PC version of your game from any XBOX online store and receive access to both,” per Microsoft’s Xbox Play Anywhere documentation. Section 10.13.13 extends that same logic to a broader set of cross-platform and cross-network scenarios, formalizing rules for how entitlements, purchases, and progress must behave once a game plugs into XBOX Network services beyond a simple console-to-PC pairing.
One important clarification buried in the policy language: this section does not open the door for Steam, the Epic Games Store, or any other third-party storefront client to run natively on Xbox consoles. It governs games that already provide cross-platform access or commerce, tightening the rules around how that access and commerce must function, rather than inviting competing storefronts onto Xbox hardware. Developers hoping Policy 7.20 signals an open Xbox console platform will be disappointed; this is a compliance expansion, not a walled-garden teardown.
Section 10.13.14: Seven Languages, One Metadata Standard
Section 10.13.14 adds required metadata and in-game localization rules, listing the supported languages as English, French, Spanish, German, Portuguese, Japanese, and Simplified Chinese, in regions where those languages apply. This is narrower than a blanket global-localization mandate. It instead requires developers to properly tag and surface metadata for whichever of those seven languages a title already supports, closing gaps where a game claims regional availability without matching in-game language coverage or accurate store listing metadata.
For mid-size and indie studios, this is arguably the most operationally annoying part of Policy 7.20, because it touches the store listing pipeline rather than the game binary itself. Metadata accuracy issues are the kind of thing that can trigger certification rejections late in a submission cycle, and a studio that assumed its localization paperwork was in order could find itself resubmitting after October 22 if its listing metadata doesn’t match what actually ships in the build.
Age Ratings Become a Lifecycle Obligation, Not a Launch-Day Checkbox
Section 11.11 was already part of the Xbox Store policy framework, but Policy 7.20 tightens it meaningfully. Developers must now keep a product’s age rating accurate and current for the entire lifecycle of the product, including any time a rating authority issues an updated classification. That means a content update, a DLC drop, or a tonal shift introduced post-launch can trigger a fresh obligation to re-certify the rating, not just at the point of initial submission.
This lands alongside a separate certification change Microsoft made in August 2026, removing the XR-017 title-ratings test from its certification suite. Age-rating declarations continue to be validated at submission even after that test was removed, according to Xbox certification documentation, meaning the lifecycle obligation introduced in Policy 7.20 fills a gap left by retiring the automated XR-017 check rather than replacing a safeguard outright. Developers now carry more of the ongoing compliance burden themselves, with Microsoft spot-checking rather than running a dedicated automated ratings test at every submission.
Mods and User-Generated Content Face New Reporting Rules
Section 11.12 expands obligations for any product that integrates with a third-party game-mod or UGC platform. Microsoft isn’t banning mods or third-party UGC systems outright. Instead, it is adding reporting and content-moderation expectations for developers whose games plug into those systems, shifting more responsibility onto the studio rather than leaving moderation entirely to the third-party mod platform.
Xbox’s own player-facing guidance already carries a blunt warning about the risk profile of mod content: “Mod content isn’t rated by the ESRB or other boards and may not be appropriate for every age,” according to Xbox Support’s guidance on enabling PC game mods. Section 11.12 essentially pushes developers to take that warning seriously from a compliance standpoint, requiring them to have reporting and moderation processes in place rather than treating third-party mod integration as a hands-off feature.
This echoes a broader industry pattern of platforms tightening account- and content-level controls rather than loosening them, a trend also visible in how console makers have hardened authentication requirements, as covered in our look at Steam Guard vs PSN two-factor authentication adoption. Anti-cheat and certification systems are following a similar trajectory of shifting more enforcement burden onto structured, auditable processes, a theme we also tracked in our comparison of EAC, BattlEye, and Vanguard’s kernel-level requirements.
How Xbox Store Policy 7.20 Stacks Up Against PlayStation and Steam
No single storefront discloses a perfectly matched policy document, so a side-by-side comparison has to be read carefully. PlayStation’s software terms permit user-generated content such as text, images, videos, gameplay clips, and music, while reserving Sony’s right to review, modify, remove, or disable that content, according to PlayStation’s software usage terms. Those terms also grant Sony broad, worldwide, royalty-free rights to use and commercially exploit submitted UGC, including sublicensing and promotional use. That is a terms-of-use framework governing what players submit, not a store-policy section matching the cross-device entitlement, metadata-localization, or third-party-mod reporting package Xbox just introduced.
Valve has not published an equivalent, publicly comparable Steam policy document covering the same five areas, so a precise current comparison on cross-device entitlements or mod reporting would be speculative. What is clear is that Xbox is now the only one of the three major storefronts with a dated, versioned, publicly change-logged policy document spelling out cross-device consistency requirements in this much technical detail.
| Policy Area | Xbox Store Policy 7.20 | PlayStation Store | Steam |
|---|---|---|---|
| Cross-device entitlements & purchases | Explicit section (10.13.13) covering roaming entitlements, purchases, commerce, and progress | No comparable public store-policy section identified | No comparable public store-policy section identified |
| Cross-device functionality parity | Explicit section (10.13.12) requiring matching input, saves, multiplayer, and modes | No equivalent requirement identified | No equivalent requirement identified |
| Mods and UGC | Expanded reporting/moderation duties for developers (11.12) | UGC may be reviewed, edited, removed; broad license granted to Sony | No current policy text retrieved for comparison |
| Age ratings | Lifecycle-long accuracy requirement (11.11) | No directly comparable current rule identified | No directly comparable current rule identified |
| Localization metadata | Explicit section (10.13.14), seven listed languages | No equivalent rule identified | No equivalent rule identified |
Why Microsoft Is Formalizing This Now
Xbox’s strategy over the past two years has leaned hard into being a service and an ecosystem rather than a single box under the TV. Xbox Play Anywhere, cloud streaming, a growing lineup of Xbox-branded handhelds, and companion apps that let players track progress away from a console have all multiplied the number of places a single Xbox entitlement needs to behave consistently. As of July 10, 2026, cross-platform PC and XBOX save roaming is required for Xbox Play Anywhere titles and recommended for non-XPA titles, according to Xbox certification documentation, showing Microsoft was already tightening this area incrementally before Policy 7.20 made it an explicit, numbered store-policy section.
There’s also a regulatory backdrop worth noting. Lawmakers have been turning up pressure on how platforms handle digital ownership, visible in the proposed federal bill covered in our report on the Power to the Players Act and digital game ownership. While Policy 7.20 does not address resale rights, offline modes, or server-shutdown protections directly, a company formalizing its entitlement and commerce rules in granular, versioned detail right as Congress debates digital ownership is unlikely to be a coincidence. Tighter internal documentation of how entitlements work gives Microsoft a clearer paper trail if regulators start asking platform-specific questions.
A Brief History of Xbox Store Policy Versioning
Microsoft has run a numbered, change-logged store policy framework for years, with past versions archived publicly, including a preserved copy of Policy 7.7 in Microsoft’s documentation archive. The available change-history record does not provide a reliable publication date for versions 7.19 or 7.18, nor a complete redline count of every clause altered between versions, so Policy 7.20 should be understood as the latest entry in a long-running, incrementally updated document rather than a one-off overhaul. What distinguishes this release is the concentration of change in one area, cross-device and cross-platform behavior, rather than scattered updates across unrelated sections.
That pattern matters for developers trying to anticipate what Policy 7.21 or 7.22 might bring. If Microsoft is building out a numbered section family under 10.13 specifically for cross-device and cross-platform behavior, it’s a reasonable bet that future versions will keep expanding that same family rather than starting a new one, following the same incremental logic the company has applied to other certification areas over time.
Developer and Publisher Reaction So Far
As of the most recent reporting on October 18, 2026, no named studio, publisher, or trade group had issued a public statement responding to Policy 7.20. Coverage of the update, including a report from unixgaming.org on the new rules taking effect October 22, describes the policy as a tightening of synchronization requirements around progress, purchases, and content rather than a flashpoint that has drawn public developer pushback. That silence likely reflects the technical, back-office nature of the changes. Entitlement logic, metadata tagging, and lifecycle rating accuracy are plumbing-level concerns that rarely generate the kind of public studio statements that storefront fee changes or content restrictions tend to provoke.
That said, the absence of public comment doesn’t mean the absence of internal work. Certification teams at mid-size and large publishers have had five weeks since the September 15 publication date to audit their cross-device builds, localization metadata, and mod-integration reporting processes. Studios that missed the September announcement and are only now scrambling to read the fine print have a much tighter window before the October 22 enforcement date arrives.
Market Impact: Game Pass, Handhelds, and the Cost of Compliance
The practical effect of Policy 7.20 falls hardest on three groups: studios shipping titles across Xbox console and Xbox-branded handhelds under a shared product code, publishers running live-service games with companion apps tied into XBOX Network services, and any developer whose game integrates third-party mod or UGC platforms. For the first group, section 10.13.12 means QA budgets now need to explicitly cover parity testing across every device a shared product code targets, not just the flagship console build.
For the second group, section 10.13.13 raises the bar on how carefully a studio needs to architect entitlement and purchase logic before connecting a game to XBOX Network services at all. A live-service title with a companion mobile app, cross-progression, and in-game purchases now has a much more explicit certification target to hit, which could slow down submission timelines for titles that haven’t already built clean entitlement syncing. For the third group, the reporting and moderation obligations under 11.12 add ongoing operational cost rather than a one-time engineering fix, since moderation is a continuous process rather than a shippable feature.
What Developers Should Do Before October 22
Studios with titles already live on the Xbox Store, or submissions in the certification pipeline, have a narrow and specific checklist to work through before Policy 7.20 takes effect. The highest-priority items are the ones most likely to trigger a certification rejection if overlooked.
- Audit any title sharing a product code across multiple XBOX devices for matching primary input, save behavior, multiplayer, and game modes under section 10.13.12.
- Review entitlement, purchase, and companion-app logic for any game tied into XBOX Network services against the new section 10.13.13 requirements.
- Confirm store listing metadata matches actual in-game language support across the seven languages named in section 10.13.14.
- Re-verify age ratings remain current, including after any post-launch content update that could trigger a new classification under section 11.11.
- Document reporting and moderation processes for any third-party mod or UGC platform integration under section 11.12.
What Comes Next for Platform Policy
A few trends seem likely to play out over the coming months based on the direction Policy 7.20 sets. First, expect Microsoft to keep expanding the 10.13 section family as its handheld and cross-device hardware lineup grows, since this policy reads like a foundation rather than a finished structure. Second, expect PlayStation to face growing pressure to publish a more detailed, versioned store policy of its own, particularly if Sony keeps pushing PC ports and cross-platform features that raise the same entitlement questions Xbox just formalized.
Third, the lifecycle age-ratings requirement is likely to catch some live-service titles off guard the first time a content update shifts a rating, producing a wave of after-the-fact compliance scrambles rather than clean pre-submission approvals. Fourth, the mod and UGC reporting requirements could push smaller studios to lean on established third-party mod platforms with existing moderation infrastructure rather than building in-house systems, consolidating more modding activity onto a handful of established services. Fifth, given the parallel momentum behind digital ownership legislation, it would not be surprising to see a future Xbox Store policy version address resale, transfer, or offline-mode requirements directly, rather than leaving that fight entirely to Congress.
Frequently Asked Questions
What is Xbox Store Policy 7.20?
It is the latest version of Microsoft’s Xbox Store certification and publishing requirements, published September 15, 2026, adding three new sections and updating two existing ones that cover cross-device consistency, cross-platform commerce, localization metadata, age ratings, and mod/UGC reporting.
When does Xbox Store Policy 7.20 take effect?
October 22, 2026, roughly five weeks after Microsoft published the policy to its developer documentation on September 15, 2026.
What does section 10.13.13 of Xbox Store Policy 7.20 cover?
It covers Cross Platform Digital Game Entitlements and Commerce, meaning digital entitlements, purchases, commerce, progress, cross-platform play, cross-network play, and companion apps for any title integrated with XBOX Network services.
Does Xbox Store Policy 7.20 let Steam or the Epic Games Store install on Xbox consoles?
No. The new cross-platform commerce section governs games that already provide cross-platform access or entitlements; it does not authorize third-party storefront clients to install on Xbox console hardware.
How does Policy 7.20 change rules around mods and user-generated content?
Section 11.12 now requires developers integrating third-party mod or UGC platforms to meet additional reporting and content-moderation expectations, rather than treating mod support as a hands-off feature.
Are age ratings now checked after a game launches?
Yes. Section 11.11 requires developers to keep a product’s age rating accurate throughout its entire lifecycle, including whenever a rating authority issues a new classification, not just at initial submission.
How does this compare to PlayStation Store or Steam policy?
PlayStation’s software terms address user-generated content broadly but do not publish a directly comparable section covering cross-device entitlements, metadata localization, or mod reporting in the same detail. Valve has not published an equivalent public policy document for direct comparison.
Where can developers read the full Xbox Store Policy 7.20 text?
The complete, current policy document and its change history are published on Microsoft’s developer documentation site, alongside archived versions of prior policy releases for reference.