The Microsoft Store Appeal Service Agency That Reinstates the Developer Accounts Other Reinstatement Agencies Give Up On.

If Microsoft Store failed your submission or pulled your app, every day it stays down costs you downloads and revenue. We go through your certification report and your whole Partner Center account, find what actually failed and answer every policy line by number. Start with a free assessment and know where you stand before you pay.

97%Peak reinstatement rate
10,000+Cases resolved
145+Platforms covered
Free assessment before you pay anythingEvery reply mapped to the Store Policy number in the reportAttorney-reviewed letters when a case needs legal weight
Partner Center, reviewed by usPick the product with the problem
Partner CenterApps and games
Certification report

Notes Pro

Reviewed by the Store certification team

Fix each line, then resubmit with notes mapped to the report.

Grade ModerateSend us this case →
Note

Pick the product that is stuck. The report shows which numbered policy lines failed, and each line gets its own fix.

As featured in
Fox BusinessBusiness InsiderCBS NewsMarketWatchHuffPostInternational Business Times
What we recover on the Microsoft Store

Get Your Microsoft Store Apps Certified and Back in the Store

A failed certification, a removed product and a payout hold all sit in different parts of Partner Center. We work all of it at once.

Microsoft Store · Partner Center, Certification report
BeforeCertification failed
SubmissionBlocked
Security scanFlagged
Notes for certificationGeneric
All lines 42Passed 39Failed 3
Policy lineSectionResult
Security, unsafe dependencyFailed
Technical, crash on launchFailed
Listing accuracyFailed
Privacy policyWarning
Age ratingPassed
AfterCertified
SubmissionPublished
Security scanClean
Notes for certificationMapped per line
All lines 42Passed 42Failed 0
Policy lineSectionResult
Security, unsafe dependencyPassed
Technical, crash on launchPassed
Listing accuracyPassed
Privacy policyPassed
Age ratingPassed

What changesEvery failed line fixed and answered in the notes, so the package certifies and the update ships.

Microsoft Store · Partner Center, Apps and games
Before1 removed
New acquisitionsStopped
ListingHidden
Open notices1
All 6In the Store 5Removed 1
ProductStore IDStatus
Photo editorRemoved
Photo editor for XboxUpdate blocked
Screen recorderIn the Store
File converterIn the Store
Note takerIn the Store
AfterAll in Store
New acquisitionsOpen
ListingLive
Open notices0
All 6In the Store 6Removed 0
ProductStore IDStatus
Photo editorIn the Store
Photo editor for XboxIn the Store
Screen recorderIn the Store
File converterIn the Store
Note takerIn the Store

What changesThe removed product back in the Store, with the listing, privacy policy, and package brought in line with the policies it was removed under.

Microsoft Store · Partner Center, Payout summary
BeforePayout on hold
Tax profileIncomplete
Payout profileIncomplete
Next payoutHeld
Payout balanceOn hold
Payout period Held
Payout period Held
Payout period Held
AfterPaid
Tax profileComplete
Payout profileComplete
Next payoutScheduled
Payout balanceReleased
Payout period Paid
Payout period Paid
Payout period Scheduled

What changesPayouts released once the tax and payout profiles are complete and any account action is cleared through the right support path.

Drag the handle to compare. Illustrative figures.
Who reviews your submission

Who at Microsoft Reviews Your App and Developer Account

Certification, policy review, account integrity, IP notices and payouts all run against the same developer account. Our people have sat on the other side of these reviews. Tap a team to see what it wants from you.

The teams running on your accountSelect a process
Task Manager
ProcessesPerformanceDetailsServices
NameChecksActivityStatus
Properties

Store certification

Tests security, technical function and content on every submission, then issues the certification report.

Needs to see

A submission where every failed line in the report is fixed and noted.

How we answer it

We answer each line in the report with the fix and where to see it.

Note

Six Microsoft teams run against a developer account at once. Select one to see what it checks and what it needs.

Your notice

What Your Microsoft Store Notice Means

The notice tells you what Microsoft flagged. It rarely tells you why. Pick the notice that matches yours and see what sets it off, what Microsoft can prove and what it’s only assuming.

SEC
Certification report, failed policy lines

Certification failed

Reviewed by the Store certification team

Typical grade: Moderate

