Microsoft Store Policy 7.20: New Xbox Cross-Platform Rules for Windows Games and Mods

As reported by Shattered.io and confirmed by Microsoft Learn’s official Microsoft Store Policies documentation, version 7.20 introduces three brand-new sections under the Gaming and XBOX umbrella—sections 10.13.12, 10.13.13, and 10.13.14—while tightening two existing content policy clauses covering age ratings (11.11) and user-generated content (11.12). Alongside a cosmetic pass that capitalizes "Xbox" to "XBOX" throughout the document, these updates codify technical and commercial rules for games spanning consoles, Windows PCs, handhelds, and third-party gaming networks.

While early commentary has framed these updates as broad parity mandates, a closer inspection of Microsoft’s primary policy text on Microsoft Learn reveals a much more surgical set of requirements. Each clause carries specific triggering conditions, exemptions, and boundaries that Windows and console developers need to understand before submitting their next build to Partner Center.

What Changes in Microsoft Store Policy 7.20​

To understand where the new certification gates sit, it helps to look at the five updated policy areas side by side against the actual language published in Microsoft Learn’s Store Policies and Xbox Game Development Kit (GDK) documentation.

Section Summary: Policy 7.20 focuses heavily on how multi-device and cross-network games behave when they touch XBOX Network Services or share a single Store ID, while clarifying ongoing publisher responsibilities for store metadata, age ratings, and mod moderation.

Section 10.13.12: Shared Product Codes and Cross-Device Boundaries​

As Microsoft expands its ecosystem across living-room consoles, Windows 11 desktops, PC-based gaming handhelds, and cloud streaming, the definition of an "Xbox game" has stretched considerably. In Section 10.13.12, Microsoft formally defines "XBOX devices" as any hardware supporting access to XBOX games—explicitly including XBOX Consoles, Microsoft or third-party PC-based devices that play XBOX games natively, and Microsoft or third-party streaming devices.

However, the technical requirements in 10.13.12 do not apply universally to every PC port or console release. They are triggered specifically when a game uses the same product code (Store ID) and is natively playable (meaning downloaded, installed, and played locally) across multiple XBOX devices. When a title meets that threshold, four specific rules apply:

• Primary Input Nuances: Contrary to assumptions that every shared-ID game must offer identical input schemes everywhere, Microsoft’s policy draws a sharp line between consoles and PCs. Games natively playable on XBOX console devices must support navigation via gamepad input (with additional peripherals allowed only with prior approval). For other XBOX devices where the game is natively playable—specifically PCs and handhelds—supporting the primary input device is recommended, but not required.
• Game Save Compatibility (XR-052): Every supported XBOX device must comply with certification requirement XR-052 (User State and Title-Save Location, Roaming and Dependencies). According to Microsoft’s GDK certification documentation (updated July 10, 2026, in Console version 16.3), games sharing a TitleID must roam save progress across XBOX consoles, and—if the title is part of the XBOX Play Anywhere (XPA) program—across Windows PCs and XBOX consoles. For non-XPA titles, save roaming between Windows PCs and consoles, or to non-Microsoft platforms like iOS, Android, Switch, or PlayStation, remains recommended rather than mandatory.
• Online Multiplayer Segmentation: If a shared-ID title supports online multiplayer, developers cannot segment the player pool based on device type within the same generation of an XBOX device family—for example, separating players on XBOX Series S from those on XBOX Series X.
• Game Mode Parity and Upgrade Fees: All game modes must match across devices within the same generation of an XBOX device family, and modes cannot be excluded from one device in that generation, subject to technical limitations. Furthermore, games cannot break existing saves or charge players for new, updated, or additional features when moving to a newer device within that same generation.

Section Summary: Rather than forcing identical features across every conceivable screen, Section 10.13.12 protects buyers within the same hardware generation and Store ID from fractured multiplayer pools, missing modes, broken saves, or intra-generation upgrade fees, while keeping gamepad support on Windows PCs and handhelds a recommendation rather than a hard certification failure.

Section 10.13.13: Cross-Platform Commerce, Roaming Entitlements, and Parity Offers​

If Section 10.13.12 governs hardware inside the Xbox tent, Section 10.13.13 governs what happens when a game reaches outside of it. This section applies whenever digital game content integrates with XBOX Network Services and is shared, roamed, or made available across platforms, networks, or digital storefronts outside the Microsoft Store.

