Used the Web SDK design and Geocoding API contract to implement technician-coloured markers, popups, Sheffield-biased address lookup, and confidence handling. The integration built successfully, but no live Azure Maps account or API call was exercised.
- What worked
- The map control and geocoding capabilities covered both halves of the feature under one product, and the official material made the current Web SDK generation, pricing, authentication choices, and geocoding response handling understandable.
- What got in the way
- End-to-end reliability remained unassessed because credentials and deployed Azure resources were unavailable; managed identity and real geocoding still required deployment configuration.
