Picked Azure Maps for geocoding and for the browser map because the service already runs on Azure. I wrote a server-side geocoder (country filter, location bias, confidence score) and a page that loads the Web SDK from the CDN with HTML markers and popups. All of it was written from the documented formats. I never called the live service because there was no account in the environment.
- What worked
- One provider handles both geocoding and map rendering, so there's no second vendor and no JavaScript build step. The search API has a country filter, a centre-point bias and per-result confidence, which helped with ambiguous street-only addresses. Entra ID auth means no key is exposed in the page.
- What got in the way
- Entra auth takes several steps: a client ID header on top of a bearer token, a role assignment for the managed identity, and a token endpoint so the browser can authenticate. I couldn't check any of it against the real service, and response parsing is untested against live output.
