Microsoft Store Erases $19 Entry Fee for Solo Developers: No Credit Card Needed, Just an ID

Individual developers can now publish apps on the Microsoft Store without paying a cent. Microsoft has officially eliminated the one‑time registration fee for personal accounts, replacing it with an identity‑verification process that requires a government ID and a selfie. The change, announced at Build 2025 and now live in more than 200 markets, marks a deliberate pivot toward openness—and a direct challenge to Apple’s $99 annual developer charge.

A Long‑Overdue Unlocking

The Microsoft Store’s journey has been rocky. When it debuted alongside Windows 8 in 2012 as the “Windows Store,” it was slow, restricted to Universal Windows Platform (UWP) apps, and starved of marquee software. Over the next decade, Microsoft rebuilt the storefront: it rebranded to Microsoft Store in 2021, tore down the wall between UWP and classic Win32 apps, embraced Progressive Web Apps, .NET MAUI, and Electron, and let developers host their own binaries. Performance improved dramatically, and heavyweight apps like Adobe Creative Cloud, Discord, Slack, Spotify, and ChatGPT moved in.

Yet the cash barrier persisted. Until now, individual developers forked over a one‑time $19 fee, while companies paid $99. Google asks $25 once; Apple demands $99 every year. Microsoft’s move undercuts them all. “Eliminating registration fees for individual developers isn’t just a technical decision—it’s a statement of respect for those who create from the periphery, with limited resources but powerful ideas,” said independent developer Freddy Castillo in a statement shared by Microsoft.

What Exactly Changed

The headline is stark: zero dollars to register as an individual. But the mechanics matter. Previously, a credit card was mandatory, which screened out potential publishers in regions where card ownership is low or trust in online payments is fragile. Now, identity is the gatekeeper. During onboarding, a government‑issued ID and a selfie must be submitted through Microsoft’s Partner Center. The system verifies that the person matches the document, and if successful, the developer can immediately reserve an app name and begin building.

This new flow is being rolled out gradually—Microsoft calls it a “flighted” rollout—so not every sign‑up path may yet offer the waiver. Developers are advised to start at the Microsoft Store developer marketing page to hit the updated experience. Company accounts still go through the legacy route and pay the $99 fee, which includes traditional business verification.

All supported app formats remain eligible: Win32, UWP, PWA, .NET MAUI, and Electron. MSIX packaging is recommended because the Store can apply its own signature to unsigned MSIX packages, removing the need for a separate code‑signing certificate for distribution. For non‑gaming apps, developers can either use Microsoft Commerce and its integrated payout and tax handling, or bring their own billing and keep 100% of revenue.

How to Onboard—Step by Step

1. Navigate to the Microsoft Store developer sign‑up page (preferably the marketing‑focused entrypoint).
2. Sign in with a personal Microsoft account (no corporate tax ID needed).
3. Choose “Individual” as the account type and fill in basic contact details and a publisher display name.
4. Complete the ID verification step—upload a government ID and take a selfie as prompted.
5. Once verified, go to Partner Center, reserve your app name, prepare your package (MSIX highly suggested), and submit for review.
6. Decide whether to integrate Microsoft Commerce or external billing for purchases.

The entire process, from cold start to live listing, can now happen without a credit card, a bank transfer, or any upfront financial outlay.

How It Stacks Up to Rival Platforms

Microsoft’s offering is now the only major mobile‑style app marketplace with no registration fee for individuals. That’s a powerful recruiting tool for students, hobbyists, open‑source contributors, and creators in low‑income regions.

Why Microsoft Did It—Strategic Calculus

The policy is not just a goodwill gesture. It amplifies three of Microsoft’s long‑term plays:

• Platform openness as a competitive weapon. By making the Store friction‑free for solo devs, Microsoft can grow its catalog faster than rivals, improving discoverability for users and reinforcing Windows as a hub for diverse software.
• Regulatory positioning. Global antitrust pressure on app stores is mounting. A zero‑fee path for individuals allows Microsoft to paint its store as the fair, developer‑friendly alternative, even as the EU’s Digital Markets Act and similar laws force changes at Apple.
• Ecosystem synergies. More apps inside the Store means stronger OS‑level integration (automatic updates, WinGet indexing, better search), a larger surface for enterprise management tools, and indirect revenue from services like Azure, Office 365, and editorial promotion slots.

The Upside for Developers and Users

Lower Entry Cost

Students, tinkerers, and creators in cash‑constrained markets can now publish experimental tools, utilities, and passion projects without the $19 ticket. This diversifies the Store’s app pool and could unearth hidden gems.

Simplified Signing

MSIX paired with Store signing means a solo developer doesn’t need to buy or manage an Authenticode certificate. Microsoft handles the trusted signature, making installations smoother for everyday users while enterprises can still use their own signing for side‑loaded packages.

Flexible Monetization

The ability to bring your own billing for non‑gaming apps is a revenue game‑changer. A niche productivity tool can charge users directly, avoid the 15%–30% platform cut, and still benefit from the Store’s distribution and discovery features.

Discoverability Leverage

Microsoft’s curated editorial picks, personalized recommendations, and AI‑driven “collections” give even small apps a shot at visibility. A well‑crafted store listing—sharp screenshots, concise description, privacy page—can attract downloads far beyond a developer’s own website.

Trust Badge

Apps that survive Store review and carry a Microsoft signature are less likely to trigger security warnings or be flagged by enterprise policies. That “verified by Microsoft” halo can be decisive for users who rightfully fear malware from random internet downloads.

