MS Fabric - Event house unavailable

[kzelentsov]

Good day,

I have Admin role within workspace which hosted in Ms Fabric Capacity (F2).

Within the workspace I do have multiple entities (pipelines, notebooks, lakehosues, eventhouse) and I'm able to run, delete, create, modify, read all entities except eventhouse.

It was deployed long time ago by developer who is no longer part of the company.

I updated ownership for all objects, including event house, but whenever I'm trying to open it - getting an error:

Access error:  Can't access the Eventhouse. Check your network for a VPN preventing access.

I do not have any VPN or specific netwroks settings for this workspace, capacity, event house.

I tried to restart MS Fabric Capacity multiple times but without success. All items related to this workspace works fine except the event house.

Your assistnace, suggestions are highly appreciated.

[v-shchada-msft]

Hi @kzelentsov, 
Thank you for reaching out to the Microsoft Fabric Community Forum and thanks to @pallavi_r and @MJParikh for sharing helpful insights.

Just checking in, were you able to resolve the issue? If not please feel free to share an update and we will be happy to assist further.
Your feedback will also help others facing similar challenges.

Thank you.

[kzelentsov]

unfortunately I was not able to resolve the issue, considering that above eventhouse was created for non-prod environment we decided to delete it and recreate from scratch. But root cause still undefined. 

[v-shchada-msft]

Hi @kzelentsov,

Thank you for the update. Since recreating the Eventhouse resolved the issue, this points more toward stale or orphaned backend metadata or permissions tied to the original Eventhouse rather than the workspace, capacity, or network configuration itself.

Although the exact root cause could not be confirmed, if this happens again in a production environment, I would recommend opening a Microsoft Support ticket before deleting the item so the backend state can be investigated further.

Thanks and Regards.

[pallavi_r]

Hi @kzelentsov ,

Since the Eventhouse was originally created by a developer who is no longer with the company, this seems to be an orphaned permission issue where item-level permissions override your workspace Admin role. As workspace Admin, you should have access, but Eventhouse creators can set item-level restrictions that persist even after ownership changes.

If you've already attempted to take ownership and the issue persists, it indicates stale/orphaned permissions on the backend that cannot be resolved through the UI. Better to open a Microsoft Support ticket for i) Review and reset the Eventhouse permission state;ii) Clearing any orphaned owner credentials from the departed developer iii) Release the item-level permission lock blocking Admin access

If this post helps, please accept this as a solution. Appreciate your kudos.

Thanks,

Pallavi

[MJParikh]

Hi @kzelentsov ,

The error message points to a network issue, but in most cases the root cause sits elsewhere with Eventhouse. A few areas worth checking.

Ownership change at the workspace level does not always cascade to the underlying Kusto database principals. Open the Eventhouse database details and confirm the Database Admin role lists your account, not only the former developer. Run .show database principals against the database to verify. If your account is missing, add yourself through .add database YourDBName admins ('aaduser=your-upn').

The "VPN preventing access" message often fires when the browser fails to reach the Kusto cluster endpoint. Check tenant admin settings under Fabric Tenant settings for any block on public network access to OneLake or Eventhouse workloads. Also test in a private window with extensions disabled, since ad blockers and corporate proxies sometimes block the kusto.fabric.microsoft.com endpoint silently.

F2 SKU sits at the lower end for Eventhouse. Confirm your capacity stays Active during access attempts, since throttling on F2 surfaces as obscure errors rather than clear capacity warnings. Scale temporarily to F4 or F8 and retest.

When an Eventhouse was provisioned long ago, the underlying cluster metadata sometimes drifts after platform updates. Spin up a fresh Eventhouse in the same workspace as a sanity check. If the new one opens fine, the older one likely needs a support ticket, since orphaned ownership from a departed developer does not always repair from the UI alone.

For deeper diagnosis, capture a network trace using F12 Network tab while opening the Eventhouse. Look for failing 403 or 401 calls against the kusto endpoints. The response body usually names the exact authorization failure, which gives Microsoft support a faster path to resolution.

Hope this helps.

Thank you!
Proud to be a Super User!
📩 Need more help?
✔️ Don’t forget to Accept as Solution if this guidance worked for you.
💛 Your Like motivates me to keep helping

@kzelentsov