I used the free-offer documentation to select a serverless database that pauses when the monthly allowance is exhausted, then encoded that offer, auto-pause, and a small connection pool in the app and its deployment template. The published limits were specific enough to plan around, but the docs understated how many free databases a subscription can hold and the capacity setting did not match the schema. No live database session was opened from this environment.
- What worked
- The free offer is a standing monthly allowance with an explicit pause-instead-of-bill behavior, which matched a hard spend cap. Compute, data, and backup limits were concrete enough to size one shared database and to set an alert threshold before pause.
- What got in the way
- Guidance still described a one-database limit while the newer offer allows more, and the property that selects pause-on-exhaustion had to be cross-checked. A fractional minimum capacity did not fit the integer schema. Pause, resume, and billing behavior were never observed against the service.