Providing secure, identity-based access to private apps and resources without traditional VPNs
Global Secure Access - Private Network Connector not recognized by tenant (Tenant ID not found error)
I'm setting up Microsoft Entra Private Access (Global Secure Access) and I'm stuck
because my Private Network Connector isn't being recognized by the tenant.
If anyone has encountered a similar issue or has insight into a solution,
I'd really appreciate your help.
■ Environment
- Tenant region: Japan
- Connector server: Windows Server 2022 (Azure VM, Japan East region)
- License: Microsoft Entra Suite (includes Private Access)
■ Steps performed
- Activated Global Secure Access for the tenant
- Installed the Private Network Connector on Windows Server 2022
- Signed in with a Global Administrator account and completed connector registration
- Enabled the "Private Access profile" under Traffic forwarding
- Installed the Global Secure Access client on a separate PC and signed in
■ Items confirmed to be working correctly
- Connector Diagnostics tool results:
- Certificate Check: Passed
- Port Connectivity Check: Passed (port 443 to login.microsoftonline.com)
- Certificate Revocation List Check: Passed
- Connector Service / Updater Service: Both Running
- Endpoint Connectivity Check: Bootstrap Passed, TrustRenewal Passed
- Confirmed that browsing directly to https://login.microsoftonline.com from the connector server successfully displays the sign-in page
- The Global Secure Access client shows "Connected" status, with all channels (Entra / M365 / Private) showing as Connected
- NSG outbound rules are all set to Allow
- The Global Administrator role is assigned and shows as Active
- The VM region (Japan East) matches the tenant's default country/region (Japan)
■ The problem
Despite everything above being confirmed normal, the connector never appears
under [Global Secure Access] > [Connect] > [Connectors and sensors] in the
Microsoft Entra admin center (tried clearing browser cache, using private/
incognito windows, and reinstalling/re-registering the connector multiple
times — none of it resolved the issue).
A banner is persistently displayed at the top of the page stating:
"Private Network is currently disabled for your tenant."
Additionally, when trying to create an Application Segment under an
Enterprise Application, I get the following error:
"The requested tenant ID: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' was not found."
This tenant ID matches both my actual tenant ID and the CN on the connector's
certificate (Subject: CN=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
■ Questions
- Has anyone else run into this same "Tenant ID not found" error?
- Could this be a backend provisioning issue on the tenant side? If so, does anyone have insight into how long this typically takes to resolve?
- After a license is assigned, how long does it typically take before Private Access features become fully functional/provisioned?
Thank you in advance for any guidance.