Provide a way to disconnect database connections from ArcGIS Pro

[ajelenGDi]

Please return Disconnect option for enterprise databases to the ArcGIS Pro as was in ArcMap. With one click in Catalog Pane.

Closing the ArcGIS Pro does not disconnect the user from enterprise geodatabase. Removing connection or showing users and locks is not appropriate solution.

This issue had already the enhancement submitted: #ENH-000084097 

[D_Atkins]

Clarifying but does this DisconnectUser count as 'the solution' for most use cases in this thread?

This operation is so infrequent and tailored to the database, I'd prefer to see a GUI button rather than having to tab over to and tinker with a script --- this morning, I rolled back to ArcMap to get this done, but I'd like to be prepared for the coming days when ArcMap is less an option...  

[MarceloMarques]

I agree the ability to connect and disconnect to an enterprise geodatabase in Pro is absolutely needed.
I posted this idea back in 2019 - Pro Contents Window Connected Geodatabases 

This issue already has an enhancement submitted: #ENH-000084097

This is in the queue and under consideration, just do not know when it might be implemented yet.

[MarcelBeckmann]

Wow. More than five years and status is still open. 

To me it seems so unprofessional to leave database connections just open and not being able to disconnect them. Although everybody knows the negative effects of open databaseconnections. 

[TamiOnstad]

Ran into this for the first time today and am shocked that this STILL has not been implemented.  Even changing user connection on a single connection file (changing from being connected as the SDE user and the data owner for different tasks) does NOT kill the first connection as the SDE user.  When I am done doing things as SDE I want to close that connection and switch to the data owner connection, but it is impossible to do this without closing and reopening the project, which is a HUGE hassle.  I am unfortunately trying to set up UN things, so I cannot easily move back to ArcCatalog for this work.  This is a huge, gaping hole in Pro functionality, so ESRI please provide a solution that does not involve closing and reopening my Pro project.