Changing the server/connection path in existing connection?

[KarloFabricMigr]

In Fabric in 'Manage connections and gateways', once the connection is created I can't edit the server of the SQL server anymore or base URL for API for example, it's greyed out. Is it possible to edit this without deleting the existing connection and recreating it?

This is an example for a connection for Fabric API, but it's the same thing for all my connections.
Can't change connection type, which makes sense, but I should be able to change the data source path.

edit: I created this connection, and even the tennant admin can't do this

[v-cboorla-msft · Accepted solution]

Hi @KarloFabricMigr 

Thanks for using Microsoft Fabric Community.

Unfortunately, it's a current limitation in Fabric that once a connection is created, certain properties like the server or base URL become read-only and cannot be edited. This is a deliberate design choice to ensure data integrity and prevent accidental changes to existing connections that might affect dependent workflows or datasets. As you have noticed, the connection type is also greyed out, which is intended to prevent changes that could invalidate the connection or its associated data. At present, the only way to modify these properties is to delete the existing connection and recreate it with the updated information. This ensures that any changes are intentional and deliberate.

However, your suggestion is definitely valuable! We use customer feedback like yours to prioritize future features. The more users who request the ability to customize backgrounds, the higher it moves on our list.

Appreciate if you could share the feedback on our Microsoft Fabric Ideas. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.

Thank you

[tomvdp]

Deleting and re-creating the connection isn't really a solution, is it? Apparently, that invalidates all the elements that use that connection. In our case that means we would need to reconfigure all the source mappings just because it is impossible to edit the name of the server in the connection! 

[bhanu_bi]

If a connection 'sql_dev' is used in pipelines, by deleting and recreating the connection, will those pipelines automatically pick the new connection by name ? 

Or do we need to update the setting in pipelines again by selecting the connection, tables and in turn there is lot of redevelopment.

We are in situation that requires us to change the server URL in our connection.

[tomvdp]

I'm curious as we are in the same situation here. Did you try deleting and re-creating using the same name? Did that change go smoothly or did you have to update everything that depends on the connection?

[v-cboorla-msft]

Hi @KarloFabricMigr 

We haven’t heard from you on the last response and was just checking back to see if your query got answered. Otherwise, will respond back with the more details and we will try to help.

Thank you.