Facing Issue Switching Databricks Connection from Dev to Prod in Deployment Pipelines

[yedu]

Hi Everyone,

I’m working on a Power BI project where I need to switch the data source from Dev to Prod automatically when moving the report through Deployment Pipelines.

For SQL Server, it only needs two parameters (Server and Database), and the Power BI Service lets you create two parameter rules. So, no problem there.

But with Databricks, the story is different.
The connection needs more than two parameters
for example:

• Server hostname

• HTTP path

• Database

• Schema

When I try to set these up in Deployment Pipelines, the service only allows two parameter rules. After that, the Add rule option becomes disabled. Because of this, I can’t fully change my Databricks connection from Dev to Prod like I can with SQL Server.

What I have tried so far:

• Created separate parameters for each part of the Databricks connection.

• Tried using only the most important parameters to stay within the 2-rule limit.

• Tested different workarounds in Power Query, but none worked as expected.

The main blocker:
The two-parameter rule limit in the Power BI Service is stopping me from setting up Databricks environment switching in deployment pipelines.

As I’ve gone through Microsoft Learn, I found that when creating parameter rules in deployment pipelines, the Power BI service only supports changing two parameters per dataset per pipeline stage. The docs also say that this applies to all data sources and isn’t Databricks-specific, which could mean this is a general service limitation, not a Databricks issue.

I want to know from the community is, 

1. Is this two-parameter limit fixed for all connectors or just for Databricks?

2. Has anyone found a way to combine these values or use a custom connection string to bypass the limit?

3. Has anyone successfully switched Databricks connections between Dev and Prod in deployment pipelines?

Any help, advice, or even confirmation that this isn’t possible will be really helpful.

Thanks,

[v-echaithra]

Hi @yedu ,

I hope the information provided is helpful.I wanted to check whether you were able to resolve the issue with the provided solutions.Please let us know if you need any further assistance.

Thank you.

[v-echaithra]

Hi @yedu ,

We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.

Thank you for your patience and look forward to hearing from you.

Best Regards,
Chaithra E.

[v-echaithra]

Hi @yedu ,

We would like to confirm if you've successfully resolved this issue or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.

Thank you for your patience and look forward to hearing from you.

Best Regards,
Chaithra E.

[v-echaithra]

Hi @yedu ,

Thank you @jaineshp  for your inputs.

We would like to confirm if you've successfully resolved this issue or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.

Thank you for your patience and look forward to hearing from you.

Best Regards,
Chaithra E.

[jaineshp]

@v-echaithra,

Thank you for the kind recognition - always happy to contribute to our community's success!

Best Regards,
Jainesh Poojara | Power BI Developer

[jaineshp]

Hey @yedu,

Looking at your Databricks deployment pipeline issue, here are some practical solutions I've seen work:

Option 1: Smart Parameter Consolidation

• Create an "Environment" parameter (Dev/Test/Prod)
• Build all your connection details using Power Query conditionals based on this single parameter
• Use your second parameter slot for something like "DatabaseOverride" if needed

Option 2: Hybrid Approach

• Keep Server Hostname and HTTP Path as your two deployment rules
• Hard-code Database and Schema to be consistent across environments (most teams do this anyway)
• This covers 80% of use cases and stays within the limit

Option 3: Configuration Table Method

• Store all connection details in a simple config table/file
• Use one parameter to specify environment
• Let Power Query pull the rest automatically

Reality Check:

The 2-parameter limit is definitely a real limitation across all connectors, not just Databricks. SQL Server works because it only needs Server + Database, but anything more complex hits this wall.

What's Worked for Others:

Most people I've talked to either go with Option 1 (environment parameter) or just accept that some connection details need to be manually updated. Not ideal, but Microsoft hasn't addressed this limitation yet.

The environment parameter approach is probably your best bet - it keeps things clean and works within the existing constraints.

Fixed? ✓ Mark it • Share it • Help others!

Best Regards,
Jainesh Poojara | Power BI Developer