Changing the source connection info

For on-premises connections in Fabric, items like connection type, server name, and authentication mode are fixed at creation time. Fabric treats these as immutable. This design keeps lineage, security, and gateway bindings consistent. Because of this, editing the server or connection type in place is not supported.

What you can do instead.

1. Recreate the connection
   This is the supported path today. Create a new connection with the updated server or connection type, then rebind your Lakehouse, Warehouse, Dataflow Gen2, or pipeline to the new connection. This feels heavy, but it avoids hidden breakages.

2. Use DNS or aliases for future changes
   If the change is server-related, use a DNS alias or SQL Server alias. Point Fabric to the alias once, then handle server changes at the network or database layer. This reduces future reconnection work.

3. Centralize gateway connections
   If you are using an on-premises data gateway, manage connection definitions centrally and keep naming stable. This helps limit downstream updates when environments change.

4. Parameterize at the data layer, not the connection
   You cannot parameterize the Fabric connection itself, but you can parameterize database names, schemas, or queries inside Dataflows Gen2 or notebooks. This gives some flexibility without touching the connection.