> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/extensions/microsoft-cloud-solution-provider/additional-resources/faqs/how-do-i-get-the-microsoft-csp-nonprofit-qualification.md). # How do I get the Microsoft CSP nonprofit qualification? To access Microsoft CSP nonprofit benefits, your organization must first be validated as an eligible nonprofit organization through Microsoft’s nonprofit eligibility process. This involves registering on the [Microsoft Nonprofits Portal](https://nonprofit.microsoft.com/), where Microsoft will review and approve your status. It's important that your organization's legal name and tax ID used during registration match the information submitted for the nonprofit validation. Once your status has been approved, your CSP partner can create your customer account in Partner Center, ensuring that the organization type is set correctly as a nonprofit. After your nonprofit status is confirmed, you can access charity-specific offers and pricing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.platform.softwareone.com/extensions/microsoft-cloud-solution-provider/additional-resources/faqs/how-do-i-get-the-microsoft-csp-nonprofit-qualification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.