I’m considering using Metabase and my organization is pretty tied into Azure. Curious to hear if there are people using Metabase predominantly with Azure services and if there are any nuances to keep an eye on.
At first glance, running Metabase from a Docker image seems like it would make the most sense and
we would be connecting to an Azure SQL Server. Would be really cool if we could connect to Data Lakes and Data Warehouses though.
Hi @crawforc3
You should be able to connect without any problems to Azure SQL Server - the past two years, Metabase has been using the Microsoft JDBC driver, which is compatible with Azure too.
And using the Docker image might be the easiest way.
Just remember to store the metadata (the Metabase settings and data) in Postgres/MySQL and not the default H2, which is not recommended for production.
https://metabase.com/docs/latest/operations-guide/running-metabase-on-docker.html
As for “Data Lake” and “Data Warehouse”, I’m not sure what type of connection they use.
Metabase currently “only” has about 15 drivers, so if those cannot connect, then you’re at a loss.
Thanks flamber, metabase looks like the hero this world needs 
Where can I find the list of db drivers?
Here’s the list of Metabase supported drivers:
https://metabase.com/docs/latest/administration-guide/01-managing-databases.html
And then you have to look for drivers created by other people - they mostly comment on the driver issues, if they have created one or are working on it:
https://github.com/metabase/metabase/issues?q=label%3A"Database+Support"
Has anyone managed to connect to Azure SQL? I’ve had a lot of trouble and just wondering if its possible. If so, can you post a screenshot of the configuration? I just get timeout errors no matter how I try to configure the Additional JDBC connection string options
Any help is greatly appreciated. Thanks!
Figured it out! My issue was: you have to manually enter the port number, "1433". Leaving the default does not connect to Azure SQL. Other settings here:
@briandouglasbdc Great that you found a solution. When leaving the field Port empty, then it allows use of Dynamic Ports on SQL Server, but I don’t think Azure SQL has that option, so you need to define a port in that case.
