> 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/my-application-for-microsoft-education-is-denied.md).

# My application for Microsoft Education is denied

If your application for [Microsoft Education](/extensions/microsoft-cloud-solution-provider/products-and-programs/microsoft-for-education.md) is denied, you can resubmit it. Microsoft allows up to three verification attempts. 

To request a reverification:

1. Read the specific reasons provided in your denial notification.
2. Gather the required documents to support your eligibility. 
3. Sign in to the Microsoft 365 Admin Center and update the inaccurate details under **Settings** > **Organization Information**.
4. Request a reverification. 

After resubmitting the request, allow 3–5 business days for Microsoft to review your submission. 

To track the request status, visit the Microsoft 365 admin center.

If your request is unsuccessful after three attempts, you must engage with Microsoft Support directly. You can also contact SoftwareOne. 


---

# 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/my-application-for-microsoft-education-is-denied.md?ask=<question>&goal=<user_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.