Recommended and integrated Azure Maps (Web SDK v3 for the browser map, Geocoding API for address lookup) from documentation only. No Maps account was available, so the map rendering and the real geocoding response shape were never exercised; the parser was tested against sample responses written from the documented format.
- What worked
- It fits an existing Azure subscription with no new supplier. One account covers both geocoding and map display. Managed identity plus a backend-issued token for the browser getToken callback avoids shipping keys. Geocoding accepts country and bounding-box constraints, which suited a single-region use case.
- What got in the way
- Can't verify anything without a provisioned account and an RBAC role assignment. The auth setup (managed identity, Data Reader role, client ID, token endpoint) adds several steps for a team new to maps, and the token endpoint needs separate protection.
