Microsoft has quietly rewritten the rulebook that governs every game sold through the Microsoft Store and the Xbox network. Version 7.20 of the Microsoft Store Policies, published September 15, 2026, takes effect October 22, 2026, and it does something no prior revision has attempted: it forces publishers to treat Xbox consoles, Windows PCs, and companion apps as one continuous environment rather than three separate storefronts.
The update lands at a politically loaded moment. Microsoft gaming chief Asha Sharma has spent the past month talking up a “family of devices” strategy for the next Xbox generation, Game Pass listings now carry a dedicated Handheld platform column, and rivals Valve and Sony are racing to lock down their own portable and cross-save ecosystems. Buried in the legal fine print of policy version 7.20 is the actual mechanism Microsoft plans to use to pull that strategy together: mandatory cross-device save roaming, mandatory cross-platform entitlement recognition, and mandatory localization in seven languages. For developers, it is the biggest compliance shift to hit Xbox and PC publishing since Microsoft merged its Xbox Live branding into the “Xbox network” name change in 2025.
What Changed in Microsoft Store Policy 7.20
According to Microsoft’s own published change history, version 7.20 replaces version 7.19, which had been in effect since October 14, 2025. The headline edits are not cosmetic. Microsoft renamed every instance of “Xbox” to “XBOX” throughout the document to align with a branding refresh, then added three entirely new subsections — 10.13.12, 10.13.13, and 10.13.14 — that did not exist in any prior version of the policy.
Section 10.13.12, titled Support Across XBOX Devices, sets baseline requirements for any game that ships under a single product code across multiple XBOX form factors. It covers primary input handling, game save behavior, online multiplayer parity, and game mode consistency. Section 10.13.13 goes further, addressing cross-platform digital entitlements, commerce, and what Microsoft calls game-progress roaming — the ability for a save file to follow a player from an Xbox console to a Windows PC and, eventually, to a companion app. Section 10.13.14 adds a metadata and localization mandate: games distributed through the Microsoft Store must support in-game localization in English, French, Spanish, German, Portuguese, Japanese, and Simplified Chinese wherever those languages are supported in the target region.
Microsoft also revised section 11.11 on age ratings, which now requires publishers to keep ratings accurate and current for the full lifecycle of a product rather than only at launch, and updated section 11.12 on user-generated content to add reporting and moderation obligations for any game that integrates third-party mod or UGC platforms. The existing security clause in section 10.2, which requires publishers to not jeopardize device or system security and bars disabling platform safety features, carries over unchanged from version 7.19, but it now sits alongside the new cross-device and localization rules as part of a far larger compliance surface.
Why Microsoft Is Forcing Cross-Play and Save Roaming Now
The timing is not an accident. Xbox has spent 2026 publicly repositioning itself away from a single hardware box and toward what leadership calls a device family spanning consoles, Windows PCs, cloud streaming, and eventually a dedicated handheld built either in-house or with a partner. Sharma has reaffirmed that framing multiple times this fall, and the ASUS-made ROG Xbox Ally and Ally X have already proven there is demand for Xbox-branded software outside a traditional console. If Microsoft wants a save file, a friends list, and a purchased game library to feel identical whether a player is on a living-room console, a handheld, or a laptop, the company needs a legal mechanism to force every publisher on its platform to support that behavior rather than leaving it optional.
That mechanism is section 10.13.13. Microsoft’s own Xbox certification documentation, published separately from the store policy itself, already states that cross-platform PC and XBOX console game-save roaming is required for XPA titles — games published under Microsoft’s first-party XPA program — and merely recommended for everyone else. Policy 7.20 pushes that expectation into the general store terms that apply to any publisher, signaling that the “recommended” language for third-party titles is likely to tighten in a future revision once the infrastructure is in place.
The localization requirement in 10.13.14 tells a parallel story. Seven mandatory languages is a notably broader list than Microsoft has required in the past, and it maps closely to the markets where Xbox has been trying to grow Game Pass subscriptions outside North America, particularly Latin America, continental Europe, and East Asia. A publisher that wants shelf space on the Microsoft Store now has to budget for localization work that used to be optional polish.
Microsoft Store Policy 7.19 vs 7.20: What Actually Changed
| Provision | Version 7.19 (Oct. 14, 2025) | Version 7.20 (Oct. 22, 2026) |
|---|---|---|
| Branding in document text | “Xbox” used throughout | Renamed to “XBOX” throughout |
| Cross-device support rules | Not addressed as a standalone section | New section 10.13.12 covers input, saves, multiplayer, and game modes across XBOX devices |
| Cross-platform entitlements and commerce | Not addressed | New section 10.13.13 covers entitlements, commerce, progress roaming, cross-network play, and companion apps |
| Localization requirements | Not specified in store policy | New section 10.13.14 mandates 7 languages where regionally supported |
| Age rating maintenance | Accuracy expected at submission | Section 11.11 now requires accuracy for the full product lifecycle |
| User-generated content oversight | General content standards applied | Section 11.12 adds reporting/moderation duties for UGC and mod integrations |
| Security baseline (section 10.2) | Bars compromising device/system security | Unchanged, carried forward as-is |
| Package distribution rule | Games (excluding subscription titles) must use supported Store package types | Unchanged, carried forward as-is |
The table above is drawn directly from Microsoft’s published change log and the archived text of version 7.19. Two things stand out. First, every brand-new obligation in 7.20 is about devices talking to each other — saves, entitlements, companion apps — rather than about content restrictions. Second, Microsoft left the core security and distribution language from 7.19 completely untouched, which suggests the company sees this revision as additive infrastructure rather than a response to a specific security incident.
How This Compares to Steam and Apple’s App Store Rules
Valve took an early lead on one piece of this puzzle: AI content disclosure. Steam has required developers to disclose the use of AI-generated content since January 2024 and rewrote that policy in January 2026 to separate pre-generated material from content a game generates live during play, according to Valve’s own developer documentation. Steam’s approach is narrower than what Microsoft is now building: it is a labeling requirement tied to store listings and in-game disclosure, not a cross-device infrastructure mandate. Valve has also never required publishers to support save roaming across a defined language list, largely because Steam’s own ecosystem — PC, Steam Deck, and the upcoming Steam Machine — already shares a single account and cloud-save layer by design, so there has been less need to legislate it into the store terms.
Apple’s App Store Review Guidelines sit at the opposite end of the spectrum from both. Apple’s rules are content- and commerce-focused — restrictions on in-app purchase mechanics, external payment links, and age-appropriate content — rather than infrastructure-focused. Apple does not operate console hardware, so it has no equivalent to Microsoft’s cross-device save-roaming problem. The practical effect is that Microsoft is now the only major platform holder writing hardware-interoperability obligations directly into its store terms of service, a reflection of being the only company among the three that ships both a console and a PC storefront under one brand.
Platform Policy Comparison at a Glance
| Platform | Cross-device save roaming | AI content disclosure | Mandatory localization | Standard commission |
|---|---|---|---|---|
| Microsoft Store / Xbox | Required for XPA titles; general obligation added in Policy 7.20 | Addressed under broader security/transparency updates, full text not yet public | 7 languages mandated under section 10.13.14 | Varies by product type; console games historically near 30% |
| Steam (Valve) | Native to platform design, not a written store-policy mandate | Required since Jan. 2024, rewritten Jan. 2026 to split pre-generated vs. live content | Not mandated; left to publisher discretion | 30% standard, reduced above revenue thresholds |
| Apple App Store | Not applicable (no console hardware) | Covered under general content and metadata review rules | Not mandated; left to publisher discretion | Reduced to 5% in the EU for qualifying game storefront rivals in 2026 |
| Epic Games Store | Not mandated in store terms | Not mandated in store terms | Not mandated; left to publisher discretion | 12% flat rate since 2019 launch |
The commission figures in the table reflect each platform’s long-standing public terms; Apple’s reduced EU rate for competing game storefronts was confirmed when the European Commission pushed through its 2026 App Store fee ruling. None of the four platforms currently publish a figure for what share of their total catalog is affected by cross-device or AI-disclosure rules, which matters for the next section.
The Open Questions Microsoft Has Not Answered
Microsoft’s public documentation for version 7.20 is unusually thin on specifics for two of its most consequential additions. The company has confirmed it added generative-AI transparency language and a child-safety update to the same policy cycle, per a contemporaneous report on the change, but the operative text defining what counts as a disclosable AI output, where that disclosure must appear, and what penalty applies for non-compliance has not been made public in a form that allows a precise reading. The same is true of a widely discussed restriction on exchanging in-game currency or items for real-world value through external marketplaces: Microsoft’s change history gestures at the policy area without publishing the exact scope, so it remains unclear whether the rule targets all transferable items, only developer-operated marketplaces, or player-to-player resale specifically.
Microsoft has also not published a percentage figure for how many games or developers the new cross-device and localization rules will actually touch, nor has it announced a grace period or staged enforcement timeline beyond the single October 22, 2026 effective date. For a policy change this structurally significant, the lack of an enforcement calendar leaves publishers guessing about whether a title that is close to compliant on launch day will be quietly grandfathered in or pulled from new submissions until it meets the full 10.13.12 through 10.13.14 requirements.
Historical Context: From Xbox Live to the XBOX Network Rebrand
Microsoft Store policy has evolved in fairly small increments for most of the past decade. Version 7.7, which took effect in February 2018, and version 7.15 both carried the same core distribution clause now found in 7.20 almost word for word: games must be submitted through supported package types, and once submitted that way, they must be installed and updated only through the Store. Version 7.19, published September 10, 2025, was itself a branding-driven update — it replaced references to “Xbox Live” with “Xbox network” to match a wider naming overhaul and added the pricing-term restriction on search terms that is still in force today.
Version 7.20 breaks that pattern of incremental branding tweaks. It is the first revision in the document’s public history to add genuinely new structural obligations rather than clarify or rename existing ones. That makes it comparable, in scope if not in subject matter, to the moment Apple first introduced its App Tracking Transparency requirement into the App Store guidelines: a policy change that looks like routine legal housekeeping on the surface but reshapes how every publisher on the platform has to build their product going forward.
Market Impact: What This Means for Publishers and Players
For large publishers already building cross-save systems for games that ship on Xbox, PlayStation, Switch 2, and PC simultaneously, the compliance lift from Policy 7.20 is modest; many of the biggest live-service titles already roam saves across platforms because players demand it. The bigger burden falls on small and mid-size studios that have historically treated the Xbox console version and the Windows PC version of a game as separate SKUs with separate save systems, often because building true cross-device save sync is engineering overhead that smaller teams have deprioritized. Those studios now have less runway to defer that work if they want continued Store distribution past October 22, 2026.
The localization mandate carries its own cost curve. A studio that previously shipped English-only on Xbox and added other languages opportunistically now has a baseline obligation to support seven languages wherever regionally applicable, which professional localization vendors typically price per word, per language, and per quality-assurance pass. For a text-heavy RPG or narrative adventure game, that can represent a meaningful new line item in a budget that did not previously account for it.
For players, the upside is straightforward: a game bought once should increasingly behave the same way whether played on an Xbox Series X, a Windows handheld, or a future Xbox-branded portable device, with progress and entitlements following the account rather than the box. The downside is a familiar one in platform economics — compliance costs that publishers absorb have a way of showing up eventually in either game pricing, reduced platform support for smaller titles, or both.
Competitive Pressure From Valve and Sony
Microsoft is not writing these rules in a vacuum. Valve’s Steam ecosystem already offers near-seamless cross-device saves across Steam Deck, Steam Machine, and PC because Valve controls both the storefront and the dominant handheld hardware running the same underlying SteamOS stack. Sony, meanwhile, has reportedly been developing its own handheld strategy built around a next-generation chip node aimed at battery efficiency and true portability rather than a bulkier hybrid device, based on recent supply-chain reporting. Microsoft’s 10.13.12 through 10.13.14 additions read as a direct legal response to both: if Xbox wants its “family of devices” pitch to be credible against a Valve ecosystem that already behaves this way natively, writing the behavior into binding store policy is the fastest way to guarantee publisher compliance without waiting for every studio to volunteer the engineering work.
What Developers Need to Do Before October 22
Studios with titles currently live on the Microsoft Store or awaiting Xbox certification should treat three tasks as priorities ahead of the effective date. First, audit save-file architecture for any game using a shared product code across Xbox console and PC builds, since section 10.13.12 applies specifically to that scenario. Second, review localization coverage against the seven mandated languages and flag any region where a currently English-only release might fall out of compliance. Third, revisit age-rating documentation to confirm it reflects the product’s current state rather than its state at original submission, since section 11.11 now treats rating accuracy as a lifecycle obligation rather than a one-time checkbox.
Studios that integrate third-party mod support or user-generated content tools should also review their moderation and reporting pipeline against the updated section 11.12 language, since Microsoft has signaled it expects publishers — not just the platform — to carry some responsibility for policing UGC that flows through their games.
Five Predictions for How This Plays Out
- Microsoft will publish a follow-up clarification or FAQ for sections 10.13.12 through 10.13.14 before the October 22, 2026 effective date, mirroring how it has handled past ambiguous policy rollouts.
- The “recommended” save-roaming language for non-XPA titles in Xbox’s certification documentation will be upgraded to “required” within the next one to two policy cycles, extending what is currently a first-party-only obligation to all third-party publishers.
- A dedicated Xbox handheld announcement, when it comes, will explicitly reference the cross-device infrastructure built under Policy 7.20 as the technical backbone making the device viable at launch rather than years later.
- Smaller studios will push back publicly on the localization mandate’s cost burden, likely through developer forums and trade press, pressuring Microsoft to clarify whether partial compliance or phased rollout is acceptable.
- Steam and Apple will not mirror Microsoft’s cross-device mandate in the near term, since neither company’s business model depends on unifying console and PC behavior the way Xbox’s does; expect continued policy divergence rather than convergence among the three platforms.
Frequently Asked Questions
When does Microsoft Store Policy 7.20 take effect?
Version 7.20 was published September 15, 2026, and becomes effective October 22, 2026, according to Microsoft’s official policy documentation.
What are the biggest changes in Policy 7.20?
Three new sections: 10.13.12 (cross-device support requirements covering input, saves, multiplayer, and game modes), 10.13.13 (cross-platform entitlements, commerce, and progress roaming), and 10.13.14 (mandatory localization in seven languages). Microsoft also updated age-rating and user-generated-content rules.
Does this policy require cross-play between Xbox and PlayStation?
No. The cross-platform language in section 10.13.13 refers to roaming across XBOX-branded devices, Windows PC, and Microsoft’s own network and storefronts, not cross-play with competing console platforms like PlayStation or Switch 2.
Which languages does the new localization rule require?
English, French, Spanish, German, Portuguese, Japanese, and Simplified Chinese, applied wherever those languages are supported in the relevant region.
How does this compare to Steam’s AI content policy?
Steam’s policy is a labeling and disclosure requirement for AI-generated content in store listings and gameplay, in place since January 2024 and revised in January 2026. Microsoft’s 7.20 update references generative-AI transparency changes in the same policy cycle, but the full operative text has not been published in detail, making a precise comparison difficult at this stage.
Will small indie developers be exempt from the new rules?
Microsoft has not published an exemption threshold or an affected-developer percentage. The policy text applies broadly to game products distributed through the Microsoft Store, with the notable carve-out that games offered only through PC gaming subscription products are excluded from the package-submission rule.
Is this related to the rumored Xbox handheld or Project Helix?
Not directly, but the timing overlaps with Microsoft’s public comments about a broader Xbox device family strategy. The cross-device save and entitlement infrastructure mandated in 10.13.12 and 10.13.13 is the kind of technical groundwork a unified console-handheld-PC ecosystem would depend on.
What happens to games that are not compliant by October 22, 2026?
Microsoft has not published a specific enforcement timeline, grace period, or penalty schedule for the new provisions. The general Store policy framework ties continued distribution to policy compliance, but no staged enforcement date beyond the effective date itself has been made public.
