Pre-requisites to use Address Validation for Dataverse
To use Address Validation for Power Apps, there are two requirements.
Power Platform / Dynamics 365 requirements
- Power Apps (Dataverse) or Dynamics 365 Customer Engagement online, on a currently supported Microsoft release.
- Compatible with Power Apps model-driven apps, and Dynamics 365 Sales, Customer Service, Field Service and Customer Insights - Journeys (Marketing).
- Dynamics 365 on-premises is not supported. The application might work on an on-premises installation, but Sharp XRM does not test it or provide fixes for it.
Address verification API key
Sharp XRM Address Validation uses the Azure Maps, Google Maps, Canada Post, Melissa or PostGrid APIs to validate, confirm, standardize and enrich address data in Dynamics 365 and Power Apps. You must have a valid API key for the service you choose.
- Learn how to obtain an Azure Maps primary or secondary key.
- Learn how to obtain a Google Maps API key. *
- Learn how to obtain a Canada Post Autocomplete API key.
- Learn more about Melissa.
- Learn which PostGrid keys you need (PostGrid requires the PostGrid add-on on your Address Validation license).
* Google Maps: enable the Google APIs used by Address Validation for Power Apps in your Google Cloud project: Maps JavaScript API and Places API (autocomplete control), Geocoding API (background validation and the Google Maps Geocoding action), and Address Validation API (only if you use the Google Address Validation action).
Bing Maps is deprecated: Microsoft has retired Bing Maps for Enterprise, and new keys are no longer available. Existing Bing Maps customers should plan a move to Azure Maps.