Power BI Azure Cosmos DB v2 Connector – Connection Error

[risfy2025]

Hello,
I'm experiencing an issue when trying to connect to Azure Cosmos DB using the v2 connector in Power BI Desktop (version 2.144.XXX).

Issue Details:

• I receive a "Cannot connect" error, but the details field is completely empty ("").
• The error occurs right after entering the endpoint and attempting to proceed to the next screen.
• The endpoint is copied directly from the Azure Portal and is confirmed to be correct.
• The same connection settings work fine on other PCs.
• The v1 connector connects successfully without any issues.

Question:

• Is this kind of error (with an empty details message) a known issue with the v2 connector?
• Are there any recommended troubleshooting steps or ways to check logs that might help identify the cause?

Thank you in advance for any insights or suggestions!

[V-yubandi-msft]

Hi @risfy2025 ,

Thanks for posting your query in the Microsoft Fabric Community. Based on your description, it appears the issue is occurring on a specific machine and only when using the Cosmos DB v2 connector. Since the v1 connector works fine and the same endpoint connects successfully on other PCs, we can identify this as a local setup issue.

Here are a few steps that might help resolve the problem.

1. Old credentials or cached metadata might be interfering so Clear cache, and also clear saved credentials under Data source settings.

2. Some features, like preview or beta connectors, may require elevated permissions, especially in environments with strict firewalls or proxy settings. Right click the Power BI Desktop shortcut and choose  Run as Administrator, then try connecting again.

3. Check Power BI Desktop Version Ensure you are using the latest version of Power BI Desktop, as earlier builds  might have compatibility issues with the v2 connector, which is still in Beta.

You can find Microsoft official guidance on the v2 connector setup and limitations 

 Power Query Azure Cosmos DB v2 (Beta)

Key limitations:

Thank you for your response @Ritaf1983 .

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.

[Ritaf1983]

Hi @risfy2025 

This type of error (a "Cannot connect" message with an empty details field) has been reported by others and may be related to a few common causes specific to the v2 Azure Cosmos DB connector in Power BI:

Possible Causes:

1. Missing or outdated .NET Framework components – the v2 connector may rely on specific runtime components that are not present on your machine, even if they exist on others.

2. Proxy or firewall settings – check if this PC is behind a proxy or has firewall rules that block specific outbound calls. The v2 connector uses different endpoints or protocols than v1.

3. Power BI Desktop version – you mentioned 2.144.XXX, which should be March 2024. Try upgrading to the latest version or testing with a slightly earlier build (some builds introduced silent breaking changes).

4. Credential cache corruption – try deleting the cached credentials from:
   File > Options and settings > Data source settings > Clear Permissions
   and restart Power BI.

5. Authentication method mismatch – the v2 connector may be trying to use a different authentication protocol (e.g., Managed Identity or OAuth2) which isn't supported on your local environment due to configuration issues.

Logs and Troubleshooting Steps:

• Check Power BI logs located at:
  C:\Users\<YourUsername>\AppData\Local\Microsoft\Power BI Desktop\Traces
  Open the latest .txt file and search for CosmosDB, v2, or any timestamp around your last connection attempt.

• Enable tracing (from Options > Diagnostics) and reproduce the error – this gives more verbose logs.

Additional Suggestions:

• Try to connect via the v2 connector on a different user profile on the same PC to rule out profile-level issues.

• If it works on other PCs but not this one, use Fiddler or Wireshark to compare network traffic between the working and failing machine (look for blocked ports or DNS issues).

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly