How to Request a Refund for an Unauthorized Microsoft Purchase

To request a refund for an unauthorized Microsoft purchase, use the correct account, product, permissions, and destination. This guide explains the supported workflow and the checks that confirm the result.

Identify the Correct Billing Account and Purchase Channel

Confirm the owning account, required permissions, affected files or services, and the exact outcome you need. Keep a backup when the task changes local content or removes access.

Quick Billing Investigation

First, contact the bank or card issuer right away using the number on the back of the card or from a bank statement. Next, check whether the charge is tied to a Microsoft account, and verify the final state before changing any backup or secondary account.

How to Request a Refund for an Unauthorized Microsoft Purchase

1. Contact the bank or card issuer right away using the number on the back of the card or from a bank statement
2. Check whether the charge is tied to a Microsoft account
3. Use the refund process described in “Cancel an order or pre-order from Microsoft Store” via “Returning items you bought from Microsoft for exchange or refund”

After the final step, reopen the affected app, portal, file, or account page and confirm the exact status or behavior described in the title.

WPS Office: A Free, AI-Powered Microsoft Office Alternative

WPS Office cannot directly change Microsoft-side account, billing, subscription, activation, tenant, OneDrive service, or SharePoint permission state. Those changes must be completed in the appropriate Microsoft portal.

As a free Microsoft Office-compatible alternative, WPS Office combines document, spreadsheet, presentation, and PDF tools with an interface designed for an easy everyday transition. Beyond opening and saving common DOCX, XLSX, PPTX, and PDF files, WPS AI can assist with writing and rewriting, formulas and data insights, presentation creation, and PDF summaries or Q&A. AI availability and limits can vary by plan, device, region, and version.

Test advanced macros, add-ins, external connections, sensitivity controls, and Microsoft-only cloud integrations on a copy before moving a critical workflow.

Practical Checks That Prevent a Repeat

• Record which account and payment method owns the workflow
• Keep a verified backup before removing access, changing ownership, or replacing a local file
• Apply high-impact changes to one test item or user before expanding the scope
• Save confirmation numbers, dates, and screenshots of the final settings when they affect billing, security, or permissions

Frequently Asked Questions

Which account, file, or app should I use when I contact the bank or card issuer right away using the number on the back?

Contact the bank or card issuer right away using the number on the back of the card or from a bank statement. Personal purchases normally appear in Microsoft account Order history; business purchases appear in the Microsoft 365 admin center under Billing and invoices.

What result should appear when I check whether the charge is tied to a Microsoft account?

The purchase may use another email address, an Apple or Google store, a reseller, or a work tenant. Match the receipt, payment descriptor, amount, and date before disputing it. Confirm the account type, product version, ownership, and permissions before assuming the control is unavailable.

What should I preserve before I use the refund process described in “Cancel an order or pre-order from?

Keep the order or invoice number, charge date, amount, last four card digits, purchasing account, and any existing case ID. Never post the full card number publicly. Keep the relevant backup or confirmation until you have checked the result.

Where should I verify the final result after I request a refund for an unauthorized Microsoft purchase?

Use the refund process described in “Cancel an order or pre-order from Microsoft Store” via “Returning items you bought from Microsoft for exchange or refund”. Reopen the affected app or portal and confirm that the expected status persists.