Static Web App Database Connection Issue

Question

Static Web App Database Connection Issue

Alan Davis 0

I have been using an Azure Static Web App with a DB Connection to an Azure SQL server which it appears is being / has been retired - what do I need to do to get this to continue to work?

2 answers

Your answer

Answer 1

Hii Alan,

Thank you reaching us regarding the issue.

It sounds like you're facing some challenges with your Azure Static Web App's database connection due to the retirement of the current feature. Here’s what you should consider to keep your app functioning properly:
Steps to Continue Using Database Connections:

Configuration File: Ensure that you have a staticwebapp.database.config.json file in your configuration folder. This file is essential for database connections. The default folder name is swa-db-connections, but if you've configured a different name, make sure it aligns with your data_api_location in the build workflow file.
Database Type: If you're using Azure Cosmos DB, you need to reference a staticwebapp.database.schema.gql file within your configuration. This schema file must define your database's structure.
Migration: Since the Azure Static Web Apps database connection feature will be retired on November 30, 2025, it's recommended to migrate to a self-hosted Data API builder instance on Azure Container Apps.
Local Development: If you're developing locally, you can use the Azure Static Web Apps CLI to manage your database connections. Make sure to start the CLI correctly by using the --data-api-location option pointing to your configuration folder.
Post-Migration Support: If you have issues specific to configuring or developing with the Data API builder post-migration, consider reaching out to the Data API Builder GitHub forum for assistance.

Reference:
https://learn.microsoft.com/en-us/azure/static-web-apps/database-overview
https://learn.microsoft.com/en-us/azure/static-web-apps/database-azure-sql?tabs=bash&pivots=static-web-apps-rest#configure-the-static-web-app
https://learn.microsoft.com/en-us/azure/data-api-builder/overview

Kindly let us know if the above comment helps or you need further assistance on this issue.
Please "upvote" if the information helped you. This will help us and others in the community as well.

Alan Davis 0 Reputation points

2025-12-08T16:28:40.2566667+00:00

Thank you for this are you able to reach out and assist me further?
Alan Davis 0 Reputation points

2025-12-08T18:53:42.97+00:00

@Golla Venkata Pavani are there any detailed step by step instructions that would assist me to make this transition?

Answer 2

Adam Zachary 2,025

I ran into this change with one of my customers not long ago.

Azure quietly retired the old Static Web App “built-in database connection” preview feature, so anything that relied on that older model will stop working.

You’ll need to move to a proper API layer. The current, supported approach is to connect your Static Web App to Azure SQL through an API built in Azure Functions or Azure App Service, using managed identity or a normal connection string. Once we switched to that model, everything worked again.

In short, the old DB connection feature is gone. You just need to replace it with an API that handles the SQL calls securely and directly.

Alan Davis 0 Reputation points

2025-12-08T21:12:49.0466667+00:00

Are you able to prove more detail or point me in the right direction @Adam Zachary
Adam Zachary 2,025 Reputation points

2025-12-08T21:22:21.7333333+00:00

Sure Alan, happy to point you in the right direction.

Now that Microsoft has officially confirmed the retirement of the built-in Static Web Apps database connection feature, the supported path moving forward is to shift the database access into a proper backend layer. You have two good options depending on how much control you want:

First option: Data API Builder (DAB) This is the closest replacement for what SWA used to offer. DAB sits in front of your Azure SQL database and automatically exposes REST or GraphQL endpoints. You host it in Azure Container Apps or App Service, and then your Static Web App simply calls those endpoints. It’s lightweight, fast to set up, and fully supported going forward.

Second option: Your own API (Azure Functions or App Service) If you need more customization, build a small API that handles your SQL queries. Your Static Web App calls your API, and the API talks to Azure SQL using a managed identity or a regular connection string. This is what my team used when the old SWA database connection feature first started breaking.

Both routes are fully supported, and both avoid the retired SWA integration.
Alan Davis 0 Reputation points

2025-12-08T21:45:04.2066667+00:00

Thanks I need to try to resolve this ASAP. If you are able to reach out off line to offer me more guidance I would appreciate almost a step by step process to migrate my existing Static Web App to work again.
Adam Zachary 2,025 Reputation points

2025-12-08T22:09:57.8866667+00:00
I totally get the urgency, Alan. When this feature was retired it broke a few of our customer apps overnight, so I’ve been in the same situation. While I can’t reach out offline from here, I can definitely outline the steps you’d take to get your Static Web App working again. It’s not too bad once you know the path.

Here’s the high-level flow we followed during our migrations:

Decide which backend you want to use (DAB or your own API). If you just need CRUD-style access to SQL, Data API Builder is the quickest fix. If you have more logic or custom rules, then an Azure Function API is a better fit.

Stand up the backend. For DAB: deploy a DAB container to Azure Container Apps and point it at your SQL connection. For Functions: create an HTTP-triggered Function App and put your SQL calls in there.

Enable authentication. Most people use managed identity so you don’t have to keep a connection string in SWA.

Update your Static Web App to call the new backend. This usually means replacing calls to the old /data-api/... endpoints with your new API URL.

Verify everything locally first. The SWA CLI makes it easy to test the new API connection before pushing anything live.

Deploy and update your SWA config. Once the backend is working, redeploy your Static Web App so it knows where to send database requests.

If you tell me which way you want to go DAB or a Function App, I can give you a step-by-step checklist tailored to that option.
Alan Davis 0 Reputation points

2025-12-08T22:43:11.1066667+00:00

Wow thank you dab would be sufficient we just need it to allow a data call as a read request. No updates or anything like that

Share via

Static Web App Database Connection Issue

2 answers

Your answer