What sets it off

  • A package that crashes or fails a technical test
  • Listing metadata that does not match the product
  • Missing required declarations

What they can prove

  • The numbered policy lines that failed
  • The device family tested

What they infer

  • That the product is not ready for customers

Our pathway

  1. 1Read every failed line on the report
  2. 2Fix each one in the package or listing
  3. 3Write notes that answer each line by number
  4. 4Resubmit once
A certification report is a checklist. Answer every line, by number, and it passes.
Security, unsafe behavior

Security finding

Reviewed by the Store certification team

Typical grade: Difficult

What sets it off

  • A bundled library that matches an unsafe behavior
  • Code the scan cannot account for

What they can prove

  • The scan result on the package
  • The library that matched

What they infer

  • That the product may harm the device or the user

Our pathway

  1. 1Identify the flagged dependency
  2. 2Rebuild without it or replace it
  3. 3Rescan and keep the clean result
  4. 4Resubmit with the replacement named
Security findings are fixed in the build, not argued in the notes.
NOTICE
Removal under the Microsoft Store Policies

Product removed

Reviewed by the Policy and content review team

Typical grade: Difficult

What sets it off

  • Listing claims the product does not deliver
  • Content or function outside the policies

What they can prove

  • The listing and the product at the time
  • The policy line cited

What they infer

  • That customers were misled

Our pathway

  1. 1Match the removal to the policy line cited
  2. 2Fix the product and listing together
  3. 3Document the change
  4. 4Request review through Partner Center support
A removal names a policy. We answer that policy and show the product that meets it.
Personal information requirements

Privacy and data

Reviewed by the Policy and content review team

Typical grade: Moderate

What sets it off

  • Personal information accessed without a privacy policy
  • Capabilities declared that the product does not need

What they can prove

  • The declared capabilities
  • The listing privacy policy field

What they infer

  • That data is collected without disclosure

Our pathway

  1. 1Publish a privacy policy that matches the product
  2. 2Remove unused capabilities
  3. 3Disclose what is collected and why
  4. 4Resubmit with the change noted
Declare only what the product uses, and say what it does with it.
Copyright or trademark notice

IP complaint

Reviewed by the IP and notice handling team

Typical grade: Difficult

What sets it off

  • A rights owner notice on the product or listing
  • A name or icon close to a registered mark

What they can prove

  • The notice and the content it names
  • The rights owner on file

What they infer

  • That the claim is valid unless answered

Our pathway

  1. 1Check whether the claim actually covers the product
  2. 2Replace any content that is not yours
  3. 3Answer through the notice channel
  4. 4Seek a retraction where the claim is wrong
Most IP removals clear when the content is replaced or the claim is withdrawn.
$HELD
Payout and tax profile hold

Payout hold

Reviewed by the Payout and tax team

Typical grade: Moderate

What sets it off

  • An incomplete tax or payout profile
  • An account action under review

What they can prove

  • The missing profile fields
  • The balance held

What they infer

  • That the payee is not yet verified

Our pathway

  1. 1Complete the tax profile
  2. 2Complete the payout profile
  3. 3Clear any account action first
  4. 4Confirm the next payout
Most payout holds are a profile field, not a penalty.
App Developer Agreement, account action

Account closed

Reviewed by the Partner Center account integrity team

Typical grade: Hell 1 to 2

What sets it off

  • Links to a closed developer account
  • Rating or review manipulation
  • Repeated serious violations

What they can prove

  • Shared identifiers such as a signing certificate
  • The violation history

What they infer

  • Common control with an account that was closed

Our pathway

  1. 1Map every shared identifier
  2. 2Document contractors and build history
  3. 3Re-sign and separate what should not be shared
  4. 4One complete request through support
A shared certificate usually means a shared contractor. We prove it on paper.
Policy lookup

What Each Microsoft Store Policy Number Means

Your certification report cites numbered sections of the Microsoft Store Policies. Each failed line needs its own fix and its own note. Look up the lines on yours.

Look up a failed lineType a policy number
Run

Type the policy number from your certification report, and we will tell you what it checks and how we answer it.

CancelBrowse
Microsoft Store Policies 10.2

Security

What certification checks

How we answer the line

The note we attach

Section names come from the current Microsoft Store Policies. The summaries are ours. Your report’s wording is what counts.

