Secure research starts with responsible testing.
Bounty Program Guidelines
Partner with Microsoft to strengthen our products and services by identifying and reporting security vulnerabilities that could impact our customers.
IMPORTANT: The Microsoft Bounty Program is subject to the following terms and those outlined in the Microsoft Bounty Terms and Conditions, Microsoft Bounty Legal Safe Harbor, Rules of Engagement, Coordinated Vulnerability Disclosure (CVD), Bounty Program Guidelines, and the Microsoft Bounty Program page.
MICROSOFT BOUNTY TERMS & CONDITIONS
Last updated: July 23, 2025
The Microsoft Bug Bounty Programs Terms and Conditions ("Terms") cover your participation in the Microsoft Bug Bounty Program (the "Program"). These Terms are between you and Microsoft Corporation ("Microsoft," "us" or "we"). By submitting any vulnerabilities to Microsoft or otherwise participating in the Program in any manner, you accept these Terms.
PROGRAM OVERVIEW
The Program enables users to submit vulnerabilities and exploitation techniques ("Vulnerabilities") to Microsoft about eligible Microsoft products and services ("Products") for a chance to earn rewards in an amount determined by Microsoft in its sole discretion ("Bounty"). Each Product for which Bounties are available has a separate set of terms applicable to that Product (the "Product Program Terms"), which are incorporated by reference into these Terms. In the event of a conflict between these Terms and the Product Program Terms for a particular Product, the Product Program Terms control for that particular Product only. The decisions made by Microsoft regarding Bounties are final and binding. Microsoft may change or cancel this Program at any time, for any reason.
CHANGES TO THESE TERMS
We may change these Terms at any time. Participating in the Program after the changes become effective means you agree to the new Terms. If you don't agree to the new Terms, you must not participate in the Program.
If you wish to opt-out of the Program and not be considered for Bounties, contact us at secure@microsoft.com. Opting out will not affect any licenses granted to Microsoft in any Submissions provided by you.
PROGRAM ELIGIBILITY
You ARE eligible to participate in the Program if you meet all of the following criteria:
- You are 14 years of age or older. If you are at least 14 years old but are considered a minor in your place of residence, you must obtain your parent's or legal guardian's permission prior to participating in this Program; and
- You are either an individual researcher participating in your own individual capacity, or you work for an organization that permits you to participate. You are responsible for reviewing your employer's rules for participating in this Program.
ATTENTION PUBLIC SECTOR EMPLOYEES: If you are a public sector employee (government and education), all Bounties must be awarded directly to your public sector organization and subject to receipt of a gift letter signed by your organization's ethics officer, attorney, or designated executive/officer responsible for your organization's gifts/ethics policy. Microsoft seeks to ensure that by offering Bounties under this Program, it does not create any violation of the letter or spirit of a participant's applicable gifts and ethics rules.
You ARE NOT eligible to participate in the Program if you meet any of the following criteria:
- You are a resident of any countries under U.S. sanctions (see link for current sanctions list posted by the United States Treasury Department) or any other country that does not allow participation in this type of program, or is prohibited under Microsoft Export policy;
- You are under the age of 14;
- Your organization does not allow you to participate in these types of programs;
- You are a public sector employee (government and education) and have not obtained permission from your ethics compliance officer to participate in the Program;
- You are currently an employee of Microsoft Corporation or a Microsoft subsidiary, or an immediate family (parent, sibling, spouse, or child) or household member of such an employee;
- Within the six months prior to providing us your Submission you were an employee of Microsoft Corporation or a Microsoft subsidiary; or
- You currently (or within six months prior providing to us your Submission) perform services for Microsoft or a Microsoft subsidiary in an external staff capacity that requires access to the Microsoft Corporate Network, such as agency temporary worker, vendor employee, business guest, or contractor; o
To adhere to Microsoft's commitment to complying with all applicable U.S., EU, and UK export and sanctions laws and regulations, Microsoft prohibits any financial transactions with individuals or entities designated by these trade laws or to embargoed or comprehensively sanctioned destinations (including Iran, Cuba, Syria, North Korea, Russia, and Belarus). For more detailed information on our export compliance policies, please refer to the Microsoft Export Control Policy.
Microsoft reserves the right to disqualify any participant. Participation and the awarding of prizes are at Microsoft’s sole discretion and may be subject to additional eligibility criteria. If you have questions about these laws or regulations, please consult your own legal counsel.
SUBMISSION PROCESS & COORDINATED VULNERABILITY DISCLOSURE
If you believe you have identified a Vulnerability that meets the applicable requirements set forth in the Product Program Terms, you may submit it to Microsoft through the process described in the Product Program Terms or, if none is provided, in accordance with the following process:
Each Vulnerability submitted to Microsoft shall be a "Submission." Submissions must be submitted to the MSRC Researcher Portal. In the initial email, specify the name of the Bounty Program you are submitting under, the Vulnerability details, and specific product version numbers you used to validate your research. Please also include as much of the following information as possible:
- Type of issue (buffer overflow, SQL injection, cross-site scripting, etc.)
- Product and version that contains the bug, or URL if for an online service
- Service packs, security updates, or other updates for the product you have installed
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue on a fresh install
- Proof-of-concept or exploit code
- Impact of the issue, including how an attacker could exploit the issue
A sample report is available here. You must follow Coordinated Vulnerability Disclosure (CVD) when reporting all Vulnerabilities to Microsoft. Submissions that do not follow CVD may not be eligible for Bounties and not following CVD could disqualify you from participating in the Program in the future.
Depending on the detail of your Submission, Microsoft may award a Bounty of varying scale. Well-written reports and functional exploits are more likely to result in Bounties. Those Submissions that do not meet the minimum bar described above are considered incomplete and not eligible for Bounties.
Microsoft is not responsible for Submissions that we do not receive for any reason. If you do not receive a confirmation email after making your Submission, notify Microsoft at secure@microsoft.com to ensure your Submission was received.
There are no restrictions on the number of qualified Submissions you can provide and potentially be paid a Bounty for.
If you submit a Vulnerability for a product or service that is not covered by the Program at the time you submitted it, you will not be eligible to receive Bounty payments if the product or service is later added to the Program.
SUBMISSION LICENSE
Microsoft is not claiming any ownership rights to your Submission. However, by providing any Submission to Microsoft, you:
- grant Microsoft the following non-exclusive, irrevocable, perpetual, royalty free, worldwide, sub-licensable license to the intellectual property in your Submission: (i) to use, review, assess, test, and otherwise analyze your Submission; (ii) to reproduce, modify, distribute, display and perform publicly, and commercialize and create derivative works of your Submission and all its content, in whole or in part; and (iii) to feature your Submission and all of its content in connection with the marketing, sale, or promotion of this Program or other programs (including internal and external sales meetings, conference presentations, tradeshows, and screen shots of the Submission in press releases) in all media (now known or later developed);
- agree to sign any documentation that may be required for us or our designees to confirm the rights you granted above;
- understand and acknowledge that Microsoft may have developed or commissioned materials similar or identical to your Submission, and you waive any claims you may have resulting from any similarities to your Submission;
- understand that you are not guaranteed any compensation or credit for use of your Submission; and
- represent and warrant that your Submission is your own work, that you haven't used information owned by another person or entity, and that you have the legal right to provide the Submission to Microsoft.
CONFIDENTIALITY OF SUBMISSIONS/ RESTRICTIONS ON DISCLOSURE
Protecting customers is Microsoft's highest priority. We endeavor to address each Vulnerability report in a timely manner. While we are doing that we require that Bounty Submissions remain confidential and cannot be disclosed to third parties or as part of paper reviews or conference submissions. You can make available high-level descriptions of your research and non-reversible demonstrations after the Vulnerability is fixed. We require that detailed proof-of-concept exploit code and details that would make attacks easier on customers be withheld for 30 days after the Vulnerability is fixed. Microsoft will notify you when the Vulnerability in your Submission is fixed. You may be paid prior to the fix being released and payment should not be taken as notification of fix completion. If you impose a fixtimeline or Service Level Agreement ("SLA") anytime throughout the case process, you will forfeit your bounty eligbility. VIOLATIONS OF THIS SECTION COULD REQUIRE YOU TO RETURN ANY BOUNTIES PAID FOR THAT VULNERABILITY AND DISQUALIFY YOU FROM PARTICIPATING IN THE PROGRAM IN THE FUTURE.
SUBMISSION REVIEW PROCESS
After a Submission is sent to Microsoft in accordance with Section 5 (above), Microsoft engineers will review the Submission and validate its eligibility. The review time will vary depending on the complexity and completeness of your Submission, as well as on the number of Submissions we receive.
Microsoft retains sole discretion in determining which Submissions are qualified, according to the rules set forth in the Product Program Terms. If we receive multiple bug reports for the same issue from different parties, the Bounty will be granted to the first eligible Submission. If a duplicate report provides new information that was previously unknown to Microsoft, we may award a differential to the person submitting the duplicate report.
If you report a Vulnerability without a functioning exploit, you may be eligible for a partial Bounty. If you submit the functioning exploit within 90 days of submitting the Vulnerability, we may, in our discretion, provide an additional Bounty payment (but are not obligated to do so).
BOUNTY PAYMENTS
The decisions made by Microsoft regarding Bounties are final and binding.
If we have determined that your Submission is eligible for a Bounty under the applicable Product Program Terms, we will notify you of the Bounty amount and provide you with the necessary paperwork to process your payment. You may waive the payment if you do not wish to receive a Bounty.
If there is a dispute as to who the qualified submitter is, we will consider the eligible submitter to be the authorized account holder of the email address used to enter the Program.
Before receiving a Bounty, you are required to complete and submit an Internal Revenue Service tax form (e.g., Form W-9, W-8BEN, 8233) within 30 calendar days of notification of validation. If you do not complete the required forms as instructed or do not return the required forms within the time period listed on the notification message, we may not provide payment. We cannot process payment until you have completed and submitted the fully executed required documentation.
If your Submission qualifies for a Bounty, please note:
- you may not designate someone else as the Bounty recipient unless you are considered a minor in your place of residence;
- if you are eligible for this Program but are considered a minor in your place of residence, we may award the Bounty to your parent/legal guardian on your behalf and require them to sign all required forms on your behalf. The Bounty will be added to the taxable income of your parent/legal guardian;
- if you are unable or unwilling to accept your Bounty, we reserve the right to rescind it; and
- if you accept a Bounty, you will be solely responsible for all applicable taxes related to accepting the payment(s).
NOTE: For public sector employees (government and education), all Bounties must be awarded directly to your public sector organization and subject to receipt of a gift letter signed by the organization's ethics officer, attorney, or designated executive/officer responsible for the organization’s gifts/ethics policy. Microsoft seeks to ensure that by offering Bounties under this Program, it does not create any violation of the letter or spirit of a participant’s applicable gifts and ethics rules.
PUBLIC RECOGNITION
Microsoft may publicly recognize individuals who have been awarded Bounties. Microsoft at it is discretion may recognize you on web properties or other printed materials unless you explicitly ask us not to include your name.
PRIVACY
See the Microsoft Privacy Statement disclosures relating to the collection and use of your information in connection with the Program.
CODE OF CONDUCT
By participating in the Program, you will follow these rules:
- Don’t do anything illegal.
- Don't engage in any activity that exploits, harms, or threatens to harm children.
- Don't send spam. Spam is unwanted or unsolicited bulk email, postings, contact requests, SMS (text messages), or instant messages.
- Don't share inappropriate content or material (involving, for example, nudity, bestiality, pornography, graphic violence, or criminal activity).
- Don't engage in activity that is false or misleading.
- Don't engage in activity that is harmful to you, the Program, or others (e.g., transmitting viruses, stalking, posting terrorist content, communicating hate speech, or advocating violence against others).
- Don't infringe upon the rights of others (e.g., unauthorized sharing of copyrighted material) or engage in activity that violates the privacy of others.
- Don't help others break these rules.
If you violate these Terms, you may be prohibited from participating in the Program in the future and any Submissions you have provided may be deemed to be ineligible for Bounty payments.
Repeated breaches of these Code of Conduct may result in disqualification from the following:
- Researcher Recognition Program Quarterly Leaderboards and Annual MVR Leaderboards
- MSRC researcher celebration events and BlueHat attendance
- Participation in Microsoft Bounty Research Challenges and Hacking Events
NO WARRANTIES
MICROSOFT, AND OUR AFFILIATES, RESELLERS, DISTRIBUTORS, AND VENDORS, MAKE NO WARRANTIES, EXPRESS OR IMPLIED, GUARANTEES OR CONDITIONS WITH RESPECT TO THE PROGRAM. YOU UNDERSTAND THAT YOUR PARTICIPATION IN THE PROGRAM IS AT YOUR OWN RISK. TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAW, WE EXCLUDE ANY IMPLIED WARRANTIES IN CONNECTION WITH THE PROGRAM. YOU MAY HAVE CERTAIN RIGHTS UNDER YOUR LOCAL LAW. NOTHING IN THESE TERMS IS INTENDED TO AFFECT THOSE RIGHTS, IF THEY ARE APPLICABLE.
LIMITATION OF LIABILITY & BINDING ARBITRATION
If you have any basis for recovering damages in connection with the Program (including breach of these Terms), you agree that your exclusive remedy is to recover, from Microsoft or any affiliates, resellers, distributors, third-party providers, and vendors, direct damages up to $100.00. You can't recover any other damages or losses, including direct, consequential, lost profits, special, indirect, incidental, or punitive. These limitations and exclusions apply even if this remedy doesn't fully compensate you for any losses or fails of its essential purpose or if we knew or should have known about the possibility of the damages. To the maximum extent permitted by law, these limitations and exclusions apply to anything or any claims related to these Terms and the Program.
BINDING ARBITRATION AND CLASS ACTION WAIVER If You Live In (or If a Business Your Principal Place of Business Is In) the United States
We hope we never have a dispute, but if we do, you and we agree to try for 60 days to resolve it informally. If we can't, you and we agree to binding individual arbitration before the American Arbitration Association ("AAA") under the Federal Arbitration Act ("FAA"), and not to sue in court in front of a judge or jury. Instead, a neutral arbitrator will decide and the arbitrator's decision will be final except for a limited right of review under the FAA. Class action lawsuits, class-wide arbitrations, private attorney-general actions, and any other proceeding where someone acts in a representative capacity aren't allowed. Nor is combining individual proceedings without the consent of all parties. "We," "our," and "us" includes Microsoft and Microsoft's affiliates.
- Disputes Covered—Everything Except IP. The term "dispute" is as broad as it can be. It includes any claim or controversy between you and us concerning the Program or these Terms, under any legal theory including contract, warranty, tort, statute, or regulation, except disputes relating to the enforcement or validity of your, your licensors’, our, or our licensors’ intellectual property rights.
- Mail a Notice of Dispute First. If you have a dispute and our customer service representatives can't resolve it, send a Notice of Dispute by U.S. Mail to Microsoft Corporation, ATTN: CELA Arbitration, One Microsoft Way, Redmond, WA 98052-6399, U.S.A. (or to your mobile phone carrier at its principal place of business in the United States marked ATTN: Legal Department). Tell us your name, address, how to contact you, what the problem is, and what you want. A form is available at http://go.microsoft.com/fwlink/?LinkId=245499. We'll do the same if we have a dispute with you. After 60 days, you or we may start an arbitration if the dispute is unresolved.
- Small Claims Court Option. Instead of mailing a Notice of Dispute, you may sue us in small claims court in your county of residence (or if a business your principal place of business) or King County, Washington, U.S.A. if you meet the court's requirements.
- Arbitration Procedure. The AAA will conduct any arbitration under its Commercial Arbitration Rules (or if you are an individual or if the value of the dispute is $75,000 or less whether or not you are an individual, its Consumer Arbitration Rules). For more information, see www.adr.org or call 1-800-778-7879. To start an arbitration, submit the form available at http://go.microsoft.com/fwlink/?LinkId=245497 to the AAA and mail a copy to us. In a dispute involving $25,000 or less, any hearing will be telephonic unless the arbitrator finds good cause to hold an in-person hearing instead. Any in-person hearing will take place in your county of residence (or if a business your principal place of business) or our principal place of business—King County, Washington if your dispute is with Microsoft. You choose. The arbitrator may award the same damages to you individually as a court could. The arbitrator may award declaratory or injunctive relief only to you individually to satisfy your individual claim.
- Arbitration Fees and Payments.
- Disputes Involving $75,000 or Less. We will promptly reimburse your filing fees and pay the AAA’s and arbitrator’s fees and expenses. If you reject our last written settlement offer made before the arbitrator was appointed, your dispute goes all the way to an arbitrator’s decision (called an “award”), and the arbitrator awards you more than this last written offer, we will: (i) pay the greater of the award or $1,000; (ii) pay your reasonable attorney’s fees, if any; and (iii) reimburse any expenses (including expert witness fees and costs) that your attorney reasonably accrues for investigating, preparing, and pursuing your claim in arbitration.
- Disputes Involving More than $75,000. The AAA rules will govern payment of filing fees and the AAA's and arbitrator's fees and expenses.
- Conflict with AAA Rules. These Terms govern to the extent they conflict with the AAA’s Commercial Arbitration Rules or Consumer Arbitration Rules.
- Must File Within One Year. You and we must file in small claims court or arbitration any claim or dispute (except intellectual property disputes) within one year from when it first could be filed. Otherwise, it's permanently barred.
- Rejecting Future Arbitration Changes. You may reject any change we make to this section (except address changes) by sending us notice within 30 days of the change by U.S. Mail to the address in section (b). If you do, the most recent version of the section before the change you rejected will apply.
- Severability. If the class action waiver is found to be illegal or unenforceable as to all or some parts of a dispute, then those parts won't be arbitrated but will proceed in court, with the rest proceeding in arbitration. If any other provision of this section is found to be illegal or unenforceable, that provision will be severed but the rest of this section still applies.
CHOICE OF LAW AND PLACE TO RESOLVE DISPUTES
If you live in (or, if a business, your principal place of business is in) the United States, the laws of the state where you live govern all claims, regardless of conflict of laws principles, except that the Federal Arbitration Act governs all provisions relating to arbitration. You and we irrevocably consent to the exclusive jurisdiction and venue of the state or federal courts in King County, Washington, for all disputes arising out of or relating to these Terms or the Program that are heard in court (excluding arbitration and small claims court).
MISCELLANEOUS
These Terms, the Microsoft Privacy Statement, and any applicable Product Program Terms are the entire agreement between you and Microsoft for your Participation in the Program. It supersedes any prior agreements between you and Microsoft regarding your participation in the Program. All parts of these Terms apply to the maximum extent permitted by relevant law. If a court or arbitrator holds that we can't enforce a part of these Terms as written, we may replace those terms with similar terms to the extent enforceable under the relevant law, but the rest of these Terms won't change.
UNSOLICITED IDEAS
Other than your Submission, Microsoft does not consider or accept unsolicited proposals or ideas, including without limitation ideas for new products, technologies, promotions, product names, product feedback and product improvements ("Unsolicited Feedback"). If you send any Unsolicited Feedback to Microsoft through the Program or otherwise, Microsoft makes no assurances that your ideas will be treated as confidential or proprietary.
IF YOU DO NOT AGREE TO THESE TERMS, PLEASE DO NOT SEND US ANY SUBMISSIONS OR OTHERWISE PARTICIPATE IN THIS PROGRAM.
MICROSOFT BOUNTY LEGAL SAFE HARBOR
SUMMARY
- We want you to responsibly disclose through our bug bounty programs, and don't want researchers put in fear of legal consequences because of their good faith attempts to comply with our bug bounty policy. We cannot bind any third party, so do not assume this protection extends to any third party. If in doubt, ask us before engaging in any specific action you think might go outside the bounds of our policy.
- Because both identifying and non-identifying information can put a researcher at risk, we limit what we share with third parties. We may provide non-identifying substantive information from your report to an affected third party, but only after notifying you and receiving a commitment that the third party will not pursue legal action against you. We will only share identifying information (name, email address, phone number, etc.) with a third party if you give your written permission.
- If your security research as part of the bug bounty program violates certain restrictions in our site policies, the safe harbor terms permit a limited exemption
1. Safe Harbor Terms
To encourage research and responsible disclosure of security vulnerabilities, we will not pursue civil or criminal action, or send notice to law enforcement for accidental or good faith violations of Microsoft Bug Bounty Terms and Conditions ("the policy"). We consider security research and vulnerability disclosure activities conducted consistent with this policy to be “authorized” conduct under the Computer Fraud and Abuse Act, the DMCA, and other applicable computer use laws such as WA Criminal Code 9A.90. We waive any potential DMCA claim against you for circumventing the technological measures we have used to protect the applications in our bug bounty programs’ scope.
Please understand that if your security research involves the networks, systems, information, applications, products, or services of a third party (which is not us), we cannot bind that third party, and they may pursue legal action or law enforcement notice. We cannot and do not authorize security research in the name of other entities, and cannot in any way offer to defend, indemnify, or otherwise protect you from any third party action based on your actions.
You are expected, as always, to comply with all laws applicable to you, and not to disrupt or compromise any data beyond what our bug bounty programs permit.
Please contact us before engaging in conduct that may be inconsistent with or unaddressed by this policy. We reserve the sole right to make the determination of whether a violation of this policy is accidental or in good faith, and proactive contact to us before engaging in any action is a significant factor in that decision. If in doubt, ask us first!
2. Third Party Safe Harbor
If you submit a report through our bug bounty program which affects a third party service, we will limit what we share with any affected third party. We may share non-identifying content from your report with an affected third party, but only after notifying you that we intend to do so and getting the third party's written commitment that they will not pursue legal action against you or initiate contact with law enforcement based on your report. We will not share your identifying information with any affected third party without first getting your written permission to do so.
Please note that we cannot authorize out-of-scope testing in the name of third parties, and such testing is beyond the scope of our policy. Refer to that third party's bug bounty policy, if they have one, or contact the third party either directly or through a legal representative before initiating any testing on that third party or their services. This is not, and should not be understood as, any agreement on our part to defend, indemnify, or otherwise protect you from any third party action based on your actions.
That said, if legal action is initiated by a third party, including law enforcement, against you because of your participation in this bug bounty program, and you have sufficiently complied with our bug bounty policy (i.e. have not made intentional or bad faith violations), we will take steps to make it known that your actions were conducted in compliance with this policy. While we consider submitted reports both confidential and potentially privileged documents, and protected from compelled disclosure in most circumstances, please be aware that a court could, despite our objections, order us to share information with a third party.
3. Limited Waiver of Other Site Policies
To the extent your security research activities are inconsistent with certain restrictions in our relevant site polices but are consistent with the terms of our bug bounty program, we waive those restrictions for the sole and limited purpose of permitting your security research under this bug bounty program. Just like above, if in doubt, ask us first!
ELIGIBLE SUBMISSIONS
The goal of the Microsoft Bug Bounty program is to uncover significant technical vulnerabilities that have a direct and demonstrable impact on the security of our customers.
Vulnerability submissions must meet the following criteria to be eligible for bounty awards:
- Identify a vulnerability that was not previously reported to, or otherwise known by, Microsoft.
- Provide the information necessary to quickly reproduce, understand, and fix the reported issue.
- This typically includes a concise write up containing any required background information, a description of the bug, a proof of concept (PoC), and a video.
- Find example reports here.
- Third-party software vulnerabilities must demonstrate a qualifying security impact on a Microsoft service.
- Third-party software vulnerabilities must be unique and not reported to the affected vendor and must not be under an existing third-party bounty program.
- Researchers are responsible for complying with all terms governing third-party environments.
- We do not authorize testing on behalf of third parties.
- Microsoft’s Safe Harbor protections do not apply to issues arising from third-party complaints.
Additional Information:
- If we receive multiple bug reports for the same issue from different parties, the bounty will be granted to the first submission.
- If a duplicate report provides us new information that was previously unknown to Microsoft, we may award a differential to the duplicate submission.
- If the same vulnerability appears across multiple products or endpoints and requires separate fixes, it is classified as a “variant.” For variant cases, a maximum of 10 bounty awards may be awarded.
- If a submission is potentially eligible for multiple Microsoft bounty programs, you will receive the single highest payout award from a single bounty program.
- Microsoft may accept or reject any submission at our sole discretion that we determine does not meet the above criteria.
SCOPE
Each bug bounty program has its own targeted scope, eligibility criteria, award range, and submission guidelines to help researchers pursue impactful research. However, any vulnerability that demonstrates significant impact to affected Microsoft services or customers may qualify for bounty. This includes third-party and open-source components included by default in a Microsoft product or service. Please note that qualifying reports must demonstrate a qualifying security impact on the specified service.
OUT OF SCOPE
Some submission types are generally not eligible for Microsoft bounty awards. Please refer to our bounty programs for additional information on eligible submission, vulnerability, or attack methods.
- Scanners and automation tools are common trade practices in the security community. They often produce many results for further investigation and can yield many false positives. Reports from automated tools, scanners must include additional analysis to demonstrate the exploitability of the vulnerability to be eligible for bounty award.
- Submissions that require manipulation of data, network access, or physical attack against Microsoft offices or data centers and/or social engineering of our customer support service desk, employees, or contractors are not eligible for bounty awards.
- Third-party vulnerabilities covered under an existing external bounty program do not qualify. MSRC coordinates disclosure and avoids double payment.
- Content-related issues as defined by the Microsoft Vulnerability Severity and Content Classifications for AI Systems.
- Content-related issues can be reported to the MSRC Researcher Portal. In the Security Impact section, select “AI derived harm”.
- Recent acquistions are out-of-scope.
- For LinkedIn, GitHub, and Activision Blizzard, Inc., please visit their official website for reporting vulnerabilities or contact their security team for more information.
- Vulnerabilities in any version other than latest, fully patched version at time of submission.
- Vulnerabilities in a web application that only affect unsupported browsers and plugins.
- Vulnerabilities that are addressed via product documentation updates, without change to product code or function.
STANDARD AWARD POLICY
Any security vulnerability classified as "critical" or "important" severities* and aligns with an eligible security impact that affects Microsoft-owned domains and cloud services will be eligible for a standard or baseline award — unless it qualifies for a higher award within one of Microsoft’s specialized Cloud Programs. The Standard Award Policy does not apply to Endpoint & On-Prem Programs.
Eligible Security Impacts:
- Elevation of Privilege
- Information Disclosure
- Remote Code Execution
- Spoofing
AWARD AMOUNTS
| Report Quality | Critical | Important |
|---|---|---|
| High | $5,000 | $2,500 |
| Medium | $3,000 | $1,500 |
| Low | $1,500 | $750 |
*For additional details on how Microsoft classifies severity, please see the Windows Security Servicing Criteria, Microsoft Vulnerability Severity Classification for AI Systems, Microsoft Vulnerability Severity Classification for Online Services, and Microsoft Vulnerability Severity Classification for Windows.
FAQs
This page answers frequently asked questions about the Microsoft Bounty Program. Please see the Microsoft Bounty Terms for the full terms and conditions that apply to the Microsoft Bounty Program.
How do I submit a vulnerability report?
Submit your finding to Microsoft using our MSRC Researcher Portal, including instructions to reproduce the vulnerability, using the bug submission guidelines found here.
Some important notes:
- We request you follow Coordinated Vulnerability Disclosure (CVD) when reporting all vulnerabilities to Microsoft. Submissions that do not follow CVD may not be eligible for bounty and could disqualify you from participating in bounty programs in the future.
- Microsoft will exercise reasonable efforts to clarify indecipherable or incomplete submissions, but more complete submissions are often eligible for higher bounties (see program award tables for details).
- There are no restrictions on the number of qualified submissions an individual submitter can provide and potentially receive bounty awards for.
What happens after I submit a bounty-eligible vulnerability report?
See blog post: What to Expect When Reporting Vulnerabilities to Microsoft
- You will receive an email confirming that we have received your submission.
- The MSRC case managers and engineering team will review the submission, including reproducing the vulnerability and assessing the severity and security impact. The review time may vary depending on the complexity and completeness of your submission, but typically takes 2 weeks.
- After your submission has been reproduced and assessed, the bounty team will review your submission for bounty award eligibility. If your submissionis eligible for a bounty award, the bounty team will contact you to share the good news and begin the award payment process.
- You will be asked to complete registration with one of our award payment providers. Once registration is complete you will receive your bounty award through that provider.
- We will recognize most individuals who have been awarded bounties through our security researcher acknowledgements or our Online Services Security Acknowledgements.
I have been awarded a bounty. What do I do next?
If you have been awarded a bounty, the next step is to log into the MSRC Researcher Portal to select your preferred bounty award payment provider and accept the Microsoft Bounty Terms. Microsoft partners with Intigriti to deliver bounty awards quickly and with more award options for bounty recipients including bank transfer, Paypal, and cryptocurrency.
Payment Provider Options
Intigriti (preferred):
- Delivery Options: Bank transfer, PayPal, Payoneer
- Payment Frequency: every second business day
Next Steps For Each Payment Provider
Intigriti:
Please select Intigriti as your payment provider in the MSRC Researcher Portal. Use an email already registered with Intigriti or provide a new email and Intigriti will register you as a part of the award payment process.
Who is eligible to participate in the bounty program?
Please see the Program Eligibility section of the Microsoft Bounty Terms.
How does Microsoft determine bounty awards?
- The products and services in scope for bounty awards and award amounts are published on the Microsoft Bounty Programs pages.
- Microsoft retains sole discretion in determining which submissions are qualified.
- If we receive multiple bug reports for the same issue from different parties, the bounty will be awarded to the first eligible submission. The other submission will be considered duplicates, and not eligible for bounty awards.
- If Microsoft is aware of the issue internally but has not yet released a fix, the first eligible external submission is still eligible for award.
- If a duplicate report provides new information that was previously unknown to Microsoft, we may award a differential to the person submitting the duplicate report.
- If a submission is potentially eligible for multiple bounty programs, you will receive single highest payout award from a single bounty program.
My case is not in scope for a bounty award, but I have new information. What should I do next?
If you have additional information to share about your case, please send it to your case manager on the email case thread. If the assessment of your case changes after a bounty award decision has been made, the bounty team is always happy to take a second look at the report.
I submitted a vulnerability that is not in scope for your current bounty programs. Am I eligible for an award?
Bounty is just one of the ways we recognize researchers who help us protect Microsoft customers. If you submission is not eligible for bounty awards, you may still Researcher Recognition points and public acknowledgement for your contribution to fixes and updates.
Am I eligible for bounty if I find a vulnerability while pentesting Microsoft Azure?
It is your responsibility to comply with the Microsoft Cloud Unified Penetration Testing Rules of Engagement. To receive a bounty award, an organization or individual must submit a report identifying a bounty eligible vulnerability to Microsoft using the MSRC Researcher Portal and bug submission guidelines.
When are you going to add a bounty for [X]?
We’re constantly evaluating our programs to determine how to strengthen and grow our partnership with the global security research community to protect Microsoft’s customers.
What can I disclose about a vulnerability report I submitted for bounty and when can I disclose it?
Protecting customers is Microsoft's highest priority. We endeavor to address each vulnerability report in a timely manner. While we are doing that, we require that all submissions remain confidential and cannot be disclosed to third parties or as part of paper reviews or conference submissions. You can make available high-level descriptions of your research and non-reversible demonstrations after the vulnerability is fixed. You may receive an award prior to the fix being released and award should not be taken as notification of fix completion.
- Please contact bounty@microsoft.com if you intend to discuss the vulnerability after it has been fixed. This includes blog posts, public presentations, whitepapers and other media.
- To give people time to update, we generally recommend waiting for at least 30 days after your submission has been fixed by Microsoft before discussing it publicly.
Can I submit a vulnerability when I find It and submit a working exploit later?
Yes. We want to know about a security vulnerability as soon as you’ve found it. If you plan to develop a functioning exploit after submitting the vulnerability, please contact bounty@microsoft.com. Depending on the bounty scope, a working exploit may be eligible for an additional bounty award.
How long do I have to send in additional information after an initial submission?
Assessment typically takes 14 business days from the time a case is created. Please provide any additional information or respond to questions from your case manager within this time frame in order to help our engineering team reproduce your report as easily as possible.
What is Intigriti's role in the Microsoft Bounty Program?
Microsoft partners with Intigriti to deliver bounty awards to eligible researchers. Intigriti helps us deliver bounty awards quickly, and with more award options like PayPal, Payoneer, or direct bank transfers in more than 30 currencies.
Microsoft manages our Bounty Programs independently from the Intigriti platform. Vulnerability reports must be submitted directly to Microsoft through the MSRC Researcher Portal, and the details of those submissions will not be shared without payment provider partners. Our payment provider partners will only receive information about the award amount, case number, and case severity. Any questions about the status of a submission assessment, fix, or release should be directed to Microsoft.
We recommend all researchers use Intigriti to receive their bounty awards. Researchers who are unable to use one of these providers may choose to use Microsoft’s corporate payment system to receive bounty awards. Awards through our corporate system may take 1 to 3 months to process, significantly longer than awards delivered through Intigriti.
I have more questions, who can I ask?
If you have additional questions about Microsoft bounty programs, please contact bounty@microsoft.com.