Maps country codes Northern Ireland
I am using the Maps API to get and verify addresses. As of January 1st, Northern Ireland will have a new country code; I could not find anything about this in the documentation, but does someone know if the Azure Maps API will use that country code for addresses from Northern Ireland directly? Thanks, Jeroen
Announcing the General Availability of the Azure Maps Geocode Autocomplete API
It was just last September that we were Introducing the Azure Maps Geocode Autocomplete API but now we’re excited to announce the general availability (GA) of the Azure Maps Geocode Autocomplete API, a production‑ready REST service that delivers fast, intelligent, and structured location suggestions. After a successful public preview, we have integrated your feedback and this API is now fully supported for mission‑critical workloads, providing a modern, scalable successor to the Bing Maps Autosuggest REST API and empowering developers to deliver high‑quality, responsive location experiences. Why This API Matters Today’s applications increasingly rely on smart, real‑time location suggestions, whether for store locators, delivery routing, rideshare dispatch, address entry, or dynamic search UIs. The Azure Maps Geocode Autocomplete API brings: Instant, relevant, typed‑ahead suggestions Granular result type filtering for Place or Address categories or even subtypes of Place category Structured, developer‑friendly outputs Support for multilingual experiences and localized ranking Proximity‑aware and popularity‑aware results Whether you are modernizing an existing solution or building something new, this API gives you precision, flexibility, and performance at scale. From Preview to GA: What’s New ✔ Stable GA API version The service is now available on the 2026‑01‑01 GA version, offering a reliable, long‑term contract for production workloads. ✔ Improved suggestion ranking and language handling This version introduces refined ranking logic and improved language handling, enabling more accurate, geo‑aware, and language‑appropriate suggestions across global markets. ✔ Updated documentation and samples The GA release includes new and refreshed REST API documentation, updated samples, and improved how-to-guide to help developers build complete geocoding workflows and migrate from Bing Maps more easily. What It Can Do The Geocode Autocomplete API is purpose‑built to deliver accurate, structured suggestions as users type. Core capabilities include: Entity suggestions: Places (e.g., administrative divisions, populated places, landmarks, postal codes) and Address (e.g., roads, point addresses) entities Structured output: Consistent address components for easy downstream integration Relevance‑based ranking: Popularity, proximity, and bounding‑box awareness Multilingual support: Honor language preferences via Accept-Language Flexible filtering: Target specific countries or entity types These capabilities help you create intuitive, high‑quality user experiences across global applications. How to Use It Use the GA version of Geocode Autocomplete with the following endpoint: https://atlas.microsoft.com/search/geocode:autocomplete?api-version=2026-01-01&query={query} Common optional parameters include: coordinates – Bias suggestions near the provided location bbox – Biases suggestions to entities that fall within the specified bounding box of the visible map area top – Limit the number of returned suggestions resultTypeGroups / resultTypes – Filter for Places or Addresses or its subtypes countryRegion – Restrict to specific country/Region A typical workflow: Call Autocomplete as the user types Use the selected suggestion with Azure Maps Geocoding service to retrieve coordinates and complete the interaction (e.g., map display, routing, address validation) Example: Autocomplete for Place Entity Query GET https://atlas.microsoft.com/search/geocode:autocomplete?api-version=2026-01-01 &subscription-key={YourAzureMapsKey} &coordinates={coordinates} &query=new yo &top=3 This request returns structured top 3 suggestions for the partial input “new yo,” helping users quickly find places like New York city or New York state based on user location. { "type": "FeatureCollection", "features": [ { "type": "Feature", "properties": { "typeGroup": "Place", "type": "PopulatedPlace", "geometry": null, "address": { "locality": "New York", "adminDistricts": [ { "name": "New York", "shortName": "N.Y." } ], "countryRegions": { "ISO": "US", "name": "United States" }, "formattedAddress": "New York, N.Y." } } }, { "type": "Feature", "properties": { "typeGroup": "Place", "type": "AdminDivision1", "geometry": null, "address": { "locality": "", "adminDistricts": [ { "name": "New York", "shortName": "N.Y." } ], "countryRegions": { "ISO": "US", "name": "United States" }, "formattedAddress": "New York" } } }, { "type": "Feature", "properties": { "typeGroup": "Place", "type": "AdminDivision2", "geometry": null, "address": { "locality": "", "adminDistricts": [ { "name": "New York", "shortName": "N.Y." }, { "name": "New York County" } ], "countryRegions": { "ISO": "US", "name": "United States" }, "formattedAddress": "New York County" } } } ] } Example: Autocomplete for an Address Entity Query GET https://atlas.microsoft.com/search/geocode:autocomplete?api-version=2026-01-01 &subscription-key={YourAzureMapsKey} &bbox={bbox} &query=One Micro &top=3 &countryRegion=US This request returns structured address suggestion for NE One Microsoft Way, categorized as an Address entity. { "type": "FeatureCollection", "features": [ { "type": "Feature", "properties": { "typeGroup": "Address", "type": "RoadBlock", "geometry": null, "address": { "locality": "Redmond", "adminDistricts": [ { "name": "Washington", "shortName": "WA" }, { "name": "King County" } ], "countryRegions": { "ISO": "US", "name": "United States" }, "postalCode": "98052", "streetName": "NE One Microsoft Way", "addressLine": "", "formattedAddress": "NE One Microsoft Way, Redmond, WA 98052, United States" } } } ] } Example: Integrate with Web Application Below sample shows user enter query and autocomplete service provide a series of suggestions based on user query and user location. Ready to Bring Autocomplete to Production? The Azure Maps Geocode Autocomplete API is now fully production‑ready, giving you the stability, performance, and flexibility needed to power fast, intuitive location‑driven experiences. Whether you're migrating from Bing Maps Autosuggest or enhancing your existing address or search workflows, the GA release makes it easier to deliver high‑quality suggestions at scale. If you're ready to upgrade your location experiences, now’s the perfect time to start. Explore the updated Azure Maps Autocomplete documentation, try the new endpoint, and let us know how it works for you. We’d love to hear your feedback. Let’s keep building great location intelligence experiences together. Resources to Get Started Geocode Autocomplete REST API Documentation How-to-Guide for Azure Maps Search Service Geocode Autocomplete Samples Migrate from Bing Maps to Azure Maps How to Use Azure Maps APIsGuest Blog: Modernizing your WPF App maps functionality with Azure Maps with OnTerra Systems
Although Windows Presentation Foundation (WPF) was initially released by Microsoft in 2006 with .NET Framework 3.0, there are still a huge number of mission critical WPF applications still in use today within a wide range of industries such as logistics, manufacturing, healthcare and banking. For those unfamiliar with WPF – it’s a UI framework for building Windows desktop applications. It uses XAML for UI design, C# or VB.NET for logic, MVVM (Model-View-ViewModel) for the primary design pattern, and it offers vector-based rendering, data binding, animation, styles/templates, and custom controls — all natively supported by Windows. Migrating your WPF application to use more contemporary Windows-centric approaches such as WinUI, React Native for Desktop, .NET MAUI and Blazor, or rewriting your application to be fully browser-based, can be very time-consuming and may be unnecessary in certain situations. With the deprecation of Bing Maps for Enterprise and the Bing Maps WPF Control, organizations that need maps and geospatial functionality in their WPF applications should upgrade to Microsoft’s modern maps and geospatial platform, Azure Maps. Specifically, one approach to migrating from Bing Maps to Azure Maps and continuing with your WPF-based application is to use the OnTerra Systems WPF Map Control, which is built on the Azure Maps Web SDK and includes virtually all of the same functionality as the Bing Maps WPF Control, such as road and aerial/satellite map styles, and pushpin, polygon and polyline overlay support. The OnTerra Systems WPF Map Control is a solution that translates Bing Map WPF Control methods to use the equivalent Azure Maps functionality and renders the map using .NET WebView2. Migrating from the Bing Maps WPF Control to the OnTerra Systems WPF Map Control can be done within a few steps and avoids the need to rewrite your WPF application’s maps functionality. A map with a pushpin in a WPF application using the Azure Maps-based OnTerra Systems WPF Map Control Let’s take a closer look at how Azure Maps is implemented in the OnTerra Systems WPF Map Control. This WPF-based maps solution uses Azure Maps via a wrapper SDK, integrating .NET WebView2 for modern map rendering, and was developed using AI-assisted development tools. Middle-layer wrapper using Azure Maps A middle-layer wrapper translates all Bing Maps WPF Control properties, tags, and method calls into corresponding Azure Maps Web SDK equivalents. The wrapper handles all conversions internally, mitigating the need for developers to rewrite or refactor any maps related logic. .NET WebView2 integration The WPF control utilizes the WebView2 browser component to render the Azure Maps Web SDK directly within the WPF application, which combines the strengths of both web and native platforms. This approach allows the application to leverage modern browser capabilities for map rendering and interactivity, while staying within a familiar WPF environment. Use of the Azure Maps Web SDK The Azure Maps Web SDK provides faster performance, smoother rendering, and an improved user experience, particularly for interactive maps and real-time updates. Building the WPF Map Control solution on the Azure Maps Web SDK provides the opportunity to extend the WPF application to use additional Azure Maps Web SDK features and map styles in the future. SDK package for simplified integration The solution is packaged as a reusable SDK, rather than exposing APIs directly as this approach is easier for integration and provides developers with a ready-to-use experience. Replacing the Bing Maps WPF Control NuGet package with the OnTerra Map Control NuGet package is one of the steps to migrating from Bing Maps to Azure Maps in your WPF application and continues the already-familiar NuGet package-based approach. Using the OnTerra WPF Map Control approach provides a way for your existing Bing Maps WPF Control code to continue to function without any significant changes, enabling a straightforward migration from Bing Maps to Azure Maps. While there are different possible approaches to bringing the power of Azure Maps to your new or existing Windows applications as mentioned above, the OnTerra Systems WPF Map Control provides: No code refactoring required: Existing Bing Maps WPF Control applications can transition to Azure Maps with minimal modifications in your existing application code. Ease of integration: The SDK package ensures minimal setup and a plug-and-play experience for developers. Faster development and maintenance: The internal middle-layer wrapper handles all complexities, reducing developer effort. To get access to the OnTerra Systems WPF Map Control or if you’d like to discuss how it can help you seamlessly transition to Azure Maps, please contact OnTerra Systems at https://www.onterrasystems.com/contact.Introducing the Azure Maps Geocode Autocomplete API
We’re thrilled to unveil the public preview of Azure Maps Geocode Autocomplete API, a powerful REST service designed to modernize and elevate autocomplete capabilities across Microsoft’s mapping platforms. If you’ve ever started typing an address into a search bar and immediately seen a list of relevant suggestions—whether it’s for a landmark, or your own home—you’ve already experienced the convenience of autocomplete. What’s less obvious is just how complex it is to deliver those suggestions quickly, accurately, and in a format that modern applications can use. That’s exactly the challenge this new API is designed to solve. Why Autocomplete Matters More Than Ever The Azure Maps Geocode Autocomplete API is the natural successor to the Bing Maps Autosuggest REST API, designed to meet the growing demand for intelligent, real-time location suggestions across a wide range of applications. It’s an ideal solution for developers who need reliable and scalable autocomplete functionality—whether for small business websites or large-scale enterprise systems. Key use cases include: Store locators: When a customer starts typing “New Yo…” into store locator, autocomplete instantly suggests “New York, N.Y.” With just a click, the map centers on the right location—making it fast and effortless to find the nearest branch. Rideshare or dispatching platforms: A rideshare driver needs to pick up a passenger at “One Microsoft Way.” Instead of typing out the full address, the driver starts entering “One Micro…” and the app instantly offers the correct road segment in Redmond, Washington. Delivery services: A delivery app can limit suggestions to postal codes within a specific region, ensuring the addresses customers choose are deliverable and reducing the risk of failed shipments Any Web UIs requiring location input: From real estate search to form autofill, autocomplete enhances the user experience wherever accurate location entry is needed. What the API Can Do The Geocode Autocomplete API is designed to deliver fast, relevant, and structured suggestions as users type. Key capabilities include: Entity Suggestions: Supports both Place (e.g., administrative districts, populated places, landmarks, postal codes) and Address (e.g., roads, point addresses) entities. Ranking: Results can be ranked based on entity popularity, user location (coordinates), and bounding box (bbox). Structured Output: Returns suggestions with structured address formats, making integration seamless. Multilingual Support: Set up query language preferences via the Accept-Language parameter. Flexible Filtering: You can filter suggestions by specifying a country or region using countryRegion, or by targeting a specific entity subtype using resultType. This allows you to extract entities with precise categorization—for example, you can filter results to return only postal codes to match the needs of a location-based selection input in your web application. How It Works The Geocode Autocomplete API is accessed via the following endpoint: https://atlas.microsoft.com/geocode:autocomplete?api-version=2025-06-01-preview This endpoint provides autocomplete-style suggestions for addresses and places. With just a few parameters, like your Azure Maps subscription key, a query string, and optionally user coordinates or a bounding box, you can start returning structured suggestions instantly. Developers can further issue geocode service with the selected/ideal entity as query to locate the entity on map, which is a common scenario for producing interactive mapping experiences. Let’s look at below examples: Example 1: Place Entity Autocomplete GET https://atlas.microsoft.com/geocode:autocomplete?api-version=2025-06-01-preview &subscription-key={YourAzureMapsKey} &coordinates={coordinates} &query=new yo &top=3 A user starts typing “new yo.” The API quickly returns results like “New York City” and “New York State,” each complete with structured metadata you can plug directly into your app. { "type": "FeatureCollection", "features": [ { "type": "Feature", "properties": { "typeGroup": "Place", "type": "PopulatedPlace", "geometry": null, "address": { "locality": "New York", "adminDistricts": [ { "name": "New York", "shortName": "N.Y." } ], "countryRegions": { "ISO": "US", "name": "United States" }, "formattedAddress": "New York, N.Y." } } }, { "type": "Feature", "properties": { "typeGroup": "Place", "type": "AdminDivision1", "geometry": null, "address": { "locality": "", "adminDistricts": [ { "name": "New York", "shortName": "N.Y." } ], "countryRegions": { "ISO": "US", "name": "United States" }, "formattedAddress": "New York" } } }, { "type": "Feature", "properties": { "typeGroup": "Place", "type": "AdminDivision2", "geometry": null, "address": { "locality": "", "adminDistricts": [ { "name": "New York", "shortName": "N.Y." }, { "name": "New York County" } ], "countryRegions": { "ISO": "US", "name": "United States" }, "formattedAddress": "New York County" } } } ] } Example 2: Address Entity Autocomplete GET https://atlas.microsoft.com/geocode:autocomplete?api-version=2025-06-01-preview &subscription-key={YourAzureMapsKey} &bbox={bbox} &query=One Micro &top=3 &countryRegion=US A query for “One Micro” scoped to the U.S. yields “NE One Microsoft Way, Redmond, WA 98052, United States.” That’s a complete, structured address ready to be mapped, dispatched, or stored. { "type": "FeatureCollection", "features": [ { "type": "Feature", "properties": { "typeGroup": "Address", "type": "RoadBlock", "geometry": null, "address": { "locality": "Redmond", "adminDistricts": [ { "name": "Washington", "shortName": "WA" }, { "name": "King County" } ], "countryRegions": { "ISO": "US", "name": "United States" }, "postalCode": "98052", "streetName": "NE One Microsoft Way", "addressLine": "", "formattedAddress": "NE One Microsoft Way, Redmond, WA 98052, United States" } } } ] } Example 3: Integration with Web Application Below sample shows user enter query and autocomplete service provide a series of suggestions based on user query and location. Pricing and Billing The Geocode Autocomplete API uses the same metering model as the Azure Maps Search service. For billing purposes, every 10 Geocode Autocomplete API requests are counted as one billable transaction. This approach keeps usage and costs consistent with what developers are already familiar with in Azure Maps. Ready to Build Smarter Location Experiences? Whether you're powering a store locator, enhancing address entry, or building a dynamic dispatch system, the new Geocode Autocomplete API gives you the precision, flexibility, and performance needed to deliver seamless location intelligence. With real-world use cases already proving its value, now is the perfect time to integrate this service into your applications and unlock richer, more interactive mapping experiences. Let’s build what’s next—faster, smarter, and more intuitive. Resources to Get Started Geocode Autocomplete REST API Documentation Geocode Autocomplete Samples Migrate from Bing Maps to Azure Maps How to use Azure Maps APIsAzure Maps: Understanding View vs. Routing Coordinates
When you work with Azure Maps long enough, you will eventually run into a subtle but important detail: the platform returns two different types of coordinates for the same address. And while they may look interchangeable, they behave very differently once you start routing, calculating travel times, or dropping pins on a map. Let’s break down what each represents and how to use them correctly when building location‑intelligent applications. Why Azure Maps Has More Than One Coordinate for a Place Geocoders, including Azure Maps, are designed to satisfy two competing needs: Show the place in the visually “accurate” spot on a map. Get people or goods to a real, accessible point on the road network. The coordinate that satisfies the first need is rarely the same answer for the second, in fact it can be wildly off. If you have ever visited a National Park or other large location where the entrance is far from where you would display the center of the park, you will note that the difference between these coordinates can be many miles apart and often you can't drive to the exact center, so we would say the View coordinate is not Routable. So Azure Maps provides them separately; one to power the visual map experience, the other to power the routing engine. The View Coordinate: Your Visual Anchor Point Think of the Azure Maps view coordinate as “the place where the map pin should sit.” It may come from an address parcel, a building footprint centroid, or a point-of-interest geometry. Azure Maps will provide whatever option that produces the most natural visual representation of the feature on the map. This is the important part for our topic: a view coordinate is not guaranteed to land on a road or even near one. It might be in the center of a large warehouse, deep inside a shopping mall footprint, or somewhere else that makes sense visually but is effectively unreachable from the road network. View coordinates are great for anything that involves visual context such as placing a point on the map, centering the map on a search result, running spatial clustering on data values, or doing proximity lookups. They’re simply not intended for navigation. The Routing Coordinate: Your Navigable Access Point Routing coordinates serve a very different purpose. Azure Maps generates them to represent an access point. The point where a vehicle, pedestrian, or cyclist can legally and realistically approach or leave the location from the road network. This usually means: The point is snapped to the closest routable road segment. It’s positioned where a driver or pedestrian can actually arrive (e.g., the driveway, street entrance, or legal access point). It includes the orientation and topology needed for the routing engine to produce correct ETAs, distance calculations, and directions. When you're calling Azure Maps Routing APIs—calculateRoute, routeRange, distance matrices, isochrones, multi‑itinerary optimization—you should always feed the routing coordinate into the engine. Feeding a view coordinate instead may cause the service to snap to the wrong part of the network, or worse, find no viable route at all. How Azure Maps Exposes These Coordinates Azure Maps surfaces routing coordinates and view coordinates through structured fields in its search and geocoding responses. The naming varies by API, but you will often see: "usageTypes": [ "Display" ] denotes position or displayPosition → View coordinate "usageTypes": [ "Route" ] denotes routePosition, accessPoint, or entryPoints → Routing coordinate Azure Maps provides both and should your scenario involve travel movement (even indirectly), the routing coordinate is the authoritative choice. What Goes Wrong When You Swap Them If you use a view coordinate for routing, you can be asking for routes that terminate inside a building footprint, on the wrong side of the street, or at an incorrect driveway. You might also see unexpected route endpoints because the routing engine is forced to snap the point to whichever road segment it thinks is closest, which might not be the correct one. On the other hand, if you use a routing coordinate for display, your pins may look "off" because the access point for an address could be far from the building’s center. This is why the distinction matters: one is about realism, the other about navigability. The Upside: Using Them Correctly in Your Applications When building an end‑to‑end Azure Maps experience, a good mental model is: Map UI? Use the view coordinate. Anything involving routing logic? Use the routing coordinate. That includes distance calculations, service‑area modeling, route planning, delivery optimization, pickup/drop-off flows, fleet operations, and anything else where “how the user gets there” matters just as much as “where it is.” With this separation of geocode results, you can trust Azure Maps to keep your visual experience clean while ensuring the routing engine has the precision it needs to get users where they actually need to go. To find out more about Azure Maps Geocoding and our new Azure Maps AutoComplete experience, check out Search for a location using Azure Maps Search services | Microsoft LearnIntroducing the Data-Bound Reference Layer in Azure Maps Visual for Power BI
The Data-Bound Reference Layer in Azure Maps for Power BI elevates map-based reporting by allowing users to visually explore, understand, and act on their data. This feature enables new possibilities for data analysts, business leaders, and decision-makers reliant on spatial insights.Transforming Dynamics 365 Customer Data with Azure Maps | Inogic Guest Post
This guest post by Inogic explores how their integration of Azure Maps with Dynamics 365 empowers organizations to convert raw customer data into actionable location intelligence. The blog highlights: Use Case: Businesses using Dynamics 365 can visualize customer data geographically, enabling smarter decision-making and improved operational efficiency. Technology Stack: Azure Maps is used to enrich CRM data with spatial context, helping users identify trends, optimize routes, and enhance customer engagement. Benefits: Enhanced data visualization Improved field service planning Better territory management Integration Details: Inogic’s solution seamlessly embeds mapping capabilities into Dynamics 365 dashboards, making location insights accessible without leaving the CRM environment.Discover the Power of HD Isochrones in Azure Maps Route Range API
In the ever-evolving world of location-based services (LBS), precision and accuracy are key. Whether you're planning business expansions, optimizing logistics, or enhancing urban mobility, understanding travel times and accessibility is essential. Enter isochrones—a revolutionary way to visualize areas reachable within a given travel time. Azure Maps, Microsoft’s comprehensive geospatial platform, has taken isochrone generation to the next level with its updated Route Range API. Featuring HD isochrone support and specialized truck routing capabilities, this powerful API is set to transform how businesses and planners make data-driven decisions. Why Isochrones Matter Isochrones provide a dynamic alternative to traditional fixed-distance buffers. Instead of simply drawing a circle around a location, isochrones map out the actual area that can be reached within a certain time frame. This approach takes into account real-world factors like road networks, traffic conditions, and different modes of transportation. For example, a retail chain can use isochrones to determine how far customers can travel to a store within 15 minutes, while a logistics company might analyze delivery times for different service areas. This real-time, time-based insight enables more informed decisions across industries. Unlocking Precision with HD Isochrones The new HD isochrone functionality in the Azure Maps Route Range API offers significantly higher resolution and detail. This means you can generate highly precise maps of reachable areas for time intervals ranging from minutes to several hours (up to 10 million seconds!). Picture a city planner evaluating the impact of a new transit line: with HD isochrones, they can visualize how accessibility to key destinations improves over various time periods. Or imagine a franchise business assessing the best location for its next store—now, they can precisely map out the potential trade area based on realistic travel times. Specialized Capabilities for Truck Routing One of the standout features of the updated API is its advanced truck routing support. Unlike standard car-based routing, truck routing considers a host of additional factors: Vehicle dimensions and weight restrictions: Ensures routes comply with height, width, and weight limits. Hazardous materials restrictions: Avoids roads where certain materials are prohibited. Truck-specific road features: Avoiding tunnels or bridges. These capabilities are invaluable for logistics companies managing fleets. By generating truck-specific isochrones, businesses can optimize delivery routes, reduce fuel costs, and improve on-time performance—all while ensuring compliance with local regulations. For example, a distribution center might use truck isochrones to determine how far deliveries can reach within a specified time window, considering truck-specific constraints. This insight can help optimize delivery zones, improve service levels, and even reduce the environmental impact of operations. Transforming Business Decisions with Isochrones The power of HD isochrones extends beyond logistics and retail. Urban planners can leverage them to design more efficient public transportation networks, ensuring that key services like healthcare and education are accessible within reasonable travel times. City governments can simulate the effects of road closures or new infrastructure projects, minimizing disruptions and improving traffic flow. Franchise owners, on the other hand, can use isochrones to better understand customer reach and minimize cannibalization—the overlap between existing and new store locations. By analyzing travel times and customer access, businesses can strategically expand without diluting their market share. Bringing It All Together Imagine a logistics manager planning delivery routes from a central warehouse. Using the Azure Maps Route Range API, they can generate a truck-specific isochrone for a 60-minute delivery window. Here's how it works: Sample Request POST https://atlas.microsoft.com/route/range?api-version=2024-07-01-preview { "type": "Feature", "geometry": { "type": "Point", "coordinates": [ // Warehouse location 5.86605, 50.9745 ] }, "properties": { "timeBudgetInSec": 3600, // 1 hour in seconds "travelMode": "truck", // Truck mode for routing "vehicleSpec": { "height": 4.2, // Height of the vehicle in meters (13.5 feet) "length": 22 , // Length of the vehicle in meters (72 feet) "width": 2.6 // Width of the vehicle in meters (8.5 feet) } } } What Happens Next? The API returns a detailed geoJSON file outlining the area accessible within an hour. This data can be visualized on a map, providing a clear picture of delivery zones. The manager can adjust operations to maximize coverage while ensuring that all regulatory and safety requirements are met. Start Exploring Today With its updated Route Range API, Azure Maps is setting a new standard for geospatial analysis. From precision trade areas to optimized logistics, the possibilities are vast. Whether you're in retail, logistics, urban planning, or beyond, HD isochrones and truck routing can help you make smarter, data-driven decisions. Curious to see how these features can benefit your organization? Explore the official documentation to get started today!Mastering Time with Microsoft Azure Maps Timezone API
If you are a developer building a solution that needs to be aware of availability Globally, that’s where the Microsoft Azure Maps Timezone API comes to the rescue! The Azure Maps Timezone API allows developers to retrieve accurate time zone information for any location on Earth. It supports: Geospatial queries (latitude/longitude) - What is the timezone at the given co-ordinate? IANA and Windows Timezone IDs - Get the standard names, settings and codes for timezones. Sunrise and sunset times - Will I be there when I can see in daylight or will it be nighttime? Historical and future time zone transitions - Daylight savings can add a wrench into planning so be aware of time changes! This API is part of the broader Azure Maps platform and integrates seamlessly with other Azure services, has the benefits of being co-located with other Azure services and includes multiple methods to access. Real-World Use Cases Telematics and Logistics In the automotive and logistics sectors, accurate time zone data is vital for post-processing telemetry. For example, OEMs using TomTom data can leverage Azure Maps on the backend to normalize timestamps across regions—ensuring consistency in fleet analytics, delivery tracking, and driver behavior analysis. IoT and Smart Buildings Sunrise and sunset data from the API can be used to automate lighting, HVAC, and security systems. This is especially useful for energy optimization in smart buildings, where operations need to align with natural light cycles. Global Scheduling and Compliance Applications that span multiple time zones—like global HR platforms, travel apps, or compliance systems—rely on accurate time zone conversion. Azure Maps ensures that meetings, deadlines, and alerts are synchronized across regions. Retail and Operations Retailers with stores in multiple time zones can use the API to coordinate store openings, delivery windows, and promotional campaigns. This ensures a consistent customer experience regardless of location. Azure Maps Timezone API Developer Experience Azure Maps provides a Web SDK that can be used for JavaScript, .NET, Python and more. Developers can also use the REST API directly from their favorite development environment. This API offers several endpoints: Get Timezone By Coordinates Get Timezone By ID Get Timezone Enum IANA/Windows Get Timezone IANA Version Get Timezone Windows To IANA Here’s a quick example using JavaScript: fetch(`https://atlas.microsoft.com/timezone/byCoordinates/json?api-version=1.0&query=47.6062,-122.3321&subscription-key=YOUR_KEY`) .then(response => response.json()) .then(data => console.log(data)); You can try this live at Get Users Timezone with Prompt - Azure Maps Web SDK Samples and check out this sample and more at Samples.AzureMaps.com. All Azure Maps samples have full source available in GitHub. In Summary The Azure Maps Timezone API is a critical tool for any application that needs to be time-aware. It sits within a comprehensive suite of mapping APIs that is Azure compliant and available to be added to any Azure project. From logistics to IoT to global operations, Azure Maps provides the precision and flexibility developers need to build robust, scalable geospatial solutions.
