Approved 29 May but Nonprofit Hub stuck at "still being reviewed" — case 2605290040003233

UPDATE / CLARIFICATION (June 18): Correcting the record, and where this now stands.

First, an important correction. We have NOT created a new registration, and we have NOT created a new .onmicrosoft.com tenant. We declined the proposed re-registration workaround because it does not repair the original Microsoft-side issue and risks creating a second broken or duplicate record.

Despite this, the latest support response assumes we already tested the workaround and created a new account — and asked us to provide "the email used for the new registration" and "the newly created .onmicrosoft.com tenant." There is no such account to provide. This is precisely the problem we have been raising: the proposed workaround does not fix the existing approved record, and the case is still not being tracked accurately.

The facts remain unchanged:

- Our application was submitted properly on 29 May and approved the SAME DAY. Goodstack has confirmed in writing that it was verified, approved, and fully processed.

- The 715-123195 access error has been cleared. Account access, MFA, and the Microsoft 365 admin center all work normally.

- The Nonprofit Hub still does not reflect the approved eligibility for our existing tenant, mindfulpeace.onmicrosoft.com.

- Microsoft's own admin center now confirms the outcome plainly: under Billing > Your products, ZERO products; under Benefits, "You have no benefits"; the marketplace shows only full retail pricing, no nonprofit offers. An organization approved on day one has nothing provisioned.

To be clear about what this is: it is not a delay, and it is not a pending review. The approval is complete and confirmed in writing. The failure is that an approved record was never provisioned to our tenant, and no team with backend authority has acted on it.

We are still asking for the same Microsoft-side resolution, and only this:

- Repair or reset the existing approved registration record;

- Or manually map the already-approved Goodstack eligibility result to mindfulpeace.onmicrosoft.com;

- Or provide an official Microsoft-side migration path, coordinated with Goodstack in advance, that preserves our organization identity and prevents duplicate or broken records.

For the record: we asked for a committed Microsoft-side resolution by June 15. That date has passed without one. We are now documenting this experience publicly and evaluating alternative providers, because a nonprofit cannot keep its operations waiting indefinitely on a benefit approved three weeks ago.

If anyone at Microsoft with backend authority is reading: the request has never changed. Provision our approved eligibility to mindfulpeace.onmicrosoft.com. We would still genuinely prefer to close this thread with the story of how Microsoft made it right.

Case 2605290040003233 remains unresolved.

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.