Forum Discussion
Approved 29 May but Nonprofit Hub stuck at "still being reviewed" — case 2605290040003233
UPDATE (June 13): This case is now in its third week. Microsoft has confirmed that the approved registration record cannot be repaired, and the proposed workaround is for us to re-register using different registration details. We have declined.
The entire case, in four lines:
Day 1 (May 29): We applied and received written approval through Microsoft's nonprofit process. Goodstack later confirmed in writing that our application was approved, fully processed, and our nonprofit eligibility verified.
Week 1: The Nonprofit Hub did not reflect the approval. Support's response focused on VPN, browser, and waiting 24 hours.
Week 2: After we provided screenshots, Event IDs, Goodstack confirmation, and technical findings, the case remained unresolved. At one point, support replied that we had not responded, even though we had.
Week 3: The first substantive answer finally arrived in writing: the registration record is "stuck in an error state that can no longer be recovered or repaired due to backend system constraints." The proposed workaround is for us to submit a new registration using a different organization email and a different or modified domain, entering our organization details manually.
This means an approved nonprofit is being asked to restart the process with modified registration details because Microsoft's backend system cannot repair or properly migrate the approved record. It took Microsoft one day to say yes — and three weeks to fail to make that yes visible.
We declined.
We have one official domain: mindfulpeace.org. We have one organizational identity. Goodstack verifies nonprofit affiliation through the organization email/domain relationship, so changing the email and domain risks creating a new validation failure or a second broken record.
What we are asking for is simple:
- Repair or reset the existing approved registration record;
- Or manually map the already-approved Goodstack eligibility result to our tenant, mindfulpeace.onmicrosoft.com;
- Or provide an official Microsoft-side migration path that preserves our organization's identity and domain, with Goodstack coordinated in advance.
On June 10, we escalated this case in writing to Microsoft's CEO and COO offices with the full case summary. We did this because this is no longer only a support ticket. It is a customer trust and program accountability issue.
We are a small Buddhist nonprofit. We teach patience for a living. This case has tested it beyond reason.
To other nonprofits: keep everything in writing, preserve your approval emails, and check early that your approved eligibility is actually linked to your tenant.
Case 2605290040003233.
We would still much rather update this thread with the story of how Microsoft took ownership and fixed it.