In Australia and perhaps other countries around the world, address standard include the 'Neighborhood' field from Bing Maps, not the 'City' field. For example, Adelaide in South Australia has a population of 1+ million and covers hundreds of square miles. Addresses are NOT written as: 1 George St Adelaide SA 5063 (incorrect) where 'Adelaide' is returned in the 'City' field from Bing Maps, but rather: 1 George St Parkside SA 5063 (correct) where 'Parkside' is returned in the 'Neighborhood' field from Bing Maps. The suggestion is simply to introduce a Boolean configuration option that overrides the mapping of the 'City' field in D365 from the default Bing Maps 'City' to the 'Neighborhood' field. Alternatively, instructions on how to change/override the current code that performs this mapping could be made available (if technically feasible).

Category: Field Service
Under Review
Ideas Administrator

Thank you for your feedback.

Currently, we're working with Bing to see how this can be accomplished. We are aware of this ask and are tracking it. If we get positive feedback from Bing, we'd like to consider it in the future.


Jason Cohen

PM, Microsoft



I agree, this seems like a function that could easily be fixed for us in Australia.
I'm sure that other countries would experience the same issue when you are trying to map a Suburb rather than the City it is in.
The Dynamics 365 Field Service Account Address form has both the Suburb and City fields available, surely it is a matter of providing an option of mapping the fields from the Bing Maps data to the relevant fields in FS.

We raised a ticket today and they said it was a known function and that the Australian Address convention is different. They said that it wouldn't be changed unless there was enough support on the ideas page.
Our customers want Google Maps but we're stuck with Bing and Microsoft don't want to fix or improve it.
What a bummer...

Category: Field Service