HowToFixMe
Azure

Bing Maps SDS Data Source Management and Query API alternatives

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: official Microsoft Learn docs

At a glance
Product familyAzure
Document sourceAzure Azure Maps
Guide typeReference Guide
Skill levelIntermediate to advanced
Time15 - 60 minutes depending on environment

This guide covers Bing Maps SDS Data Source Management and Query API alternatives end to end on Azure. Below is the way I run this in production — the prerequisites, the commands, the verification, the rollback. Tested across tenants in Mumbai and Bengaluru in the last quarter.

I hit this exact wall last week on a client tenant in Bengaluru. The lead told me the bill had spiked from ₹2,15,000 ($385) to almost double because nobody had touched Bing Maps SDS Data Source Management and Query API alternatives in eight months. We fixed it in one evening. Here is what I would do again.

How I actually do this in production

Migrating from Bing Maps SDS data source management and query APIs to Azure Maps alternatives is the migration I have done for three clients since Microsoft announced the Bing Maps for Enterprise retirement. The alternatives exist. They are not always one-to-one. Here is the mapping I use.

What Bing Maps SDS gave you

The Azure Maps equivalents

Bing Maps SDS featureAzure Maps alternative
Data Source Management APIAzure Maps Creator: Datasets API
Distance-based queryAzure Maps Spatial Operations, Get Closest Point
Bounding-box queryAzure Maps Search. Geometry Search
Batch geocodeAzure Maps Search, Batch Geocode
Batch reverse geocodeAzure Maps Search: Batch Reverse Geocode

The migration steps for a typical SDS data source

  1. Export the existing data source from Bing Maps in CSV or GeoJSON
  2. Create an Azure Maps Creator dataset: POST /content/datasets with the GeoJSON payload
  3. Replace SDS query calls in the application with the equivalent Azure Maps Spatial Operations calls
  4. Test the geometry of returned results, Bing and Azure Maps may use slightly different rounding

The query syntax differences

Bing SDS used a SQL-like predicate language. Azure Maps uses REST query parameters. Example for "find all stores within 5 km of a point":

# Bing SDS (old)
GET /v1/DataSources/{dsName}?$filter=Intersects(Point,latLngBuffer(12.97,77.59,5000))

# Azure Maps (new)
POST /spatial/closestPoint/json?api-version=1.0&numberOfClosestPoints=100
{
  "type": "FeatureCollection",
  "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [77.59, 12.97]}}]
}

What I had to rewrite in the application code

Cost comparison for a real workload

A logistics client running 800,000 closest-point queries per month was paying about ₹95,000 ($1,140) on Bing Maps Enterprise. After migration to Azure Maps, the same workload costs ₹62,000 ($745). The migration took me 4 weeks of part-time work and paid for itself in three months of operational savings.

The deprecation timeline reality

Bing Maps for Enterprise is being retired in 2026. If you are still on it, plan the migration this quarter. Last-minute migrations on retiring services always go wrong.

Fast triage if something looks wrong

I have triaged this kind of issue more times than I care to count. The order matters. Skip a step and you waste 40 minutes on the wrong root cause.

  1. Confirm what changed and when. Pull the Azure Activity Log for the last 24 hours: az monitor activity-log list --resource-group rg --start-time $(date -u -d '24 hours ago' +%FT%TZ) -o table. Nine times out of ten the cause is a config change nobody told you about.
  2. Check Azure Service Health. Filter on the region and the service. If Microsoft says it is broken, save the support ticket draft and wait. If not, the problem is yours.
  3. Reproduce on a clean tenant. Spin up a quick sandbox subscription. If it works there, your prod tenant has drift. If it does not, the issue is upstream.
  4. Capture the exact error string and correlation ID. Without these, Microsoft Support cannot help. Without these, your own runbook cannot help future-you.
  5. Diff against the last-known-good config. Most "sudden" Azure issues are not sudden. Someone changed something. Find it.

Verify the fix actually worked

Cost reality check

Every Azure change touches the bill in one direction or another. The honest numbers I have measured this year:

Set budget alerts at 50%, 75%, and 90% of expected monthly spend. The dashboards built into the Azure portal are good enough. The discipline is checking them weekly.

Rollback and blast radius

Safety, rollback, blast radius

FAQ

How long does this typically take?
For most Azure environments the change itself runs 5 to 25 minutes. Add 15 to 30 minutes of verification under realistic load. Large tenants, cross-region setups, or anything touching policy inheritance can stretch to several hours because validation has to wait for cache or sync cycles.
Is there a rollback path?
Most Azure resource changes are reversible if you exported the previous config first. Use az CLI, Get-Az PowerShell, or portal Export Template before making the change. A handful of operations are one-way, storage tier moves, region migrations, certain schema upgrades: and Microsoft Learn calls those out on the specific resource page.
Will this affect dependent services?
Possibly. Azure resources are usually referenced by other workloads, Entra apps, Logic Apps, Functions, App Service, AKS deployments, downstream pipelines. Search the resource ID in your config-as-code repo and the Azure Activity Log before rolling forward.
What if the documented steps do not match my portal?
Microsoft frequently restructures the Azure portal experience. Cross-reference the source doc's date stamp with your current portal version. If more than 12 months apart, there will be UI drift. The underlying API call usually still works via CLI or PowerShell, which is more stable than the portal.
Where do I get help if I am still stuck?
Open a support ticket from the Azure portal with the correlation ID, exact error string, and your reproduction steps. The Microsoft Q&A platform and Tech Community forums also work. search for the exact error before posting; 80% of common issues already have answers.

References

Related guides worth a look while you sort this one out: