Forum Discussion
Approved 29 May but Nonprofit Hub stuck at "still being reviewed" — case 2605290040003233
Our nonprofit, MINDFUL PEACE BUDDHIST ASSOCIATION USA INC, applied through nonprofit.microsoft.com on 29 May 2026 and was approved the SAME DAY: we received Microsoft's approval confirmation email on 29 May, and Goodstack has since confirmed in writing that our application was verified, approved, and fully processed. Validation is complete — this is not a pending review.
However, when we sign in to the Nonprofit Hub as the tenant's global admin (tenant: mindfulpeace.onmicrosoft.com), it still shows "Your organization's eligibility is still being reviewed," and no offers are claimable.
Brief history:
- 29 May: applied; approval confirmed same day by both Microsoft and Goodstack.
- Shortly after: the Hub showed "Under Review," then became fully blocked with error 715-123195.
- We opened case 2605290040003233. After escalation, the 715 block was cleared around 10 June — the Hub now loads normally.
- But the status remains stuck at "still being reviewed," contradicting the completed approval.
Everything else works normally on the same account: Microsoft 365 admin center, myaccount.microsoft.com, sign-in, MFA. The issue is isolated to the Nonprofit Hub status not reflecting the already-approved eligibility.
I also have to be candid about the support experience, because it is why I am posting here. Over two weeks across multiple frontline contacts:
- Replies have been near-identical troubleshooting templates (VPN, browser, wait 24 hours) for steps we had already completed and documented in writing from the first email.
- At one point we were told we had "not responded," when our reply with all requested information had already been sent.
- We were promised an update within 24–48 hours; it never came.
- We asked four direct questions — which team is handling the case, what action has been taken, the internal reference, and the timeline — and to this day none has been answered.
I understand frontline advocates may not have backend access, and I'm not blaming individuals. But after two weeks, a small nonprofit should not have to spend this much effort to receive a benefit that was already approved on day one. The fix appears simple: sync the already-approved eligibility record to our tenant so the offers become claimable.
Could a Microsoft team member please look into case 2605290040003233? It has been 9+ business days since same-day approval, and our organization is waiting on these benefits to operate. Thank you.
2 Replies
ADDENDUM (June 13): We tested the proposed workaround today. Starting a new registration under a different email does not modify or migrate the existing record — it creates an entirely new, unrelated account, with no connection to our existing tenant (mindfulpeace.onmicrosoft.com). Even if approved, the benefits would not attach to the tenant we actually use.
In other words: the workaround cannot achieve its own stated purpose. A Microsoft-side fix of the existing approved record remains the only viable path.
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.