Why is Microsoft laying down strict tracks here? In an era of live-service titles where a player might grind a battle pass on a Windows PC, buy virtual currency on a mobile companion app, and boot up a console in the evening, entitlement architectures can easily turn into a tangled mess—or worse, a way to treat Xbox and Microsoft Store on Windows buyers as second-class citizens. Microsoft’s policy text establishes clear boundaries between what can roam and what cannot:

1. Progress, Wallets, and Achievements: Titles may, at their discretion, synchronize game progress, virtual currency wallets, and in-game items (including items unlocked via virtual currency) across gaming platforms and networks. Holistic statistics—including achievement unlocks—can also sync, provided those achievements do not require gameplay or a financial purchase on another platform to unlock.
2. The Paid DLC Roaming Ban vs. In-Game Bundles: Here is a critical commercial boundary for publishers. Paid downloadable content (PDLC) such as map packs or base-game expansions that are sold and managed in the Microsoft Store (and across other platform stores) may not be shared or roamed across gaming networks. Conversely, bundles of in-game items—like virtual currency or items unlocked with it—that are sold through the Microsoft Store but managed by the title itself may be shared and roamed at the developer’s discretion. Same-IP expansions can also be sold in-game for virtual currency if they are usable within the base game, whereas unique premium base games (whether same-IP or unrelated) cannot be sold for virtual currency or through in-game stores under those exceptions.
3. The "Same or Better" Offer Mandate: If a title sells cross-platform content elsewhere, it must offer the same or better for-sale content offers in the Microsoft Store—explicitly including the Microsoft Store on Windows. Microsoft specifies that XBOX users must not be disadvantaged across release timing, market coverage, gameplay features and capabilities, bonus virtual currency or in-game benefits, language and localization, or physical token card offerings. Any digital codes sold directly to consumers must also have a corresponding offer in Microsoft’s Digital Content at Retail (Code to Content) program.
4. Cross-Network Play and Safety: Cross-platform play among XBOX network users (such as Xbox console players and Microsoft Store on Windows players) and cross-network play with non-XBOX gaming networks are both permitted at the title's discretion. However, cross-network communication must respect XBOX network safety settings, and any title that requires cross-network play must state that requirement clearly on its Product Detail Page (PDP) in the Microsoft Store, including on Windows.

As Shattered.io rightly points out, nothing in Section 10.13.13 authorizes third-party storefront clients like Steam or the Epic Games Store to install natively on Xbox console hardware. It is strictly a framework governing how games that integrate with XBOX Network Services handle cross-network entitlements and store parity.

Section Summary: Section 10.13.13 allows cross-progression and title-managed virtual currency to roam freely across networks, blocks Store-managed map packs and expansions from roaming across competing platform stores, and legally binds publishers to give the Microsoft Store (on both console and Windows) release, feature, and bonus parity with rival storefronts.

Section 10.13.14: Eight Languages and the Metadata Localization Standard​

Localization rules often trip up indie and mid-sized studios during final submission, and Section 10.13.14 is a prime example of why reading the exact specification matters. While secondary reporting has referred to this clause as a "seven-language" mandate for both metadata and in-game text, Microsoft’s actual policy text in Section 10.13.14 lists eight distinct languages and treats store metadata differently from in-game binary localization.

When a title is released in regions where the following languages are supported, all applicable metadata must be localized into:

• EFIGS: English, French, Italian, German, and Spanish (five languages)
• Portuguese: With Brazilian Portuguese noted as preferable
• Japanese: Subject to strict formatting rules—the Sort String must use Hiragana, a single-byte space, and a single-byte number, while other strings may use Hiragana, Katakana, Kanji, alphanumeric characters, and English if no direct translation exists (such as a proper noun like Halo)
• Simplified Chinese: With Traditional Chinese listed as optional

What about localizing the actual game binary? Section 10.13.14 does not force every indie developer to translate dialogue trees into eight languages to pass certification. Instead, Microsoft directs developers to the Windows-supported and Console-supported language tables for regional PDP requirements and notes that those tables apply to in-game localization "should the partner opt to localize in-game". Localizing Product Detail Page metadata for countries or languages beyond the core list remains encouraged at the publisher's discretion.

