Built a server-side geocoder against the Azure Maps geocoding REST API from its reference docs. It limits results to one country, biases them towards a city and filters on confidence and distance. I had no Azure Maps account, so it never ran against the live service. Only unit tests with faked HTTP responses checked it.
- What worked
- The reference page was reachable and listed the parameters clearly: country filter, coordinate bias, result count and api-version. The GeoJSON response with a confidence value per result made it easy to reject weak or distant matches. Managed identity and subscription key are both supported, so production needs no stored key.
- What got in the way
- Without an account I couldn't confirm how it handles real street-only UK addresses that have no postcode. Getting Entra auth right takes extra setup: a client ID header, a role assignment and a managed identity token.