Note

Every failed line on a certification report carries a policy number. Type one and see what it checks and how we answer it.

How Microsoft’s teams see your account

How Microsoft Decides Whether to Certify or Reinstate Your App

Microsoft doesn’t read your notes or your appeal on their own. It reads them against your whole account: your submission history, your scan results, your payout profile and every appeal you’ve sent before. We write yours to answer what Microsoft is actually weighing.

!

Potentially how it looks. A fictitious reconstruction built from our research and quantified only from cases we have handled. It is not a Microsoft Store screen or tool. Names, IDs, and records are invented or redacted.

Developer recordPublisher ID Windows and XboxPublisher Open investigation
Product removed from the Store. Submission blocked pending policy review.
Annotated: do not certify without a clean scan.

Developer summary

Certification findings

Every failed line on the report gets answered by number. Lines that passed are left alone, so nothing new gets flagged.

Identity

Standing

Controls

Apps and gamesCertification reportPayout summaryAccount settings
AccountPayout accountTax profileContact emailSigning certificateCompany detailsDeviceNetworkPhone
This accountProduct removed232
Developer 02Closed
Developer 03Active
Developer 04Active
Developer 05Active
Developer 06Fraud flag
Developer 07Active

Showing 7 of 14 related records. Outsourced builds create links that look like shared control. We document who built what, and when.

SearchShow 10 entries
SubmissionResultFailed linesNotes
Showing 1 to 7 of 8 entries123...Next
SearchShow 10 entries
FamilyTestedResultAction
Failed certification lines per submissionWithin targetBreachThreshold

S1S2S3S4S5S6S7S8

We rebuild this from your own certification reports.

SearchShow 10 entries
ActionLast30 dayLifetime
Showing 1 to 9 of 47 entries123...Next
SearchShow 10 entries
CaseStatusQueueUpdated
Showing 1 to 5 of 9 entries123...Next
SearchShow 10 entries
WhenBrowser, OSDevice IDNetworkTime zoneLocation
Showing 1 to 6 of 132 entries123...Next
How the team reads itTap any line in the record

Every flag above is something a reviewer weighs before they read a word of your appeal. Tap one to see what it means and what we do with it.

Step by step

How to Fix a Failed Microsoft Store Certification

Step through the Partner Center submission page your app moves through. Below is how we work your case, start to finish.

The submission, section by sectionStep through the submission
Notes Pro, illustrative

Submission 2

Certification failed
Pricing and availabilityMarkets, price, visibilityComplete
PropertiesCategory, privacy policy URLComplete
Age ratingsRating questionnaireComplete
PackagesPackage and bundled filesFailed, 10.2
Store listingsDescription and screenshotsFailed, 10.1
Submission optionsNotes for certificationNo notes
Submit to the StoreSections as named in Partner Center
Step 1 of 5

We read the certification report

Your certification report, submission history, account notices and payout status. Nothing gets written until we see the full picture.

Changed on the page
This step produces
Certification reportSubmission historyAccount noticesPayout status
Note

This is the Partner Center submission page. Step through and watch each section move from failed to ready.

  1. 1
    Intake

    We read the certification report

    Your certification report, submission history, account notices and payout status. Nothing gets written until we see the full picture.

    • Certification report
    • Submission history
    • Account notices
    • Payout status
  2. 2
    Trigger

    We reproduce each finding

    We test on the device family that failed, scan the package and check the listing, so every fix holds up when certification runs it again.

    • Device repro
    • Dependency scan
    • Listing review
    • Owning team
  3. 3
    Grade

    We grade the case before you pay

    You’ll know how hard your case is and why. If we can’t help, we tell you before you pay.

    • Case grade
    • Risk notes
    • Package changes needed
    • Working timeline range
  4. 4
    Write

    We write to each policy line

    Notes or an appeal that answer each failed policy line with the fix and the proof. A second specialist reviews it before it’s filed.

    • Notes or appeal
    • Line by line map
    • Exhibit index
    • Quality review
  5. 5
    Escalate

    We carry it to a decision

    Every reply from Microsoft tells us something. If it’s denied, we rebuild from the reason given. We never resend the same submission.

    • Submission log
    • Reply analysis
    • Support case plan
    • Payout tracker
