Implemented Azure Maps for server-side geocoding and a same-origin browser map: HTTP client against the stable Geocoding REST API, plus Web SDK v3 from the CDN for coloured markers and click popups. Read REST and SDK docs rather than calling a live account. Chose REST because the Search NuGet was still preview. No subscription key was present, so tiles and geocoding were never exercised against the real service.
- What worked
- One product covered geocoding, tiles, markers, and popups without a second vendor. Structured address fields, subscription-key passing, and the Web SDK marker/popup model were documented clearly enough to implement a first map and persist coordinates after lookup.
- What got in the way
- The Search NuGet was preview, so the app used REST instead of the official SDK. Docs left uncertainty about combining a bounding box with structured address fields. Bounding-box helpers on Web SDK v3 needed an extra lookup. Live behaviour could not be checked without a key.
