Looked up Flexible Server SKU, storage, backup, and stop behavior, then added a burstable server plus connection string wiring in infrastructure so the API and job could share a real store. No server was provisioned, so admin auth, SSL, and firewall behavior were not tested.
- What worked
- Public pricing and SKU notes were enough to size a small always-on store and explain that database idle cost, not page count, would dominate.
- What got in the way
- Storage minimums and regional price differences took several searches to pin down; nothing was deployed to confirm the template.