Forum Discussion

Jerry4's avatar
Jerry4
Copper Contributor
Aug 21, 2026

Founders Hub verification stuck 2+ weeks — Entity Name field error, "Unmanaged tenant"

Hi team,

I'm hoping someone from the Startups team can help unstick a support case that's been open for over two weeks with no resolution.

Background:
Our initial Founders Hub application accidentally recorded our website domain in the "Entity Name" field instead of our actual legal business name. I caught this and tried to correct it myself via Partner Center, but the self-service profile page returns a 404 — because our account is registered as an "Unmanaged" Azure for Startups tenant, which doesn't have a full self-service Partner Center portal enabled. As I understand it, Microsoft intentionally locks backend editing for unmanaged/pending-vetting records, so the correction has to be made manually by a Microsoft agent.

I opened a support request with the correct legal entity details attached (California Articles of Organization + IRS EIN confirmation) so this can be manually corrected and re-triggered for verification, but the case has been sitting open with no update.

Details:

  • Support Request ID: 2608070010000038
  • Created: Aug 6, 2026
  • Follow-ups sent: Aug 16 (x3) and Aug 20, all with no substantive response
  • Severity: currently "C" — I attempted to raise it myself but the portal does not allow changing severity on this ticket
  • Support plan: Basic
  • Correct legal entity info already provided in the ticket.

What I need:

  1. Manual backend correction of the Entity Name field from our domain to "ByteHub AI LLC" so verification can proceed.
  2. Since I can't self-escalate severity on a Basic plan ticket, could someone from the Startups team flag case 2608070010000038 for internal escalation, or point me to the right channel to request that?

This is currently blocking us from accessing any Founders Hub benefits beyond the initial credit, so any help moving this along would be much appreciated.

Thanks,
Jerry

No RepliesBe the first to reply