If certification says no again

The Microsoft Store escalation path

01

Resubmission with notes

A fixed package with notes to certification for every failed line.

Most certification cases end here.
02

Store appeal

An appeal to reportapp@microsoft.com for a removed product or a finding you dispute.

Written to the policy number, with exhibits.
03

Partner Center support case

A focused support case when a complete appeal stalls or the account itself is involved.

Used for routing and status, not reargument.
04

Payout track

Payouts on hold, worked with a complete payout and tax profile behind them.

Kept separate from the policy dispute.
05

Attorney pre-escalation notice

When a case is stuck and the facts are on your side, an attorney-reviewed letter under the App Developer Agreement puts it on record. We only use it when the case calls for it.

The top rung. Attorney-reviewed, and used only when the case calls for it.
Stuck

Struggling to get it back on your own?

Book a call and we’ll map out your next move. Most apps that keep failing are failing the same line with a new build.

Your case

Check Where Your Microsoft Store Case Stands

Answer four quick questions and see how hard your case looks and what’s still missing. Nothing is sent until you hit submit.

  1. 1What did you receive
  2. 2Where does it stand
  3. 3What applies
  4. 4What you have

What did Microsoft Store send you

Where does the case stand today

Tick everything that applies

Which of these can you get

Preliminary gradeModerate
Team that reviews it
What they check
Next step
Still missing

A first look from four answers. The real grade comes after we review your notice and your file.

Your case file

Microsoft Store case, draft

NoticeNot chosen yet
StatusNot chosen yet
Risk signalsNone ticked
DocumentsNot checked yet
GOT SUSPENDED?UnmatchedMatched
Matched case
97%Peak reinstatement rate
Drag to rotate
Why the hard cases come here

We are the ones developers come to when every other agency and law firm has already failed.

Most developers find us after their resubmissions failed and someone else already tried. Every failed submission and denied appeal stays on the account, so the next one has to be built differently. Our team has worked inside these platforms and knows what each review is measuring. That’s how we’ve resolved more than 10,000 cases.

How hard is your case

Know How Hard Your Microsoft Store Case Is Before You Pay

Toggle what’s true for your account and watch the grade change. The more damage on the account, the more work it takes, and your price follows. If there’s no real path, we tell you before you pay.

Risk signals
MODModerate
Moderate
What the team sees
How we work it

Moderate

One failed certification line or a profile gap on a clean account. Fix the line and resubmit with notes tied to the report.

Difficult

Technical or security lines that keep failing because the real fix never went in. We reproduce it, rebuild, rescan and answer each line.

Hell 1

A removed product with a failed resubmission on file. A clean package and an appeal that answers both the removal and the report.

Hell 2

A rights holder claim against your product or its name. The withdrawal request and the listing fix run together.

Hell 3

Conduct Microsoft reads as deliberate. Stop the practice, document the change and appeal with proof.

Hell 4

Links to a closed developer account and closed cases on file. A full account map and one complete appeal through the right support path.

Hell 5

A closed account with revenue at stake. The reconsideration and the payout work run at the same time.

Hell 6

No human path left. We decline before you pay.

Hell 7

No real option left. We decline before you pay.

What you get

What’s Included in Your Microsoft Store Appeal

Everything we file for you, every reply Microsoft sends back and a plan to keep your next release from failing.

The case file, one Properties tab per deliverablePick a tab
Notes Pro case file Properties
Policy 10.1, Accurate Representation
Change: screenshots 2 and 3 now labeled
as Pro tier features.
Where to verify: Store listing, screenshots.
Policy 10.2, Security
Change: bundled updater removed. Updates
now ship through the Store only.
Where to verify: package contents.
Test account: in the submission notes.
ToMicrosoft Store, through Partner Center
ReRemoval of Planner, policy 10.1

The listing cited in the removal described a feature that shipped in the build under review. We attach the build, the listing history, and a screen recording of the feature.

We ask that the product be reinstated, and we list each change made since the removal.

Exhibit AExhibit BExhibit C
FileScanAction
Notes.exeCleanKept
updater.dllFlaggedRemoved
runtimeCleanKept
AppxManifest.xml3 of 5 capabilities usedTrimmed
Clean packageRescanned after rebuild
Payout profile

Legal nameMatches

