Meet the new Fabric connector in Cognos Analytics 12.1.1
Microsoft Fabric excels at data engineering at scale, but insight only delivers value when it is trusted. The latest release from IBM allows Cognos Analytics to sit on top of Fabric to provide well governed, consistent and auditable analytics, bridging the gap between modern data platforms and enterprise decision‑making.
That shift becomes tangible in Cognos 12.1.1, which quietly unlocks something big for mixed Microsoft–IBM users: native connectivity to Microsoft Fabric Warehouse and Lakehouse (SQL analytics endpoints). In practical terms, your Cognos authors can now point reports, dashboards, and data modules directly at governed Fabric data.
Why should you care?
You remove a whole layer of extract/land/refresh plumbing. Governance stays in Fabric workspaces, row-level permissions continue to apply, and Cognos just… reads the facts. That speeds up delivery, reduces duplication, and lets BI teams focus on modelling rather than moving data.
“But it’s just the SQL Server JDBC driver” – absolutely not, the JDBC driver is just the engine. The Fabric connector is a lot more: correct endpoint assumptions, Entra-friendly auth posture, Cognos-tested support matrix, and a smoother admin/modelling experience tuned for Fabric’s Warehouse/Lakehouse SQL endpoints.
So what’s it all about?
Direct data-server connections from Cognos to Fabric Warehouse and to Lakehouse SQL analytics endpoints, using Microsoft’s SQL stack.
✓ Standard-based drivers: JDBC inside Cognos, and ODBC/OLE DB support on the Fabric side for admin flexibility.
✓ Microsoft Entra ID (Azure AD) auth patterns, including service principals for headless/server connections, aligning with your existing Fabric workspace security.
Security and governance
Fabric’s SQL endpoints enforce workspace/item permissions and row/object access. Cognos simply inherits what your Entra identity is entitled to read, so there’s no parallel ACL to maintain in Cognos.
When to use it
• You already curate data in Fabric and want Cognos reports/dashboards directly over governed tables.
• You’re modernising from Synapse or Azure SQL and standardising on Fabric, but keeping Cognos as your enterprise BI layer.
• You want performance and security enforcement in Fabric.
The Bottom line
With Entra-based auth, standard drivers, and workspace-level governance, it’s a clean, supportable way to put Fabric data in front of your Cognos authors and execs.
Want to see what this looks like in your environment?
We can walk through the Fabric connector with your data, your security model, and your Cognos use cases to help you decide whether it’s the right approach.
