How to delete Connections that have no owners

[r_Gao]

Hello the owner of a connection in fabric left the organization and now no one is able to delete the connection - even our fabric admins. Can someone please tell us what you may have done to delete connections that don't have owners? 

[burakkaragoz]

Hi @r_Gao ,

You’ve raised a very important governance issue, and the replies above are accurate—currently, Microsoft Fabric does not provide a built-in way for admins to reassign or delete orphaned connections if the owner has left the organization.

To summarize your options:

1. Reactivating the Owner’s Account:
   If possible, temporarily reactivate the departed owner’s account and have them delete the connection.
2. Microsoft Support Request:
   If reactivation is not possible, you will need to raise a support ticket with Microsoft. Clearly mention that:
   • The connection owner’s account is no longer active (left the org).
   • Even Fabric Admins cannot delete or reassign the connection.
   • You require Microsoft to either forcibly delete or reassign the connection.
   • Here is the link to raise a support ticket.

Note:
Unlike Power Automate, Fabric currently does not allow privileged users to assign themselves as owners or co-owners of orphaned connections.

Hopefully Microsoft will add more flexible admin controls for these scenarios in the future, but for now, contacting support is the only way forward.

Let us know if you need help drafting the support request or if you receive any updates from Microsoft!

[v-aatheeque]

Hi @r_Gao ,

Just checking in with regarding the issue you reported about not being able to delete a connection after the owner left the organization.

As mentioned earlier, the recommended path forward is to raise a support ticket with Microsoft, especially since Fabric Admins currently don’t have permissions to manage or remove connections without an owner. This will allow the Microsoft support team to evaluate tenant-specific configurations and assist with forcibly deleting or reassigning the connection.

If you've already raised a support request, feel free to update the thread so others can benefit from your experience.

If we don’t hear back shortly, we may close this thread in accordance with our community guidelines but you’re always welcome to start a new post if needed.

Thank you again for being a valuable part of the Microsoft Fabric Community! Let us know if you need help creating the support ticket.

[nilendraFabric]

Hi @r_Gao 

Microsoft Fabric currently lacks a direct, built-in method for admins to reassign or take ownership of orphaned connections, unlike Power Automate, which allows privileged users to add themselves as co-owners to orphaned flows

If possible recactive the user account else ms support is the last resort 

[v-aatheeque]

Hi  @r_Gao
  Thanks for your Prompt Response, In addition to that :Since ownership cannot be changed manually through the UI if the owner has left:

• You’ll need to raise a support request with Microsoft to forcibly reassign or delete the connection.

• Mention that the original owner’s account is no longer active and that even Fabric Admins are unable to manage the connection.

• In this scenario i suggest you to raise a support ticket here. so, that they can assit you in addressing the issue you are facing. please follow below link on how to raise a support ticket:

  How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

  Hope this Helps !!
  
  

  If this post was helpful, please consider marking Accept as solution to assist other members in finding it more easily.