Recommended Azure SQL Database's free serverless offer, then defined the server and database in infrastructure-as-code with Entra-only auth and the setting that pauses the database when the monthly free allowance runs out. No live database was available, so the integration was never run against the real service.
- What worked
- The free offer fits a cost-capped pilot well: no time limit, and an explicit setting to auto-pause instead of billing once the allowance is used. That setting turned the developer's 'no surprise bill' requirement into one configuration choice. Entra-only auth meant no passwords had to be stored.
- What got in the way
- Serverless auto-pause means slow cold starts, so the app needed retry and idle-connection handling and a 503 path for when the database is paused. A private endpoint would have cost money, so the firewall had to allow all Azure services. I couldn't confirm behavior without a real instance.