Bank countryMatches

Account holderCorrected

Tax profile

Legal nameMatches

Tax formResubmitted

AddressMatches

Identity

Publisher nameMatches

VerificationPassed

ContactUpdated

CheckDesktopXbox
Launches and stays responsive
Test account signs in
Privacy policy link loads
Every capability has a visible use
Screenshots match this build

Device families shown are illustrative. We check the ones your package declares.

OKCancelApply
Deliverable 1 of 5

Notes to certification

Notes that answer each failed policy number, line by line.

Contents shown are an illustrative example file.

Note

The whole case file opens as one Properties sheet. Each tab is one deliverable. Pick a tab to inspect it.

01

Notes to certification

Notes that answer each failed policy number, line by line.

02

Store appeal

For removals and account actions, written to the policy or agreement Microsoft cited.

03

Package audit

Every dependency, capability and scan result behind the clean package.

04

Profile reconciliation

Your payout, tax and identity profiles lined up so they match.

05

Release checklist

The checks to run on every device family before you submit again.

Your case file

What Goes Into a Strong Microsoft Store Appeal

Microsoft wants to see the cause, the fix and the proof behind both. Tap a document to see an example.

Microsoft Store case types

Microsoft Store Case Types and Who Reviews Them

Pick a category, then open any case to see who reviews it, what sets it off and what we send.

Who reviews Microsoft Store cases

S

Store certification

Tests security, technical function and content on every submission, then issues the certification report.

A submission where every failed line in the report is fixed and noted.

Policy number citedSecurity and malware scanTechnical complianceContent rating
P

Policy and content review

Applies the Microsoft Store Policies to listings and products, including removal of live products.

A product and listing that match, with any flagged content removed.

Product value and functionListing accuracyContent policiesPersonal information handling
P

Partner Center account integrity

Reviews developer account actions for fraud, manipulation, and linked accounts.

Records that explain the flagged activity and prove independence where relevant.

Account historyLinked accountsPayment identityRating manipulation
I

IP and notice handling

Handles rights holder notices about Store products.

Proof of rights or a withdrawal, and a corrected listing.

Complaint typeRights holderName and iconOwnership proof
P

Payout and tax

Manages payout accounts, tax profiles, and payout holds.

Complete payout and tax profiles that match the account entity.

Payout account statusTax profileIdentity verificationRefund exposure
P

Partner Center support and Legal

Support cases in Partner Center and Microsoft’s legal channels above them.

A finished record showing the process was followed.

Complete recordAgreement termsRevenue at stakePrior cases

Certification failures

Microsoft Store noticeTechnical and crash failures

Technical and crash failures

We reproduce on the device family and fix.

Reviewed by

Store certification

What triggers it

A crash, hang, or failure on a targeted device family.

What we submit

The fixed package with notes naming the device tested and the change made.

Microsoft Store noticeSecurity findings

Security findings

We audit dependencies and ship a clean package.

Reviewed by

Store certification

What triggers it

A scan hit on the package or a bundled dependency.

What we submit

A clean rebuild, the scan result, and the dependency that was removed.

Microsoft Store noticeMetadata and listing

Metadata and listing

We align listing claims with the product.

Reviewed by

Store certification

What triggers it

A description, screenshot, or name that does not match the product.

What we submit

A corrected listing built from the certified package.

Microsoft Store noticeMinimum value

Minimum value

We document real function or consolidate thin products.

Reviewed by

Store certification

What triggers it

A product that lacks distinct function or value.

What we submit

The added function and a listing that states it plainly.

Microsoft Store noticePackage identity mismatch

Package identity mismatch

The package name or publisher does not match what Partner Center reserved.

Reviewed by

Store certification

What triggers it

A package identity that differs from the reserved product.

What we submit

A package built with the correct identity values.

Microsoft Store noticeUnsupported device family

Unsupported device family

The product targets a family it was never tested on.

Reviewed by

Store certification

What triggers it

A failure on a device family the product claims to support.

What we submit

Targets narrowed to supported families and a clean test result.

Removals

Microsoft Store noticePolicy removal

Policy removal

We cure the issue and appeal with evidence.

Reviewed by

Policy and content review

What triggers it

A live product that breaks a Store Policy.

What we submit

The cured product and an appeal citing the policy it now meets.