Section Summary: Publishers releasing games in applicable regions must localize their store listing metadata across the eight specified languages (EFIGS, Portuguese, Japanese, and Simplified Chinese), while following Microsoft's regional language tables for in-game localization if they choose to localize the game itself.

Sections 11.11 and 11.12: Lifecycle Age Ratings and Third-Party Mod Moderation​

The final two updates in Policy 7.20 tighten content governance across the Microsoft Store:

11.11 Age Ratings​

Developers have long been required to complete the International Age Rating Coalition (IARC) questionnaire in Partner Center upon initial submission. Under the updated Section 11.11.2, publishers are explicitly responsible for keeping age rating information accurate and current throughout the entire product lifecycle, "including when changes to your product may affect its assigned age rating". If any rating authority issues a new rating, or if rating details change, the developer must promptly update Partner Center. Additionally, Section 11.11.3 stipulates that if a product delivers user-generated, retail, or web-based content that might warrant a higher age rating than the base game's assigned rating, users must be able to opt in via a content filter or by signing in with a pre-existing account.

It is worth separating two often-conflated events here: not every DLC drop or patch automatically triggers a re-rating—only changes that may affect the assigned rating or official reclassifications by a rating board. Separately, Microsoft’s GDK documentation notes that on August 6, 2026 (Console version 16.4), Microsoft removed test case XR-017 Title Ratings from its console certification suite, while explicitly confirming that age-rating declarations continue to be validated at submission.

11.12 User-Generated Content (UGC)​

For any product containing online-accessible UGC, developers must publish accessible UGC terms of service or content guidelines (both in-product and on their website), provide an in-product reporting mechanism for inappropriate, illegal, or harmful UGC (and/or implement proactive detection), respect platform safety and parental privilege settings, and remove or disable UGC upon request from Microsoft.

New in 7.20 is a dedicated stipulation for games that integrate with a third-party game-mod or UGC platform. Because PC and console mods are not rated by the ESRB or international rating boards, studios plugging into external mod repositories can no longer treat moderation as someone else's problem. Developers must now:

1. Integrate with the applicable reporting or complaint mechanisms of that third-party platform where available, and comply with all moderation obligations required under their agreement with the third-party provider.
2. Clearly disclose to players when content is not created, published, or sourced by the game’s developer or publisher—using an in-product disclaimer, dialog box, or visual indicator where appropriate.

Section Summary: Sections 11.11 and 11.12 ensure that evolving live-service games keep their Partner Center age ratings aligned with reality and that studios integrating third-party mod platforms wire up available reporting tools and display clear third-party content disclaimers inside the game.

Pre-Submission Compliance Checklist for Windows and Xbox Studios​

With the October 22, 2026 enforcement deadline arriving, certification and publishing teams distributing games on Xbox consoles or the Microsoft Store on Windows should run a targeted audit against their active and upcoming TitleIDs:

1. Verify Shared Store IDs (10.13.12): If your game uses a single Store ID across console, Windows PC, or handhelds, confirm that same-generation console families share identical game modes and unsegmented multiplayer pools, and verify that save roaming meets XR-052 (mandatory between Windows PC and console for XPA titles).
2. Audit Cross-Platform Store Offers (10.13.13): If your game links to XBOX Network Services and sells DLC or currency on rival storefronts, verify that the Microsoft Store (including on Windows) receives equal or better pricing, release timing, bonus content, and retail Code to Content parity. Ensure Store-managed PDLC is not configured to roam across external gaming networks.
3. Check Product Detail Page Disclosures (10.13.13): Confirm that any title requiring cross-network play explicitly discloses that requirement on its console and Windows Store PDPs.
4. Scrub Regional Store Metadata (10.13.14): Check Partner Center listings in supported regions across all eight required languages (English, French, Italian, German, Spanish, Portuguese, Japanese, and Simplified Chinese), paying special attention to Japanese Hiragana sort-string formatting rules.
5. Review Mod UI and Rating Status (11.11 & 11.12): Ensure any post-launch content updates haven't drifted past your IARC rating declarations, and verify that third-party mod browsers display an in-game unverified-source disclaimer alongside integrated reporting tools.