![\"dab](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2026\/11\/dab_connstring.webp\")
<\/a><\/p>\nThis means a single environment variable can supply the database connection for any configuration, including (and this is the point of this article) the basic configuration bundled in the base Data API builder container image.<\/p>\n
A local POC in the blink of an eye<\/h3>\n
With this one value, developers can get started without building a custom image or mounting a configuration file. If you’re using Docker on your local development machine, you can configure a working MCP endpoint with a command as simple as this:<\/p>\n
docker run --name dab -p 5000:5000 \\\r\n -e 'DAB_CONNSTRING=Server=XXX;Database=XXX;User Id=XXX;Password=XXX;TrustServerCertificate=True;' \\\r\n mcr.microsoft.com\/azure-databases\/data-api-builder:2.0.12<\/code><\/pre>\nThe endpoint is available at http:\/\/localhost:5000\/mcp<\/code>, assuming the container starts successfully and can connect to your database.<\/p>\nAn Azure POC in the blink of an eye<\/h3>\n
Since this capability ships as part of the container image, Azure deployments or any other deployments get the same benefit as local development. Here are a few easy options.<\/p>\n
Azure Container Apps Express<\/h4>\n
With Azure Container Apps Express, you can deploy an MCP endpoint using a single command, without building a custom image or mounting a configuration file. Express automatically provisions the Container Apps environment, too.<\/p>\n
aca express create `\r\n --subscription XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX `\r\n --resource-group XXX\r\n --name dab `\r\n --image mcr.microsoft.com\/azure-databases\/data-api-builder:2.0.12 `\r\n --ingress external `\r\n --target-port 5000 `\r\n --env-vars 'DAB_CONNSTRING=Server=XXX;Database=XXX;User Id=XXX;Password=XXX;TrustServerCertificate=True;'<\/code><\/pre>\n<\/i>Azure Container Apps Express is in preview<\/strong><\/p>\nThis assumes your Azure subscription and resource group are already configured. The syntax has been verified against ACA CLI 1.0.0-preview.4.\n<\/div><\/p>\nAzure Container Apps<\/h4>\n
If you don’t want to use ACA Express, you can accomplish a similar deployment with regular Azure Container Apps. Assuming you’ve already created a Container Apps environment, the Azure CLI command is nearly as simple:<\/p>\n
az containerapp create `\r\n --subscription XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX `\r\n --resource-group XXX\r\n --name dab `\r\n --environment XXX `\r\n --image mcr.microsoft.com\/azure-databases\/data-api-builder:2.0.12 `\r\n --ingress external `\r\n --target-port 5000 `\r\n --env-vars 'DAB_CONNSTRING=Server=XXX;Database=XXX;User Id=XXX;Password=XXX;TrustServerCertificate=True;'<\/code><\/pre>\nAzure Container Instances<\/h4>\n
If you’re not an Azure Container Apps customer and prefer Azure Container Instances (ACI), you can accomplish a similar deployment just as easily:<\/p>\n
az container create `\r\n --subscription XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX `\r\n --resource-group XXX\r\n --name dab `\r\n --image mcr.microsoft.com\/azure-databases\/data-api-builder:2.0.12 `\r\n --ports 5000 `\r\n --ip-address Public `\r\n --environment-variables 'DAB_CONNSTRING=Server=XXX;Database=XXX;User Id=XXX;Password=XXX;TrustServerCertificate=True;'<\/code><\/pre>\nAzure Kubernetes Services<\/h4>\n
Finally, if neither ACA nor ACI is your preferred approach and your enterprise has standardized on Azure Kubernetes Service (AKS), you’re in luck. The same deployment is possible there, too, assuming your Kubernetes context already points to the intended AKS cluster:<\/p>\n
kubectl create deployment dab `\r\n --image=mcr.microsoft.com\/azure-databases\/data-api-builder:2.0.12\r\n\r\nkubectl set env deployment\/dab `\r\n 'DAB_CONNSTRING=Server=XXX;Database=XXX;User Id=XXX;Password=XXX;TrustServerCertificate=True;'\r\n\r\nkubectl expose deployment dab `\r\n --type=LoadBalancer `\r\n --port=5000 `\r\n --target-port=5000<\/code><\/pre>\nIs it really that easy?<\/h2>\n
It is. And you can rest assured that you’re not relying on an undocumented trick intended just for testing. The basic configuration baked into the Data API builder image makes it possible to get an MCP Server running without preparing a configuration file yourself. It’s a fast way to see how effectively agents can operate over your data.<\/p>\n
But is this for production?<\/h3>\n
Not really, at least not without considering the configuration defaults. There’s nothing inherently wrong with a dynamically generated configuration, but the base image configuration was designed for developers. It defaults the hosting environment to development<\/code>, enabling Swagger and Nitro for endpoint testing and setting Health endpoint access to anonymous. Perhaps most important is that CRUD permissions allow all operations, including mutations, for anonymous users. SQL MCP Server doesn’t, and can’t, bypasses database security, but wide-open access on any endpoint in production is pretty uncommon.<\/p>\nHaving said that, now you know.<\/strong> Whether you’re investigating the technology and want the lowest-friction starting point or you are building a proof of concept and want to get up and running fast, SQL MCP Server’s new default configuration in the base image opens up exciting possibilities to get you where you want to go even faster.<\/p>\nLearn more about SQL MCP Server<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"Deploy Microsoft’s SQL MCP Server in minutes without a configuration file. Learn how DAB_CONNSTRING enables fast deployment using Docker, Azure Container Apps, ACI, or AKS.<\/p>\n","protected":false},"author":96788,"featured_media":7184,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1,597,720],"tags":[],"class_list":["post-7888","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure-sql","category-data-api-builder-2","category-sql-mcp-server-2"],"acf":[],"blog_post_summary":"
Deploy Microsoft’s SQL MCP Server in minutes without a configuration file. Learn how DAB_CONNSTRING enables fast deployment using Docker, Azure Container Apps, ACI, or AKS.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/posts\/7888","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/users\/96788"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/comments?post=7888"}],"version-history":[{"count":2,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/posts\/7888\/revisions"}],"predecessor-version":[{"id":7914,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/posts\/7888\/revisions\/7914"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/media\/7184"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/media?parent=7888"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/categories?post=7888"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/tags?post=7888"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Release](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2026\/06\/2.0-300x300.webp\")
<\/a>