Naming connections for deployment pipelines

[pmscorca]

Hi,

I'm managing a Fabric data platform solution having 3 workspaces, one for specific environment (ws_xxx_dev, ws_xxx_test, ws_xxx_prod) and each workspace has a lakehouse (lh_xxxx without any references to the environment), a warehouse (wh_xxxx without any references to the environment) and some pipelines (pl_xxxx without any references to the environment).

The created connections, that represent tenant resources and not workspace resources, are named as cn_sourcetype_environment (f.e. cn_SQL_dev, cn_SAP_dev and so on): in order to use the deployment pipelines to promote the workspace items, is it right the adopted naming for the connections? Thanks 

[wardy912 · Accepted solution]

Hi @pmscorca 

 Yes: using environment-specific connection names like cn_SQL_dev, cn_SAP_test, cn_<source>_prod is good practice for Fabric deployment pipelines. It makes promotion predictable and allows you to map or swap connections per stage without renaming workspace items.

--------------------------------

I hope this helps, please give kudos and mark as solved if it does!

Connect with me on LinkedIn.

Subscribe to my YouTube channel for Fabric/Power Platform related content!