CloudServices - Released January 27-28, 2025

Learn more about the Bing-to-Azure migration and other improvements to CloudServices.

Bing Maps Replacement

If you integrate with Bing Maps to use features like geocoding and distance/drive time, you may have heard Microsoft is retiring the service on June 30, 2028 for enterprise licenses or June 30, 2025 for free/basic licenses. To continue using certain CloudServices features, you'll want to migrate to Azure Maps.
Note: Azure Maps is a transactions-based usage offering. Review their Pricing page, and check out their Nonprofit offers to see if your organization is eligible.
Here's what you need to do:
- If you're a current Bing customer, you can still use CloudServices without interruption. We added configuration settings to handle this, and you can switch to Azure when you're ready by updating your Maps API Key.
- If you want to start using CloudServices that require an integration, you must set up an Azure account. You'll then need to set your provider in MinistryPlatform after this release. See Get a Maps API Key for steps on how to do this.

Addresses are now submitted for geocoding only when they meet certain additional criteria, both in a single record (via the webhook) and in the overnight routine. See the details on Geocode Utility.

Fixed an issue where contacts were being reactivated after they had been intentionally inactivated using the Inactivate tool. To avoid this, Contact Status Management now ensures a Participant End Date is more than 24 hours before the qualifying activity.