PowerApps - Connections will not delete - Allow / Don't Allow keeps coming back

[sgregory]

I can't seem to get rid of orphan connections... There are no data souces used for these connections. In previous version of the app I was testing how to set up connects. Once I figured out how and what method I wanted to use I then removed the data sources and the connections for it. But they won't go away and it is keeping the connection I do need to use from being able to use it.

Each time I open the app I have to delete all the data souces and then re-connect to the SQL Server connection I actually do use.

I have tried everything from saving the app then re-importing it to see if that help. It doesn't...

I've tried deleting old versions of the app and only keeping the ones that use the connect I need. That doesn't work.

I've tried creating a new app and coping the objects (screens, buttons, etc.) to the new app but it won't allow me to do that either.

I can't have end-users removing data sources then adding them back in each time simply because of these orphan connections.

[esunilkumare]

Go to Home -> Dataverse -> Connections -> <Select three dots on your connection> -> Delete. This will delete your connection.

Refer the attached image

[Pstork1]

Just be aware that the connection may be used by multiple apps.  If you delete it there then you will delete it from all the other apps as well.

[suman_sa]

 @sgregory How do we spot this orphan connection. I checked my app code in VS Code, but not sure where to find it. this connection and the flow that used this is already deleted (I just remember it could be an Excel for Business connection, but not sure.) any suggestions, please?

[sgregory]

It will be a connection in PowerApp UI that won't delete and there is nothing using it. Check to see if the connection is using your PowerApp. If it is not, that GUID will be the one that will need to be deleted when you export the code. You will have to reimport the code after it is deleted.

[leonsig93]

Just adding on to this in case anyone runs into the same issue.

For instances where the connector was pulling in from Power Automate, you need to recreate the flow from scratch. Don't save a copy. For some reason, even though you edit the flow and remove any connections or steps associated the connection will persist on the PowerApps side.

Recreating an entire flow might be really inconvenient if its a long complex flow, but if modifying the export package isn't working for some reason (like it wasn't for me) this did.

My case was Outlook connection started failing for some users blocking their access to our apps. We had removed all Outlook steps from the original flow and replaced it with the basic Mail version instead. This worked for some users but not all. This recreate approach took care of it for everyone.

[AshleyH7]

I am attempting to follow these instruction to remove a hidden connection in my power app, but its not working. I am not sure if I am deleting the right information, or too much? when I attempt to import the App it fails. 

Can you help ? 

[sgregory]

I have not had to do this in a few years. I would recommend that you put in a support ticket to Microsoft support. Most likely the support ticket would be free with your support plan.

[AshleyH7]

oh, I have one. They have no idea what to do, Its been almost a week and after a teams call and additional misc. troubleshooting they are trying to figure it out. 

[Powerappy]

Just to add to this as someone who's recently experienced this issue with an HTTP with Azure AD connector which was 'cached' in an app which was no longer using the connector, I had follow @esunilkumare's suggestion and to go to Power Apps > Connections > Delete the offending connection. This was reportedly being used by 2 apps and 2 flows. Once I'd deleted it, I went into the Flows and was able to re-establish the connection (which was correct), the apps are no longer showing as using the connection (which is also correct). 

[benmashley]

Hey Toltekrom, Sorry only just seen your reply. I have updated my solution with a few notes and a few changes. Hope you managed to get it sorted