Overview
This release rolls up everything delivered for Address Validation for Dynamics 365 between March and July 2026. The headline addition is the new Bulk Address Validation (Preview) experience, alongside broad accuracy, reliability, and consistency improvements across every supported provider.
Changes are grouped below by API capability (Google Maps, Azure Maps, Melissa), with a first section covering enhancements that apply to all providers.
Highlights at a glance
Bulk Address Validation (Preview) - validate many records in one run from a table, API Configuration, field mapping, and a saved view or FetchXML.
Standardized confidence scoring across providers from a single shared source of truth.
More accurate postal / ZIP codes, including extended (ZIP+4) handling and a fix that had been dropping the ZIP from composed addresses.
Reliability fixes that eliminate silent write-back failures and a logging crash in the geocoding path.
License-check caching to reduce calls to the licensing service.
Usage telemetry for bulk jobs, and SharpXRM brand styling in the new UI.
Applies to all providers (cross-cutting)
New: Bulk Address Validation (Preview)
A new experience in the Address Validation for Dataverse app lets you validate the addresses on many records at once instead of one at a time. You choose a table, an API Configuration (any supported provider), and a Field Mapping, then target records with a saved/personal view or FetchXML.
Write-back modes: Overwrite (updates records in place) and Dry Run (no changes; produces a preview results CSV).
Standardized confidence scoring
Confidence levels are now derived from a single shared set of numeric tiers and mapped consistently to each provider's vocabulary. This also fixes bulk results that previously showed NOT_SUPPORTED, so confidence and the reporting service API are populated on the bulk path.
Reliability fixes
Silent write-back failures fixed: results without coordinates (e.g. when a provider omits geocode) no longer abort the record update. The corrected address is still written, existing coordinates are preserved, and only the coordinate fields are skipped. Bulk runs now correctly report such records instead of counting failures as successes.
Geocoding logging crash fixed: a disposed-content error during transaction logging that aborted response parsing (especially in bulk loops) has been resolved, and logging is now non-fatal.
Google Maps
Covers both Google Address Validation and Google Geocoding.
Country determination: added country-code resolution in the Google Address Validation service for more accurate results.
Extended postal codes: ZIP+4 / extended postal output is now surfaced.
Confidence mapping: Google Address Validation and Google Geocoding now map to the shared confidence tiers; a Google Maps Geocoding confidence-score bug was fixed.Ā
Logging and response formatting improvements for easier troubleshooting.
Azure Maps
Unit number preservation: secondary/unit information is retained through validation.
Extended postal code handling added.
Confidence mapping: Azure Maps now maps to the shared confidence tiers.
Logging and response formatting improvements for easier troubleshooting.
Melissa
Covers Personator validation and the Express Entry address autocomplete control.
Express Entry autocomplete: the PCF control was updated (v0.0.40) to expose the Native character set and diacritics parameters, with a refreshed control bundle and localized strings across all supported languages.
Ā