Microsoft has just erased the $19 registration fee for solo developers publishing to the Microsoft Store, replacing the old credit card requirement with a government ID and selfie-based identity check. The move, which began rolling out in select markets and is now reportedly live in nearly 200 countries, represents one of the most aggressive overtures the company has made to independent Windows software creators in a decade.

The change eliminates a direct financial barrier that disproportionately affected hobbyists, students, and creators in regions with limited payment infrastructure. Instead of handing over credit card details or a one-time payment, new individual publishers now verify their identity with a government-issued ID and a selfie. It’s a clear signal that Microsoft intends to transform the Store from a polite afterthought into a low-friction distribution superhighway for all manner of Windows apps.

The Big Shift: Paywall to ID Check

For years, the Microsoft Store carried a dual reputation problem: a narrow catalog of approved app types and a nontrivial onboarding cost that could deter small creators. The Windows 11 Store redesign began tearing down the first wall by welcoming Win32, PWAs, Electron apps, and more. Now Microsoft is attacking the second barrier with a free-for-individuals model and a guided sign-up flow that routes new publishers directly into Partner Center.

Under the new process, an individual developer visits the Store’s marketing sign-up page, signs in with a personal Microsoft account (MSA), and then completes identity verification by uploading a government ID and a selfie. The flow omits any credit card step entirely. This identity check serves as an abuse deterrent, replacing the monetary verification that previously guarded the platform.

It’s critical to note that the free onboarding is currently being flighted. In markets where the updated flow has landed, developers bypass the legacy fee. In others, Partner Center may still display the $19 charge. Microsoft advises new users to start from the Store’s dedicated marketing entrypoint. The company says the free experience is now available in approximately 200 markets, but real-world reports suggest the rollout is still uneven—so some developers may need patience.

Who Wins and What Stays the Same

The beneficiaries of this change are clear: hobbyists, solo devs, and creators in emerging markets. Removing the credit card gate alone opens the door for countless individuals who lack international payment methods or simply don’t want to risk a single dollar on an experiment. For them, the Store now offers a zero-cost path to a distribution channel with over 250 million monthly active users, automatic updates, and built-in trust signals.

What remains unchanged is equally important. Company and organization accounts still pay a registration fee, which varies by market and follows the legacy Partner Center onboarding path. The identity verification step applies to all new individual accounts, and existing publishers won’t receive refunds on previously paid fees. For non-gaming apps, developers still enjoy the flexibility to bring their own in-app payment system and keep 100% of revenue—a policy Microsoft reaffirms with this update.

A Guided Path from Storefront to Partner Center

The new onboarding flow is designed to be dead simple. Microsoft has built a sign-up page on the consumer-facing Store that funnels individuals directly into Partner Center with minimal friction. This path deliberately bypasses the legacy Partner Center enrollment, which for individual accounts previously required a credit card and charged the $19 fee.

After signing in with a Microsoft Account, the developer is prompted to upload a government ID and a selfie. Microsoft’s documentation indicates that this data is used for verification and handled per privacy standards, though no independent third-party audits are publicly cited. For developers with strong privacy concerns, the ID requirement remains a friction point—trading one form of gatekeeping for another.

Once verified, the developer lands in Partner Center, where they can reserve an app name, prepare packages, and choose monetization options. The entire process from start to submission can now be completed in a single session, a stark contrast to the days when even small indie efforts required tax documentation and payment steps.

Packaging, Signing, and Hosting: The MSIX Advantage

The fee waiver is most powerful when combined with MSIX packaging. Microsoft recommends MSIX for all Windows apps, and for good reason. When submitting an MSIX package to the Store—even an unsigned one—Microsoft’s submission pipeline automatically signs it with a Store-trusted certificate and maps the publisher metadata to Partner Center records. This eliminates the common headaches of certificate management, signature mismatches, and sideloading trust prompts.

Developers who package as MSIX also get integrated Store hosting and automatic updates. Microsoft handles distribution, content delivery, and update orchestration, removing the need for a custom CDN or homegrown update checker. For small teams, this operational simplicity can be a game-changer.

It’s worth noting that this server-side signing step is a Store-specific convenience. For CI/CD or enterprise distribution, developers will still need to manage code signing with tools like Azure SignTool, Azure Key Vault, or traditional certificates. But for the majority of indie apps aiming at consumer distribution, the Store’s packaging pipeline is a significant time saver.

Commerce Flexibility: Keep 100% or Use Microsoft’s Stack

One of the most consequential policy shifts of recent years has been the option for non-gaming app publishers to use external billing systems. This remains intact and unchanged with the new zero-fee onboarding. If you’re building a SaaS tool, a productivity utility, or any non-game app, you can integrate your own payment processor, manage subscriptions outside Microsoft’s commerce, and keep every cent of revenue. Microsoft will not take a cut on transactions processed entirely through developer-controlled billing.

That said, Microsoft Commerce is still an attractive option. It offers global payment coverage, simplified tax handling, integrated receipts and payouts, and platform fees that are lower in many cases than mobile storefronts. The choice is entirely yours, giving developers the freedom to marry Store discoverability with a business model that fits.