Microsoft Store noticeCopyright takedown

Copyright takedown

We establish rights or replace assets.

Reviewed by

IP and notice handling

What triggers it

A rights holder notice on content inside the product.

What we submit

Proof of rights or replacement content, and a withdrawal request.

Microsoft Store noticeTrademark takedown

Trademark takedown

We work the withdrawal and rebrand where needed.

Reviewed by

IP and notice handling

What triggers it

A name or icon claimed by a mark owner.

What we submit

Trademark filings or a renamed listing, run with a withdrawal request.

Microsoft Store noticeRemoval for inactivity or outdated content

Removal for inactivity or outdated content

A product no longer meets current requirements.

Reviewed by

Policy and content review

What triggers it

A product that has not been updated to current policy.

What we submit

An updated package and listing that meet current policy.

Partner Center account

Microsoft Store noticeAccount closure

Account closure

We map the record and appeal to the agreement term.

Reviewed by

Partner Center account integrity

What triggers it

Conduct or links that led to an account action.

What we submit

A mapped record, corrective actions, and exhibits in one appeal.

Microsoft Store noticeLinked account action

Linked account action

We prove independence with records.

Reviewed by

Partner Center account integrity

What triggers it

Shared payout, certificate, or contact details with another account.

What we submit

An identifier map and proof of independence for each link.

Microsoft Store noticeRating or review manipulation

Rating or review manipulation

We end the practice and document it.

Reviewed by

Partner Center account integrity

What triggers it

Ratings or reviews that look incentivized or coordinated.

What we submit

The practice removed and the record showing it stopped.

Microsoft Store noticeCompany verification failure

Company verification failure

The company account cannot be verified against its documents.

Reviewed by

Partner Center account integrity

What triggers it

Company details that do not match the verification source.

What we submit

Registration documents and contact details that match exactly.

Privacy and data

Microsoft Store noticePrivacy policy requirement

Privacy policy requirement

We add a policy that matches data use.

Reviewed by

Store certification

What triggers it

Personal information accessed without a privacy policy.

What we submit

A linked privacy policy that describes what the product collects.

Microsoft Store noticePersonal information handling

Personal information handling

We fix collection and disclosure flows.

Reviewed by

Policy and content review

What triggers it

Data collected or shared beyond what the product needs.

What we submit

The corrected data flow and updated disclosures.

Microsoft Store noticeCapability declarations

Capability declarations

We justify or remove restricted capabilities.

Reviewed by

Store certification

What triggers it

Declared capabilities the product does not use or explain.

What we submit

A manifest trimmed to what the product uses, with notes.

Microsoft Store noticeChildren's data concern

Children's data concern

The product may be used by children without the right handling.

Reviewed by

Policy and content review

What triggers it

An age rating or audience that does not match data practices.

What we submit

Corrected age rating and data handling for younger users.

Payouts and escalation

Microsoft Store noticePayout hold

Payout hold

We complete payout and tax profiles.

Reviewed by

Payout and tax

What triggers it

Incomplete payout or tax profiles, or a verification gap.

What we submit

Complete profiles matching the account entity and a support case.

Microsoft Store noticeIdentity verification

Identity verification

We reconcile account and entity data.

Reviewed by

Payout and tax

What triggers it

Account details that do not match verification documents.

What we submit

Matching documents submitted once after an audit.

Microsoft Store noticeLegal letter

Legal letter

Attorney-reviewed letters under the App Developer Agreement.

Reviewed by

Partner Center support and Legal

What triggers it

A complete record that stalled in support.

What we submit

An attorney prepared letter under the App Developer Agreement.

Microsoft Store noticePayout returned by bank

Payout returned by bank

A payout bounced back and the next one is held.

Reviewed by

Payout and tax

What triggers it

A returned payment on the payout profile.

What we submit

Corrected bank details in the account holder's name.

?
Don’t see yours?

Your Microsoft Store case may not be listed here. We have likely seen it.

We’ve handled far more Microsoft Store cases than fit on one page, including rare notices and cases no one could name. Send it over and we’ll work out the path with you.

Microsoft Store certification questions

Microsoft Store Certification and Removal FAQs

Don’t see your question? Send us your certification report and we’ll answer it directly.

Why did my Microsoft Store app fail certification?