The Risks and Trade‑offs

Privacy and Inclusivity of ID Verification

Swapping a credit card check for a government ID + selfie solves one exclusion problem but creates another. Not every potential developer has reliable access to a national identity document, and many will balk at handing over sensitive biometric data to a U.S. tech giant. Microsoft’s privacy statement should be read carefully—concerns about data retention, cross‑border transfer, and storage transparency are legitimate and not fully resolved by the current documentation.

Spam, Noise, and Moderation Burden

Free entry lowers the barrier for low‑effort or copycat submissions. App stores historically see a surge of junk when monetary gates vanish. Microsoft must scale its automated and human review systems to maintain quality; otherwise, user trust will erode, and good apps will be buried.

Uneven Rollout Friction

The flighted nature means confusion. A developer in a market where the free flow hasn’t landed might still see the $19 charge if they enter through the wrong portal. Microsoft’s docs suggest using the store marketing page, but until the rollout completes, inconsistent experiences will frustrate some would‑be publishers.

Discoverability Remains a Contest

Listing an app costs zero now, but getting noticed still demands effort. Store search, editorial featuring, and recommendation algorithms favor well‑optimized metadata, compelling visuals, and positive early engagement. A free registration doesn’t automatically generate downloads—it only removes the first financial hurdle.

External Billing Gray Areas

While external billing for non‑gaming apps is permitted, the exact category restrictions and buyer‑protection rules are nuanced. Developers who mishandle refunds or fail to comply with regional tax laws risk account sanctions. Microsoft’s support pages must be the final reference before implementing a direct‑payment flow.

Technical Implications and Developer Checklist

Packaging, Signing, and Delivery

• Adopt MSIX. It’s the recommended format for Store submission and enables Microsoft‑managed signing, simplifying certificate logistics.
• Integrate signing into CI/CD. If you use your own code signing for enterprise or side‑loaded deployments, use Azure SignTool with Azure Key Vault to secure private keys. Store signing helps consumer installs but doesn’t cover enterprise distribution scenarios.
• Choose a hosting strategy. Store‑hosted binaries streamline updates; self‑hosting gives you control over delivery cadence and is supported for both Win32 and MSIX apps.

Commerce and User Experience

• Pick a billing path early. If you plan to keep 100% of revenue, confirm your app category allows external billing and that you can handle taxes, receipts, and refunds. Test edge cases—failed payments, cross‑border refunds—before launch.
• Document support and refund flows. Users expect consistency. If you use external billing, clearly outline refund and support processes on your store listing and inside the app. Ambiguity leads to complaints and can damage Store trust.

Store Listing Optimization

• Treat the listing as a product page. Invest in 1–3 high‑resolution screenshots, a short explainer video if possible, a crisp value proposition, and thorough privacy/terms links. Editorial curators favor submissions that look finished.
• Reserve the app name early. Even before your code is ready, lock in your display name via Partner Center to prevent collisions.

Practical Guidance by Developer Profile

Hobbyists and Students

Use the new individual flow to publish small utilities, homework trackers, or experimental tools at no cost. Before submitting your ID, ensure you’re comfortable with Microsoft’s privacy handling—if not, consider waiting for more transparency or using alternative distribution.

Indie Commercial Teams

Decide early whether Microsoft Commerce or external billing gives you better margins and control. If you go external, invest heavily in customer support infrastructure and test refunds end‑to‑end. Optimize your store listing as if it were the landing page of a product launch.

Enterprise or Company Publishers

Remain on the company account path with its $99 fee and standard business verification. If you have side projects by employees, consider whether they merit a separate individual account, but keep governance and IP ownership in mind—tools built on company time may not belong in a personal store channel.

What’s Still Unclear

• ID data handling details. Microsoft’s developer docs describe the verification process but do not publish granular timelines for data retention or independent privacy assessments for every market. Developers with strong privacy demands should seek legal counsel or support clarification.
• Reach numbers. The widely cited 250 million monthly active Store users appears in Microsoft materials and press coverage, but such metrics evolve quarterly. Business planners should check the latest investor or press releases for the most current figure.

A Verdict—Progress, but Vigilance Required

Microsoft’s decision to scrap the individual registration fee is a concrete, and strategically smart, lowering of the drawbridge. It erases a real monetary barrier, strips away the credit‑card dependency that locked out many creators, and aligns with the company’s narrative of an open, developer‑respectful Windows ecosystem. The Store’s support for diverse app frameworks and external billing further cements its role as a versatile distribution hub, not a walled garden.

But the price of zero dollars is shifted onto identity verification. That trade‑off carries privacy and inclusivity risks that the developer community must interrogate. The flighted rollout, while operationally prudent, will cause short‑term confusion. And the inevitable influx of new submissions will test Microsoft’s moderation muscle.

The zero‑fee era is a strong step forward. Whether it transforms the Microsoft Store into a thriving, diverse bazaar or simply floods it with noise depends on how well Microsoft balances openness with quality control—and on how wisely developers use the opportunity.

Quick‑Reference Checklist

• Confirm your market has the flighted free onboarding (start at the Store developer marketing page).
• Prepare an MSIX pipeline and CI/CD signing integration (Azure SignTool/Azure Key Vault).
• Choose Microsoft Commerce or external billing and rigorously test refund and tax flows.
• Optimize your Store listing with professional screenshots, a tight value proposition, and clear privacy text.
• Assess privacy implications of ID verification and consult Microsoft’s docs or support for clarity on data handling.