Enterprise Reach via Intune

For developers aiming at commercial customers, the Store also supports distribution through Microsoft Intune and Endpoint Manager. IT administrators can push Store entries—including line-of-business apps—to managed fleets, leveraging the same packaging, signing, and update pipeline. This hybrid route is a potent channel for tools targeting businesses, especially now that entry costs are zero for small ISVs.

250 Million Users: Discoverability Reality Check

Microsoft claims the Store reaches more than 250 million monthly active users. That’s a serious audience for desktop software distribution, and the Store’s editorial curation, personalized home pages, and AI-driven recommendations improve organic discovery compared to raw web distribution. Still, a free listing is not a marketing plan. The Store now hosts a much larger catalog than it did a few years ago, so standing out requires metadata optimization, compelling screenshots, concise descriptions, and possibly promotional codes or launch discounts.

Independent publishers have reported steady growth in downloads and revenue since the Windows 11 redesign, but the discoverability landscape remains competitive. The zero-fee change will likely add new titles, making it even more important for developers to treat their Store listing as a marketing asset, not a set-it-and-forget-it landing page.

Caveats: Privacy, Rollout, and Standing Out

For all its developer-friendly intent, the new onboarding system introduces a few legitimate concerns.

1. Identity Verification and Privacy

Replacing a credit card with a government ID and selfie shifts the friction point to identity privacy. For creators in countries with unreliable ID systems or those who simply object to sharing sensitive personal data, this may still be a barrier. Microsoft’s privacy policies cover the data handling, but the lack of a publicly detailed independent audit might give pause to privacy-conscious developers.

2. Flighting and Uneven Rollout

The free onboarding flow is not yet universal. Some markets and entry points still show the legacy $19 charge in Partner Center. Developers who encounter the old flow are advised to retry via the Store’s marketing sign-up page or wait for regional rollout. This inconsistency creates confusion and could dampen the initial wave of new publishers Microsoft hopes to attract.

3. Discoverability Is a Separate Challenge

With a lower barrier to entry, the Store will likely see an influx of new apps. Standing out will require active effort in app presentation, monetization strategy, and possibly paid promotion. The economic benefit of free onboarding may be limited for those who cannot invest time in marketing.

4. Policy Edge Cases

The long-term specifics around which app categories can use external payments—and how Microsoft enforces buyer protections for those flows—remain subject to policy clarifications. Developers implementing their own billing must stay vigilant about Microsoft’s in-app policy rules to avoid takedowns.

How It Compares to Apple and Google

Microsoft’s move creates a stark contrast with its competitors. Google Play charges a one-time $25 developer registration fee, though it has occasionally waived it in certain programs. Apple’s App Store requires a $99 annual fee for individuals and organizations alike. By dropping the fee to zero for individuals—and making it a one-time verification step instead of a recurring charge—Microsoft has crafted one of the lowest-cost entry points among major app platforms for independent PC developers.

The trade-off is identity verification, a friction point that neither Apple nor Google currently mandates at registration. But for the vast majority of aspiring Windows developers, the math is simple: free beats $25 and $99.

Practical Steps for New Indie Publishers

If you’re a solo developer eyeing the Microsoft Store, here’s a practical game plan:

  • Start at the right entry point. Begin at the Store’s developer marketing page and choose Individual account. Avoid the legacy Partner Center sign-up unless your region hasn’t received the new flow.
  • Sign in with a personal Microsoft account. No corporate tax documentation is needed.
  • Complete the ID verification. Have a government ID ready and be prepared to take a selfie. This step replaces the old credit card requirement.
  • Reserve your app name and prepare your package. MSIX is strongly recommended—it unlocks server-side signing, hosting, and auto-updates.
  • Decide your commerce path early. If you’re building a non-game app, consider whether you want to use Microsoft Commerce or bring your own payment processor. Review the Store’s third-party billing policy to ensure compliance.
  • Treat the Store listing as a marketing asset. Invest in high-quality screenshots, an explainer video if possible, and a crisp description. Consider promotional codes to kickstart downloads. Use the Store’s editorial and curation features to your advantage.
  • Document your privacy choices. Be ready to provide privacy policies and terms of service during the submission review.

Looking Ahead

The removal of the individual registration fee is not a silver bullet. Identity verification introduces a different friction, the rollout remains inconsistent, and discoverability is a battle every publisher must wage. But for the first time in the Store’s history, the financial on-ramp for a solo developer is completely zero. Combined with flexible commerce options, MSIX packaging conveniences, and access to hundreds of millions of Windows users, Microsoft has made a compelling case for indie creators to consider the Store as their primary distribution channel.

As the flight expands and more developers take advantage of the free onboarding, we’ll see whether the promise of a broader app ecosystem translates into a more vibrant, trustworthy, and innovative platform for Windows users. For now, the message is unmistakable: Microsoft wants your app, and they’re willing to waive the cover charge.