A Microsoft Store app fails certification when it does not pass the security tests, the technical compliance tests or the content compliance review. Microsoft sends a certification report that names the test that failed and the Store policy that was not met. Fix those exact items before you build a new submission.

How long does Microsoft Store certification take?

Microsoft Store certification can take up to 3 business days. Content compliance review can take longer depending on how complex the app is, its visual content and how many submissions Microsoft has. Once certified, publishing takes a few minutes and customers usually see the listing within about 15 minutes.

How do I fix a failed Microsoft Store certification?

To fix a failed Microsoft Store certification, read the certification report, fix the failed test and policy, then create a new submission to restart certification. For a security failure, Microsoft says to run current antivirus on your development system and rebuild the package on a clean system. Run the Windows App Certification Kit before resubmitting.

How do I appeal a Microsoft Store rejection or removal?

To appeal a Microsoft Store rejection or ask about certification status, email reportapp@microsoft.com with your product details and a clear explanation. Microsoft reports an average processing time of 2.37 days, and in its latest reported year it overturned 623 decisions out of 1,118 enforcement appeals. A well documented appeal matters.

What does Microsoft Store policy 10.1 mean?

Microsoft Store policy 10.1 requires your listing to accurately describe what the product does and where it comes from. You must not use the same name, images or metadata as other products unless you also publish them, and you must not mislead customers about features or relationships to other products. Search terms are limited to seven relevant terms.

What does Microsoft Store policy 10.2 security mean?

Microsoft Store policy 10.2 says your product must not put user security at risk. It bans malware, dynamic code that changes functionality beyond the description and offers to install secondary software you did not develop. Games and Xbox products must be installed and updated only through the Store. Security violations can lead to removal and account suspension.

Why was my Microsoft Store app removed after it was published?

Microsoft removes a published Store app when spot checks or reports find a policy violation after launch. Microsoft keeps checking apps in the Store for compliance. Serious problems like fraud, malware or child safety issues can also lead to action against the developer account itself, so a removal needs a careful, complete response.

What privacy rules does a Microsoft Store app have to follow?

Under Microsoft Store policy 10.5, an app that collects or sends personal information needs a privacy policy. It must get opt-in consent before publishing customer data to third parties, get express consent for highly sensitive data like health or financial data, store data with modern cryptography and respect location settings. Gaps here cause removals.

Does my Microsoft Store app have to use Microsoft in-app purchase?

Under Microsoft Store policy 10.8, games and Xbox products must use the Microsoft Store in-product purchase APIs for digital goods. Non-game PC apps may use a third party payment API. A company account is required if the product asks for financial information, and loot boxes must show their odds before purchase.

Can someone help me get my Microsoft Store app certified or reinstated?

Yes. We read your certification report or removal notice against your package, listing and libraries, fix the real cause with your team and write the appeal with proof. Payout problems get worked on their own track. Book a free assessment and we will tell you how hard your case is.

What does a Microsoft Store appeal service cost?

The cost of a Microsoft Store appeal service depends on how hard the case is. A single failed test is quick work. A security finding, a removal or a Partner Center account action takes more. We start with a free assessment and quote a price before any work begins, so you know the cost upfront.

Can anyone guarantee Microsoft Store certification or reinstatement?

No one can guarantee Microsoft Store certification or reinstatement, because Microsoft makes the final decision. Be careful with anyone who promises it. What we commit to is the work: a full review of the report, a fix and appeal built on evidence and a straight answer about your chances before you pay.

Who we protect

The Developers and Businesses That Trust Us

Some agreed to be named. Most can’t be. Tap a gold-framed face to hear it from them.

Tap any gold-framed face to hear it from them
Start here

Get a Free Assessment of Your Microsoft Store Case

Send us your certification report or notice. We’ll tell you where you stand before you pay anything.

  • A strategist reads your notice before the call
  • You leave with the route and the grade in writing
  • No fee to talk, no obligation after
Microsoft Store noticeCertification failedReceived
1The real trigger is here, not in the label
2The team that reviews it
Our assessmentNext step setGrade and next step in writing
NoticeOur assessmentYour next step
© 2026 "Basilio Inc", All Rights Reserved.Terms & ConditionsPrivacy PolicyDisclaimerAcceptable Use