Azure Maps Geospatial Capability

Azure Maps gives agents geospatial reasoning for storm response and local marketing: the ZIP codes and counties a storm or service-area polygon covers, radius circles that approximate it for proximity ad targeting, a rough household count, address geocoding, and how far an address sits from a storm. Every Azure Maps tool is read-only.

Unlike the other integrations in this section, Azure Maps is a platform capability. It runs on Outermind's own Azure Maps account, so there is nothing to sign up for, no key to paste and no connection page.

Before you start

• Nothing at a vendor. You do not need an Azure subscription, an Azure Maps account or a key. Outermind reaches Azure Maps through its own managed identity.
• A tenant admin in Outermind who can edit agents, to grant the tools.

Check that it is available

1. Open the Capabilities hub and go to Connections.
2. Find the Azure Maps card. It shows a Platform capability badge instead of a Connect button.
3. If the card says "The platform Azure Maps credential is not configured in this environment", the capability is not switched on in your region yet. The tools can still be granted, but every action that needs an Azure Maps lookup tells the agent that geospatial lookups are not configured; only the purely local calculations (to_radius_targets and estimate_households) work. Contact Outermind support if you need it.

There is no /capabilities/integrations page for Azure Maps and no setup wizard, because there is no per-tenant connection to manage.

Grant the tools

Grant the Azure Maps tools to each agent that needs them from the agent's Tools tab (Workforce > Agents > Agents & SMEs). No plan feature has to be turned on first; the grant to the agent is what gives it access.

What your agents can do

Every action below is class read and tier read, so it runs without asking a person at every autonomy level.

Tool	Action	What it does
geo_polygons	to_zipcodes	The ZIP or postal codes inside a polygon, found by reverse geocoding a grid of sample points; a small code near the edge can be missed
	to_counties	The counties a polygon overlaps, each with its state; a FIPS code is never invented
	to_radius_targets	A few center-and-radius circles that approximate the polygon, in kilometres and miles, for proximity ad targeting. Calculated locally, with no Azure Maps lookup
	estimate_households	A best-effort household count, from the polygon's area and a density heuristic. Low confidence, and never census or parcel data
geo_addresses	geocode	Turns a street address into latitude and longitude, with the formatted address, postal code, county, state and match confidence
	distance_to_storm	How far a point or address is from a storm polygon or storm center, in kilometres and miles, and whether it sits inside the polygon

Safety and data handling

• Read-only. The tools look things up and calculate; they change nothing anywhere.
• What leaves Outermind. Addresses and sample points from a polygon are sent to Microsoft's Azure Maps service (atlas.microsoft.com) under Outermind's account. Results are not cached; every call asks Azure Maps again.
• Estimates are estimates. ZIP code and county coverage comes from sampling, and household counts from a heuristic. Treat them as a starting point for targeting, not as authoritative figures.