Microsoft has eliminated the $99 registration fee for company developer accounts in the Microsoft Store, effective immediately across supported onboarding flows. The shift comes alongside mandatory Entra ID integration for organizational accounts and a streamlined verification process that slashes approval times from days to hours.

Developers registering a new company account through the updated Partner Center wizard will no longer encounter the credit card authorization screen that previously blocked casual and indie teams. Instead, Microsoft now validates business identities using existing Entra ID tenants or a lightweight directory creation step. Individual accounts remain free, as they have been since 2021, but the company account change removes the last significant financial barrier to publishing Win32, PWA, UWP, and packaged desktop apps on the Store.

What Changed in the Onboarding Flow

The most visible difference appears on the account type selection page. Previously, developers had to choose between Individual and Company, with the latter requiring a $99 payment. Now, the Company option splits into two sub-paths: “Company – Entra ID directed” and “Company – New tenant.” Both lead to zero-cost registration.

The Entra ID path assumes the developer already has a Microsoft Entra ID tenant (formerly Azure Active Directory) linked to a verified domain. Partner Center queries the tenant in real time, confirms domain ownership, and pulls business metadata automatically. If the tenant passes validation, the account approval becomes nearly instantaneous—often completing in under ten minutes.

For developers without an existing Entra ID tenant, the new tenant path creates one on the fly using the provided business email and organization details. Microsoft runs a lightweight business verification against public registries and Dun & Bradstreet, then provisions a basic Entra ID directory at no cost. This path typically completes within 24 hours, compared to the previous 3–7 day manual review window. Microsoft says over 80% of new tenant requests now finalize in under six hours.

Why Microsoft Is Making Company Accounts Free

Three forces pushed this decision. First, the Windows developer ecosystem needs more enterprise-grade applications. Microsoft Store data shows that company accounts publish 76% of the revenue-generating apps but represent only 12% of total registered developers. The fee discouraged smaller ISVs and internal tool publishers who balked at paying upfront before seeing any return. Second, Apple’s App Store charges $99/year for its developer program, but Microsoft wants to differentiate by offering a free, no-recurring-cost model that appeals to line-of-business developers. Third, the migration to Entra ID aligns with the company’s broader security strategy: every organizational identity in the Store now ties to a tenant that supports conditional access, multi-factor authentication, and policy governance.

The move also simplifies compliance for enterprises. IT administrators can now manage Store publisher roles through Entra ID groups, grant delegated access to submission and analytics dashboards, and revoke permissions instantly when an employee leaves the organization. Partner Center already supported tenant-backed accounts, but the old registration process often created disconnects where a company paid with a personal credit card and then struggled to attach its corporate tenant later. The new flow resolves that structural tension.

Verification Enhancements That Cut Wait Times

Behind the scenes, Microsoft retooled its business verification engine to reduce false negatives that previously flagged many legitimate companies. The system now cross-references data from three primary sources: the provided Entra ID tenant’s verified domains, local business registries in over 140 countries, and a partnership with a major commercial data provider for real-time D-U-N-S number lookups. If all three align, the verification completes automatically.

Developers can monitor the status in a redesigned Partner Center dashboard that shows a step-by-step progress tracker. In the legacy flow, verification failed silently, and support tickets took days to resolve. Now, if an inconsistency arises—such as a domain mismatch between the Entra tenant and the submitted company name—the dashboard highlights the exact field and recommends a corrective action, like updating the tenant’s primary domain or sharing additional documentation.

Microsoft also introduced a fast-track appeal process for companies that fail automated checks. Developers can upload a scanned business license, tax registration certificate, or utility bill directly in Partner Center. A dedicated verification team reviews these documents within four business hours during weekdays. This replaces the old email-based appeal that averaged eight days.

Entra ID Integration: Mandatory for New Company Accounts

As part of the zero-fee rollout, all new company accounts created on or after May 7, 2026 must associate with a Microsoft Entra ID tenant. Individual accounts are unaffected, and existing company accounts that registered before the cutoff date can continue using their current credentials indefinitely. However, Microsoft encourages those legacy accounts to link a tenant voluntarily, warning that future security features—such as publisher attestation for AI-generated content—may require tenant-backed identities.

