Azure Maps Routes and Time (BYOK)

Azure Maps Routes and Time (BYOK) — connector documentation

• MCP endpoint: https://byok-azure-maps-routes.connectorbay.com/mcp
• REST API: POST https://byok-azure-maps-routes.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-azure-maps-routes.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Azure Maps Routes and Time Azure Maps account subscription key (primary or secondary), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-azure-maps-routes.connectorbay.com/health · Tool schemas: https://byok-azure-maps-routes.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-azure-maps-routes · agent@connectorbay.com

What Azure Maps Routes and Time (BYOK) is for

Azure Maps Routes and Time (BYOK) lets an AI assistant read your own Azure Maps Routes and Time data through the Azure Maps Routes and Time API with a key you supply (Azure Maps account subscription key (primary or secondary)). Read-only: 7 tools (get_route, get_reachable_range, get_traffic_flow_segment, list_iana_time_zones, list_windows_time_zones, convert_windows_to_iana, get_iana_version). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to atlas.microsoft.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Azure Maps Routes and Time. Azure Maps Routes and Time and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "How long does it take to drive from 47.60,-122.33 to 47.64,-122.13?"
• "What area can I reach by car in 15 minutes from 47.60,-122.33?"
• "How congested is the road at 47.6097,-122.3331 right now?"
• "Which IANA time zone ids exist?"
• "Which Windows time zone ids exist and what are their IANA equivalents?"
• "What is the IANA id for the Windows time zone 'Pacific Standard Time'?"

What it does

• get_route: Calculate a route between an origin, optional waypoints and a destination and return the distance, travel time, traffic delay, departure and arrival time and the route sections (traffic, tolls, ferries). The line geometry is left out.
• get_reachable_range: Calculate the area reachable from a point within a time or distance budget and return its boundary polygon points.
• get_traffic_flow_segment: Current and free-flow speed and travel time of the road segment closest to a point, with a confidence value, to see how congested it is.
• list_iana_time_zones: List all IANA time zone ids (for example Europe/Paris), flagging aliases and what they alias.
• list_windows_time_zones: List all Windows time zone ids with their territory and the IANA ids they map to.
• convert_windows_to_iana: Convert a Windows time zone id to the matching IANA ids, optionally narrowed by territory.
• get_iana_version: Show the version of the IANA time zone database the service currently uses.

BYOK key

You bring your own Azure Maps Routes and Time Azure Maps account subscription key (primary or secondary) (https://learn.microsoft.com/en-us/azure/azure-maps/how-to-manage-account-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to atlas.microsoft.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://learn.microsoft.com/en-us/rest/api/maps/route?view=rest-maps-1.0 (the API this connector calls, with a BYOK key)

Live from the Azure Maps Routes and Time API (atlas.microsoft.com) with a BYOK key; documentation: https://learn.microsoft.com/en-us/rest/api/maps/route?view=rest-maps-1.0. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Azure Maps Routes and Time. Azure Maps Routes and Time and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Azure Maps Routes and Time account.

Built for: Worldwide. Languages: English.

Azure Maps Routes and Time (BYOK) — Privacy Policy

Effective 16 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Azure Maps Routes and Time (BYOK) is. Azure Maps Routes and Time (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Azure Maps Routes and Time data: Read route travel times and reachable ranges, live traffic flow on a road segment and the IANA and Windows time zone lists with your own Azure Maps subscription key. You bring your own Azure Maps Routes and Time Azure Maps account subscription key (primary or secondary); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Azure Maps Routes and Time call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to atlas.microsoft.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Azure Maps Routes and Time rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Azure Maps Routes and Time receives. The request we make on your behalf, including the key and the arguments, under Azure Maps Routes and Time's own terms and privacy policy (https://azure.microsoft.com/en-us/support/legal/). Azure Maps Routes and Time acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Azure Maps Routes and Time gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Azure Maps Routes and Time data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Azure Maps Routes and Time (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Azure Maps Routes and Time at any time to end all access.

Children. Azure Maps Routes and Time (BYOK) is a general-audience service operated by the adult using the assistant, under Azure Maps Routes and Time's own age rules.

Changes. We will post changes here with a new effective date.

Azure Maps Routes and Time (BYOK) — Terms of Service

Effective 16 October 2026. These terms govern use of the Azure Maps Routes and Time (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Azure Maps Routes and Time (BYOK) provides: Read route travel times and reachable ranges, live traffic flow on a road segment and the IANA and Windows time zone lists with your own Azure Maps subscription key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Azure Maps Routes and Time credentials and only access data you are allowed to access. Azure Maps Routes and Time's terms (https://azure.microsoft.com/en-us/support/legal/) apply to your use of Azure Maps Routes and Time; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Azure Maps Routes and Time. Azure Maps Routes and Time and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Azure Maps Routes and Time returns, lightly trimmed; it may be incomplete, delayed or changed by Azure Maps Routes and Time. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Azure Maps Routes and Time account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Azure Maps Routes and Time's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Azure Maps Routes and Time may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Azure Maps Routes and Time key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Azure Maps Routes and Time takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-azure-maps-routes

Azure Maps Routes and Time (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-azure-maps-routes.connectorbay.com/mcp
• REST API: https://byok-azure-maps-routes.connectorbay.com/openapi.json
• Live status: https://byok-azure-maps-routes.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Azure Maps Routes and Time (BYOK) never asks for them.