The knowledge sources don't explicitly mention connecting GoodData to Cosmos DB mirrored in Microsoft Fabric, so I can't give you a definitive answer on that specific setup. However, here are some relevant options based on what the documentation does cover:
Option 1: Synapse SQL Connector If your Cosmos DB data is exposed via a Synapse SQL endpoint (even through Fabric mirroring), GoodData does have a native
Synapse SQL connector. [
Synapse SQL Docs]
Option 2: FlexConnect (Most Flexible) Given the deprecation of Synapse Link for new Cosmos DB accounts,
FlexConnect is likely your best path forward. It allows you to connect to virtually any data source — including APIs, NoSQL databases, and custom endpoints — using Python code, without needing a native connector. [
FlexConnect Docs]
FlexConnect specifically supports:
• NoSQL databases (including MongoDB as a documented example, which shares similarities with Cosmos DB's document model)
• Custom API integrations
• Any source reachable via code
Option 3: Other Native Connectors Depending on how your Fabric-mirrored data is exposed, you might also be able to reach it via
PostgreSQL or
Microsoft SQL Server endpoints if Fabric surfaces it that way. [
Supported Databases]
My recommendation: If Fabric mirroring exposes a SQL-compatible endpoint (e.g., Synapse SQL or SQL Server), use the corresponding native connector. If not, FlexConnect is the most flexible and future-proof approach for a non-standard source like Cosmos DB. I'd suggest reaching out to GoodData support directly for guidance on the specific Fabric mirroring scenario, as the knowledge sources don't cover it explicitly. 👍 0 button 👎 0 button ℹ️
Tip: Mention
@kapa.ai in the thread for follow-ups.
👀 Our Support team monitors all messages and will jump in if needed.