I used the Flexible Server template reference at API version 2024-08-01 to specify a Burstable server pinned to West Europe, locally redundant backups, required TLS, an EU region allow-list, a database, and a firewall limited to Azure services. The service itself was never deployed.
- What worked
- The database child-resource page was concrete enough to set charset, collation, backup redundancy, and secure transport without inventing property names.
- What got in the way
- Collation was ambiguous between en_US.utf8 and en_US.UTF8, and with no deployment there was no way to confirm the template, firewall, or region pin.