All integrations

Databases

Azure Database integration

Azure SQL, PostgreSQL, MySQL and Cosmos DB in one dashboard, not four tools.

An Azure estate rarely has one database. The application sits in Azure SQL Database on the SQL Server engine, events land in Cosmos DB through its MongoDB API, and something else runs on Azure Database for PostgreSQL or MySQL. Flitch connects to all four with a connection string over TLS and reads tables and collections side by side, so a single dashboard or written report can put support tickets from Azure SQL next to usage events from Cosmos. Free to start, and no export step between the services.

  • Azure SQL Database, PostgreSQL, MySQL, and Cosmos DB
  • SQL login or Microsoft Entra (Azure SQL)
  • Schedule background refresh

How do you connect Azure Database to Flitch?

Connect read-only with a SQL login, a Microsoft Entra service principal for Azure SQL, or a connection string for Cosmos DB.

Connection stringMicrosoft Entra service principal (Azure SQL)

Start building

Pick a prompt to get started.

Azure Database integration FAQ

Which Azure databases does Flitch connect to?

Flitch connects to Azure SQL Database, Azure Database for PostgreSQL and MySQL, and Azure Cosmos DB (MongoDB API), all over TLS.

How do I connect Azure SQL to Flitch?

Use a SQL login or a Microsoft Entra service principal, then pick your tables. Flitch connects read-only and never writes back.

Can Flitch read Azure Cosmos DB?

Yes. Flitch connects to Cosmos DB via its MongoDB API with a connection string and imports collections as datasets.

Do I need SQL for Azure dashboards?

No. Describe the dashboard or written report in plain language and Flitch builds it. Custom SQL is available for the SQL engines.

How does Flitch keep Azure dashboards current?

Schedule a background refresh and Flitch re-pulls your Azure data on your chosen cadence.

Does Flitch copy my Azure Database data?

No. Flitch queries Azure Database where it sits and pushes the aggregation down as SQL, so it reads back totals rather than holding a copy of your tables. Nothing to keep in step, nothing extra to secure, and a large table stays your database's problem rather than something Flitch has to store. The queries are generated against your data model, so a figure means the same thing on every dashboard built from it.

Not the source you're after?