For companies already using Microsoft 365 or Azure, the integration is seamless: Partner Center detects the tenant from the signed-in user’s account and pre-populates organization details. For those new to the Microsoft cloud, the new tenant creation flow includes a guided wizard that sets up a default directory, a verifiable domain (via a TXT record challenge), and an admin account. The directory comes with a free-tier Entra ID license sufficient for Store publishing; no Azure subscription is required.

Permissions and Role Management

The shift to tenant-based authentication unlocks granular role-based access control within Partner Center. Companies can define publisher roles—such as App Manager, Financial Contributor, and Developer—and map them to Entra ID security groups. For example, a finance team member can be granted access only to payout and tax profile pages without seeing app submission data. This replaces the previous all-or-nothing account owner model and aligns with least-privilege principles.

Multifactor authentication (MFA) also becomes easier to enforce. Because Entra ID policies govern sign-in, administrators can require phishing-resistant MFA, set session timeouts, and trigger access reviews for users with privileged publisher roles. Microsoft says this addresses the number one security concern raised by enterprise developers in the Windows Developer Feedback Hub: 62% of business respondents wanted MFA enforcement on publisher accounts, but only 11% had implemented it manually.

Step-by-Step: How to Register a Free Company Account

The process now involves four stages, completed entirely within Partner Center:

  • Initiate registration: Navigate to partner.microsoft.com/dashboard, sign in with a Microsoft account that has an Entra ID presence, and select “Company account – Entra ID directed” or “Company account – New tenant.”
  • Confirm business identity: For Entra ID paths, verify the tenant and domain; for new tenants, provide legal business name, country/region, and a valid email address on a corporate domain.
  • Complete verification: The system runs automated checks and prompts for additional documentation if needed.
  • Accept publisher agreement: Review and sign the updated Microsoft Store Publisher Agreement, which now includes clauses related to AI-generated content disclosure and Entra ID data processing.

Upon approval, the account gains immediate access to the Store submission pipeline, analytics, and the new AI-assisted listing optimization tool. There is no payout threshold change—developers still receive payments when earned revenue exceeds $50 in a calendar quarter.

Implications for Existing Developers

Current company account holders who paid the $99 fee will not receive a refund. Microsoft’s policy states that fees paid before the effective date are non-refundable, and the change is not retroactive. However, these developers can convert their accounts to the Entra ID model at no cost by linking a tenant. Doing so enables the enhanced security features and faster future verifications, but does not alter payout timelines or app catalog listings.

Developers with multiple company accounts—a common scenario for agencies managing separate client storefronts—must now ensure each account ties to a unique Entra ID tenant. Microsoft updated its account consolidation tool to allow merging of two tenant-backed accounts if both pass a domain-ownership challenge, though the feature is in public preview and requires a support ticket.

Perhaps most significantly, the free-account model resets competitive dynamics for Windows app distribution. Previously, the $99 barrier led some developers to bypass the Store entirely and distribute MSIX packages via standalone websites or third-party repositories. With the fee removed, those developers may reconsider the Store’s built-in update mechanism, consumer trust signals, and potential inclusion in the Microsoft Store’s curated collections.

Reaction from the Developer Community

Early feedback from Windows developer forums has been mixed but leaning positive. A thread on a popular community site saw several ISVs celebrate the cost elimination, with one poster noting: “We held off publishing our line-of-business tool for two years because we couldn’t expense the $99. Now we’re live in 24 hours.” Another developer appreciated the Entra ID linkage: “Managing Store publisher credentials through our existing Azure AD is a no-brainer for compliance.”

Criticism focused on two points. First, the mandatory nature of Entra ID for new accounts frustrates small limited-liability companies that use Google Workspace or other non-Microsoft identity providers. Those developers must create and manage a separate Entra ID tenant solely for Store publishing, which some view as unnecessary overhead. Microsoft countered that the free tenant requires minimal maintenance—no additional team members or licensing—and can be left dormant between submissions. Second, the $99 fee refund question generated heated discussion, with several developers calling for a goodwill credit towards app-promotion campaigns. Microsoft has not announced any such program.

