Dynamics 365 Field Service : Enable and configure location tracking and geofencing

In the world of field service management, keeping track of technicians’ locations and movements is not just a convenience—it’s a necessity. It helps in efficient dispatching, real-time monitoring, and most importantly, improves customer satisfaction through accurate ETAs and swift service delivery. Microsoft Dynamics 365 Field Service offers powerful Location Tracking and Geofencing capabilities to support this need.

In this blog post, we’ll explore:

  •  What location tracking and geofencing are
  •  Why they matter in field service
  •  Step-by-step instructions to enable and configure them in Dynamics 365 Field Service

What is Location Tracking?

Location Tracking refers to the ability to continuously capture and monitor the real-time location of field technicians using their mobile devices. This is typically powered by GPS and synced with Dynamics 365 through the Field Service mobile app.

 Key Use Cases:

  •  Real-time technician location on the schedule board map
  •  Accurate ETA for customers
  •  Historical travel routes for auditing or training
  •  Optimized resource dispatching

What is Geofencing?

Geofencing involves creating a virtual perimeter (or boundary) around a geographical location such as a customer site or warehouse. When a technician enters or exits this boundary, predefined automated actions or notifications can be triggered.

Common Examples:

  •  Automatically check in a technician upon arriving at the job site
  •  Notify dispatcher if the technician is delayed or leaves too soon
  •  Start/stop work orders or timesheets based on location

Step-by-Step: Enable and Configure Location Tracking

Prerequisites:

  •  Dynamics 365 Field Service environment
  •  Bookable Resources set up as field agents
  •  Installed Field Service Mobile (Power Platform-based mobile app)
  •  Proper user security roles: typically Field Service - Resource or Mobile User

Step 1: Enable Location Tracking in Settings

1. Navigate to Field Service Admin App

  • Go to your Dynamics 365 environment → Open Field Service Admin app.

2. Go to Field Service Settings

  • In the sitemap, click Settings → Field Service Settings.

3. Enable Location Tracking

  • Find the section Mobile Settings.
  • Set Location Tracking Enabled to Yes.
  • Define a tracking interval (e.g., every 5 minutes).

Step 2: Enable Location Sharing on Mobile Devices

On each technician’s mobile device:

  •  Open the Field Service (Power App).
  •  Go to the Settings section in the app.
  •  Ensure “Allow Location” is enabled in app permissions.
  •  Background location access should be set to always (on iOS/Android settings).

Note: Battery optimization settings may interfere with real-time updates—recommend setting the app to not be battery optimized.

Step 3: View Location in Schedule Board

  •  Open the Field Service → Schedule Board.
  •  Select Map View.
  •  You’ll now see real-time or last-known locations of technicians marked on the map.
  •  You can hover over their icons to view names and movement trails.

Step-by-Step: Configure Geofencing

Step 1: Set Up Geofences for Accounts or Work Orders

1. Navigate to Field Service → Accounts or Work Orders.

2. Open the record you want to geofence.

3. Add latitude and longitude coordinates (either manually or using the map control).

4. Save the record.

Step 2: Define Geofence Settings

  • Go to Settings → Geofencing Settings (this may need enabling in your org or accessed via environment variables).

Set the following options:

  •  Enable Geofencing: Yes
  •  Define entry and exit radius (e.g., 150 meters)
  •  Define triggers:
    •    Start/stop work order
    •    Log entry/exit events
    •    Send alerts to dispatcher/manager

Step 3: Automate Geofence Triggers Using Power Automate

You can create a Power Automate flow triggered on the Work Order Geofence Entry/Exit events.

Example:

  • Trigger: When Geofence Event is created
  • Condition: If Event = “Entered”
  • Action: Start Time Entry + Notify Manager

Security and Compliance Considerations

  • Privacy: Always inform technicians about location tracking and its purpose.
  • Data retention: Configure how long you store location data—balance operational needs with data privacy.
  •  Access Control: Limit who can view location history or live tracking.

Final Thoughts

Enabling location tracking and geofencing in Dynamics 365 Field Service can significantly improve efficiency, safety, and transparency in field operations. While the setup requires some configuration on both the admin and technician side, the ROI in terms of time saved, improved customer service, and operational control is substantial.

With careful implementation and respect for user privacy, these features can be game-changers for any service organization aiming to modernize and optimize their field workforce.

Comments

Post a Comment

Popular posts from this blog

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

Connecting the Dots: FetchXML and Web API Integration in Dataverse

Image
 In Dataverse, FetchXML and the Web API are two powerful mechanisms for retrieving data and interacting with entities. Here's a brief overview of each and how they can be integrated: 1.    FetchXML :      -   Definition:   FetchXML is a proprietary query language used in Microsoft Dynamics 365 and Dataverse for querying data from entities.    -   Usage:   FetchXML queries can be used to retrieve data based on complex criteria, perform aggregations, and filter records.    -   Features:   FetchXML supports various query expressions, including conditions, sorting, grouping, and aggregation functions.    -   Integration:   FetchXML queries can be executed programmatically using client-side scripting, server-side code, or through tools like the Dynamics 365 Web API. 2.    Web API :      -   Definition:  ...
Read more