Merge pull request #10515 from MicrosoftDocs/freshness-field-service-jan

AB#9206: Freshness field service jan

Author: haywoodsloan

.openpublishing.redirection.json

@@ -12663,6 +12663,10 @@
       "redirect_url": "/dynamics365/field-service/deprecations-field-service#dynamics-365-field-service-integrations-with-microsoft-outlook-teams-viva-connections-and-planner---september-1-2025",
       "redirect_document_id": false
     },
+    {
+      "source_path": "support/dynamics-365/field-service/administration/attibutemap-error-upgrade.md",
+      "redirect_url": "/dynamics365/field-service/update-field-service"
+    },
     {
       "source_path": "support/dynamics-365/finance/tax/tcs-troubleshooting-failed-access-tax-service.md",
       "redirect_url": "/troubleshoot/dynamics-365/finance/welcome-finance",

support/dynamics-365/field-service/administration/attibutemap-error-upgrade.md

@@ -1,10 +1,8 @@
 ---
 title: Can't find a user when setting up frontline workers
 description: Resolves an issue where you can't find a user when trying to assign security roles in a new Field Service environment.
-author: jasonxian-msft
-ms.author: jasonxian
-ms.reviewer: v-wendysmith
-ms.date: 11/25/2024
+ms.reviewer: jacoh, v-wendysmith
+ms.date: 01/09/2026
 ms.custom: sap:Administration
 ---
 # Can't find a user when setting up frontline workers in Dynamics 365 Field Service
@@ -13,7 +11,7 @@ This article helps resolve an issue where you can't find a user when [setting up
 
 ## Symptoms
 
-When you try to [assign security roles to a user](/dynamics365/field-service/flw-admin?tabs=viva#assign-security-roles-and-field-security-profiles) when setting up frontline workers in a new Field Service environment, you can't find the user in the **Users** lookup field.
+When you try to [assign security roles to a user](/dynamics365/field-service/flw-admin?tabs=viva#assign-security-roles-and-field-security-profiles) while setting up frontline workers in a new Field Service environment, you can't find the user in the **Users** lookup field.
 
 :::image type="content" source="media/cannot-find-user-set-up-frontline-workers/users-field.png" alt-text="Screenshot of adding frontline workers in Dynamics 365 Field Service." lightbox="media/cannot-find-user-set-up-frontline-workers/users-field.png":::
 

support/dynamics-365/field-service/administration/cannot-find-user-set-up-frontline-workers.md

@@ -1,10 +1,8 @@
 ---
 title: Can't identify the user shown in an error message 
 description: Resolves an issue where you can't identify the user shown in an error message in Microsoft Dynamics 365 Field Service.
-author: jasonxian-msft
-ms.author: jasonxian
-ms.reviewer: v-wendysmith
-ms.date: 11/25/2024
+ms.reviewer: jacoh, v-wendysmith
+ms.date: 01/09/2026
 ms.custom: sap:Administration
 ---
 # Can't identify the user shown in an error message in Dynamics 365 Field Service

support/dynamics-365/field-service/administration/cant-identify-user.md

@@ -1,8 +1,8 @@
 ---
 title: Can't create or save records due to address geocoding mapping service degradation
 description: Provides a workaround to resolve issues with saving records during service degradation of the Geo Code API in Dynamics 365 Field Service.
-ms.reviewer: mhart
-ms.date: 06/18/2024
+ms.reviewer: jasonshotts, v-wendysmith
+ms.date: 01/13/2026
 ms.custom: sap:Administration
 ---
 # Can't create or save records due to service degradation of the address geocoding mapping service
@@ -15,19 +15,19 @@ Users can't save records, such as work orders, accounts, contacts, or system use
 
 ## Cause
 
-The issue originates from a service degradation in the location APIs that the [Universal Resource Scheduling](/dynamics365/field-service/universal-resource-scheduling-for-field-service) solution uses to get the latitude and longitude information for addresses.
+The issue comes from service degradation in the location APIs that the [Universal Resource Scheduling](/dynamics365/field-service/universal-resource-scheduling-for-field-service) solution uses to get the latitude and longitude information for addresses.
 
 ## Workaround
 
 As a user, try saving the record again to ensure it's not a temporary issue.
 
 As an administrator:
 
-- To unblock operations like creating or updating records in case of a consistent failure, you can temporarily disable the [Auto Geo Code Addresses](/dynamics365/field-service/turn-on-auto-geocoding) setting in **Field Service Settings**. After re-enabling the setting, users need to manually geocode records that were updated during the outage.
+- To unblock operations like creating or updating records in case of a consistent failure, temporarily disable the [Auto Geo Code Addresses](/dynamics365/field-service/turn-on-auto-geocoding) setting in **Field Service Settings**. After re-enabling the setting, users need to manually geocode records that you updated during the outage.
 
   > [!CAUTION]
   >
-  > Disabling automatic geocoding doesn't update the geocoded information for records with updated addresses. Records might have no location information or outdated latitude and longitude values, which might affect scheduling activities that rely on location coordinates. We recommend tracking the updated records while the setting is disabled to address data gaps retroactively.
+  > Disabling automatic geocoding doesn't update the geocoded information for records with updated addresses. Records might have no location information or outdated latitude and longitude values, which might affect scheduling activities that rely on location coordinates. Track the updated records while the setting is disabled to address data gaps retroactively.
 
 - If your organization uses custom apps that call the location APIs directly from any of their processes, adjust the processes to stop calling them until the service degradation is resolved.
 

support/dynamics-365/field-service/administration/disable-auto-geo-code.md

@@ -1,10 +1,8 @@
 ---
 title: Entity record names have duplicate numbers
 description: Resolves issues with the incremental numbering of records for Dynamics 365 Field Service entities with auto-numbering.
-author: jshotts
-ms.author: jasonshotts
-ms.reviewer: mhart
-ms.date: 11/25/2024
+ms.reviewer: jasonshotts, v-wendysmith
+ms.date: 01/12/2026
 ms.custom: sap:Administration
 ---
 # Entity record names have duplicate numbers in Dynamics 365 Field Service

support/dynamics-365/field-service/administration/entity-names-duplicated-numbers.md

@@ -1,10 +1,8 @@
 ---
 title: Incorrect user privileges errors in Dynamics 365 Field Service
 description: Resolves privileges errors that occur when a user tries to access work orders in Microsoft Dynamics 365 Field Service.
-author: jasonxian-msft
-ms.author: jasonxian
-ms.reviewer: v-wendysmith
-ms.date: 11/25/2024
+ms.reviewer: jacoh, v-wendysmith
+ms.date: 01/09/2026
 ms.custom: sap:Administration
 ---
 # Incorrect user privileges errors in Dynamics 365 Field Service
@@ -28,8 +26,5 @@ When a user tries to access work orders, the following error messages appear, in
 > [!NOTE]
 > You need administrator permissions in Dynamics 365 Field Service to perform the following action.
 
-To solve this issue, [assign the correct security role and field security profile](/dynamics365/field-service/flw-admin?tabs=viva#assign-security-roles-and-field-security-profiles) to the user.
+To resolve this issue, [assign the correct security role](/dynamics365/field-service/users-licenses-permissions#assign-security-roles) and [field security profile](/dynamics365/field-service/security-permissions) to the user.
 
-## More information
-
-[Set up users, licenses, and security roles](/dynamics365/field-service/users-licenses-permissions)

support/dynamics-365/field-service/administration/media/cant-identify-user/systemuser-id.png

@@ -1,10 +1,8 @@
 ---
 title: No records after pulling IoT device data
 description: Resolves issues with missing data from IoT devices in Dynamics 365 Field Service by setting the Azure IoT Hub pricing and scale tier to S1-Standard.
-ms.author: vhorvath
-author: vhorvathms
-ms.reviewer: mhart
-ms.date: 11/05/2024
+ms.reviewer: vhorvath, v-wendysmith
+ms.date: 01/13/2026
 ms.custom: sap:IoT - Connected Field Service
 ---
 # No records after pulling IoT device data in Dynamics 365 Field Service

support/dynamics-365/field-service/administration/user-has-no-roles.md

@@ -1,10 +1,8 @@
 ---
 title:  Troubleshoot issues with IoT capabilities
 description: Provides a resolution to solve issues with IoT capabilities in Dynamics 365 Field Service.
-ms.author: vhorvath
-author: vhorvathms
-ms.reviewer: mhart
-ms.date: 11/05/2024
+ms.reviewer: vhorvath, v-wendysmith
+ms.date: 01/14/2026
 ms.custom: sap:IoT - Connected Field Service
 ---
 # Troubleshoot issues with IoT capabilities in Dynamics 365 Field Service