Hi Scorey DuBose,
Thanks for raising this question.
At this time, Microsoft has not published a specific end‑of‑life or hard removal date for the Azure Maps Search API v1.0. The current guidance is that:
- v1.0 is deprecated, which means it may no longer receive new features and could be retired in the future.
- Deprecated APIs typically continue to function for a transition period to give customers time to migrate, but exact retirement dates are announced separately when they are finalized.
- Customers are strongly encouraged to move to the latest supported Azure Maps Search API versions to avoid future disruptions and to benefit from ongoing improvements, bug fixes, and security updates.
Next steps:
- Review your application usage and identify where Search API v1.0 is still being called.
- Plan migration to the latest Azure Maps Search APIs as documented in Microsoft Learn.
- Monitor the Azure Maps and Azure service deprecations documentation and official Microsoft Learn announcements for any future timeline updates.
Reference list
- Search for a location (including fuzzy search): https://docs.microsoft.com/azure/azure-maps/how-to-search-for-address
- Best practices for Search (geobiased & fuzzy parameters): https://docs.microsoft.com/azure/azure-maps/how-to-use-best-practices-for-search
- Search coverage by country/region: https://docs.microsoft.com/azure/azure-maps/geocoding-coverage
- Provide POI/address feedback: https://docs.microsoft.com/azure/azure-maps/how-to-use-feedback-tool
- Migrate from Bing Maps to Azure Maps: https://docs.microsoft.com/azure/azure-maps/migrate-from-bing-maps
- Migrate from Google Maps to Azure Maps: https://docs.microsoft.com/azure/azure-maps/migrate-from-google-maps
Hope this helps clarify the current status. Do let me know if you have any further queries.
Thankyou!