Back to Tech landscape

Azure Maps

Cloud & DevOps

Geospatial APIs for maps, routing, and search

Official documentation (opens in a new tab)

Overview

Azure Maps delivers geospatial REST APIs and SDKs for maps, geocoding, routing, traffic, and weather—embedded in logistics, field-service, and customer-facing location features.

ConnectSoft .NET 10 services call Maps from ASP.NET Core backends on Microsoft Azure, keeping API keys in Azure Key Vault and caching policies aligned with your SLA. Factory templates remain API-first; Maps is added when the product domain needs authoritative location data—not as a replacement for your core platform stack.

For client programs we define data retention, privacy, and fallback behavior when third-party map tiles are unavailable—especially in regulated or offline-adjacent scenarios.

When location is part of your Azure roadmap, we wire Maps with the same Entra-backed security and observability as the rest of your microservices.

Why we use it:

  • REST and SDK access from ASP.NET Core services
  • Keys and quotas stored in Azure Key Vault per environment
  • Privacy and data handling reviewed for end-user locations
  • Complements—not replaces—Factory SQL and messaging baselines
  • Integrated telemetry via Application Insights
  • Suitable for fleet, asset, and customer-facing map scenarios
  • Clear ownership between map UX and core transactional APIs

Ready to work with us?

Let's discuss how our team can help achieve your digital goals