External ID free-trial tenant provisioning returns HTTP 404 — how to verify tenant status?

The HTTP 404 does not confirm that the tenant was created, reserved, or left pending; keep the retry paused and ask Microsoft Support to query the backend operation using the exact timestamp, requested domain, and request/correlation IDs.

What can be established publicly

• The free-trial workflow supports a personal Microsoft account and does not require an Azure subscription. It remains a preview feature.^1^
• Successful completion is indicated by “The tenant is created” in VS Code → View → Output. A completed tenant should then be accessible from the Entra admin center or Azure portal.^1^
• Microsoft documents that tenant creation can take up to 30 minutes.^2^
• Closely matching reports describe NotFound followed by a provisioning state, but neither report has an accepted or recommended answer establishing how users can inspect that backend state.^3^^4^
• The referenced extension issue remains open, so it does not confirm either successful creation or a service-wide outage.^5^

Tenant-name availability returning HTTP 200 only confirms that the availability check completed; it does not establish the result of the subsequent creation request. DNS and OIDC discovery are likewise not authoritative tenant-provisioning status checks. The custom-domain DNS troubleshooting guidance concerns configured custom sign-in domains, not creation of an onmicrosoft.com trial tenant, so it does not apply here.

Preserve the evidence

Save the complete Microsoft Entra External ID output channel before restarting VS Code or clearing extension data:

1. Open View → Output.
2. Select the External ID/Entra extension channel.
3. Save:
   • UTC start and failure times;
   • requested onmicrosoft.com domain;
   • selected tenant-data location;
   • extension version 1.0.10;
   • full response status and body;
   • request, correlation, operation, or activity IDs;
   • whether “The tenant is created” ever appeared.
4. Redact access tokens, cookies, authorization headers, and personal identifiers before posting logs publicly. Diagnostic guidance recommends supplying timestamps and request/correlation IDs through an approved support channel.^6^

Request an authoritative backend check

Because there is no subscription and the account cannot enter the Entra admin center, use Microsoft’s public support entry point and select the personal account path, then Get Help/Contact Support.^7^

Ask support to determine:

1. Whether mapotestpoc2026.onmicrosoft.com has a directory/Tenant ID.
2. Whether the name is reserved by an incomplete CreateCIAMTrialDirectoryAsync operation.
3. Whether that operation is pending, failed, rolled back, or orphaned.
4. Whether it is safe to retry with the same domain.
5. Whether the free-trial provisioning service was healthy in the selected region at 2026-11-06 09:02:49 UTC.

Include links to issue #30 and the two matching Q&A incidents. Do not post an unredacted token or complete authentication trace.

Only Microsoft’s service telemetry can answer whether the endpoint was functioning at that timestamp or whether this specific request left backend state. If support confirms no directory or reservation exists—or clears an orphaned operation—retry once. If a Tenant ID exists, request restoration of administrative access instead of creating another tenant.

References

1. Visual Studio Code extension for External ID - Microsoft Entra External ...
2. Create an external tenant
3. Entra External ID tenant creation returns NotFound, then remains in ...
4. Microsoft Entra External ID tenant stuck in Provisioning with zero ...
5. #30 Free trial tenant creation returns HTTP 404 after selecting Austria
6. Troubleshoot intermittent timeouts and slow Microsoft Entra provisioning to on-premises Active Directory
7. Contact Microsoft customer support | Microsoft Support