The Bigger Picture: AI, Security, and the Store Vision

This pricing change doesn’t exist in a vacuum. Over the past eighteen months, Microsoft has signaled a Store evolution that intertwines AI-assisted app discovery, stricter content policies, and enterprise-grade security. In March 2026, the company launched an AI tool that scans app metadata and user reviews to generate optimized listing text; it requires tenant-backed publisher identities to prevent abuse. In June, Store started surfacing “Enterprise Ready” badges for apps that meet specific criteria around data handling, authentication, and update cadence—badges that rely on Entra ID policies for verification.

By making company accounts free, Microsoft aims to flood the Store with a new wave of productivity apps, ISV utilities, and internally developed corporate tools. The Store client in Windows 12—expected later this year—will feature a redesigned “Work Tab” that surfaces approved apps based on an organization’s Entra ID group memberships and Intune policies. Free company accounts are a prerequisite for developers targeting that curated enterprise shelf.

Competitively, the move pressures alternative Windows app stores. Valve’s Steam primarily serves games, but the Epic Games Store and various niche marketplaces charge listing fees or revenue shares that now look steeper compared to Microsoft’s 0% store fee for Win32 apps using third-party commerce (and a 15% cut for apps using Microsoft’s commerce). By removing the upfront registration fee, Microsoft essentially says: publish your app, pay us nothing unless you use our payment processor.

The Entra ID mandate also deepens Microsoft’s defensive moat around organizational identity. Every company publishing on the Store now becomes at least a minimal Entra ID customer, opening a door for future upsell into Microsoft 365, Azure AD Premium, or Endpoint Manager. While Microsoft insists the free tenant comes with no strings, the strategic alignment is undeniable.

What This Means for Windows Users

End users will likely notice a gradual increase in the variety of apps available, particularly in the business and productivity categories. The Store’s “Curation & Verification” policy already requires apps to meet baseline quality and safety standards, and the Entra ID linkage adds another layer of publisher accountability. If an app behaves maliciously, Microsoft can trace its publisher back to a verified business identity, not an anonymous personal email.

Enterprise users, especially those on managed Windows devices, will benefit from tighter integration between the Store, Entra ID, and mobile device management tools. IT admins can set policies that allow users to install only apps from verified company publishers, with the option to block all others. This brings the Store closer to the managed software distribution model that enterprises have long demanded, without forcing them into a separate Microsoft Store for Business portal that was deprecated in 2023.

For consumers, the removal of the developer fee could accelerate the trend of companies offering free companion apps for their hardware, services, or web platforms. Think of a printer manufacturer that previously declined to list its driver app due to the registration cost; now, that barrier is gone. Over time, the Store may become a more complete catalog of Windows software, reducing reliance on sketchy download sites.

Moving Forward

Microsoft plans to iterate on the verification engine throughout the year, with a public roadmap item aimed at reducing manual document reviews to less than 60 minutes for 95% of cases by Q4 2026. A beta feature allowing developers to pre-validate their business identity before starting the submission flow is also in the works, which would let ISVs enter partner.microsoft.com, complete verification once, and then focus solely on app packaging.

No changes to individual accounts or the existing payout structure have been announced, though the Publisher Agreement update that accompanied the free account launch includes clearer language around tax withholding and digital service taxes in jurisdictions where they apply. Developers should review that agreement carefully, especially the clause that mandates compliance with Microsoft’s AI content policy, which is expected to gain enforcement teeth in a future Store quality update.

For now, the takeaway is unambiguous: publishing a professional Windows app on the Microsoft Store no longer costs a cent upfront. The combination of free accounts, Entra ID integration, and fast verification removes long-standing friction points and signals that Microsoft is serious about making the Store a hub for both consumer and business software. If the company maintains this trajectory, the Windows app ecosystem may finally shed its reputation as a distribution afterthought.