# Orphaned Account - Would like to create a team and tenant

**URL:** <https://community.auth0.com/t/orphaned-account-would-like-to-create-a-team-and-tenant/204834>\
**Category:** Get Help\
**Tags:** signup, user-management\
**Created:** [October 29, 2026, 1:03pm UTC](https://community.auth0.com/t/orphaned-account-would-like-to-create-a-team-and-tenant/204834 "2026-10-29T13:03:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![engineering9](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/engineering9/32/81454_2.png) [@engineering9](https://community.auth0.com/u/engineering9)\
**Post date:** [October 29, 2026, 1:03pm UTC](https://community.auth0.com/t/orphaned-account-would-like-to-create-a-team-and-tenant/204834/1 "2026-10-29T13:03:48Z")

</div>

I have an orphaned account that i can sign-in with. I am trying to create a new team and tenant with it, however, i am getting a generic “Bad Request” failed when clicking the button to create the tenant and I cannot progress on my own.

Please help me remediate.

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [October 29, 2026, 11:16pm UTC](https://community.auth0.com/t/orphaned-account-would-like-to-create-a-team-and-tenant/204834/3 "2026-10-29T23:16:54Z")

</div>

Hi @engineering9

Welcome to the Auth0 Community!

**[Summary]**  
When an account is in an **orphaned state** —meaning your central Auth0/Okta identity user exists and can authenticate, but it is not linked to any active tenant or Team workspace—the portal tries to initialize the workspace context upon login.

**[Root Causes]**

1. **Missing or Corrupted User Context Linking:** The Teams provisioning service expects an active team membership or user profile metadata payload to bind the new tenant to. Because the orphaned account lacks these parent associations, the backend API schema validation rejects the creation request as malformed.

2. **Tenant Name / Region Restrictions:** The requested tenant domain might conflict with a soft-deleted/reserved name, contain unsupported characters, or fail backend regional policy constraints.

3. **Session Desynchronization at Callback:** If navigating through `accounts.auth0.com/teams`, the session handshake may drop the initial onboarding state before the tenant creation endpoint receives it.

* * *

### [**Workaround]** Self-Service Workarounds to Try First

Before waiting for manual platform intervention, check if you can bypass the broken Teams wizard using direct tenant-provisioning endpoints:

1. **Direct Tenant Creation Route:**

2. **Test in a Clean Context:**

If you. continue to have issues, please send a DM to the [@support](https://community.auth0.com/groups/support) group with the tenant name and email address associated with your Auth0 account.

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [November 8, 2026, 11:17pm UTC](https://community.auth0.com/t/orphaned-account-would-like-to-create-a-team-and-tenant/204834/4 "2026-11-08T23:17:39Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
