Connected Field Service for Azure IoT Hub Setup

(4) Share

Report

Posted on by Krish9677

Hi D365 Community,

I'm working on setting up Connected Field Service (CFS) with Azure IoT Hub, and I'm running into some issues. I've followed the Microsoft documentation https://learn.microsoft.com/en-us/dynamics365/field-service/installation-setup-iothub for the setup, https://github.com/microsoft/Dynamics-365-Connected-Field-Service-Deployment#deploy-the-arm-template but I'm just not getting it to work correctly. I'm relatively new to CFS, so please bear with me if I'm missing something obvious!

My main problem is that devices aren't syncing between CFS and IoT Hub. When I create a device in CFS, it doesn't seem to sync with Azure IoT Hub. And if I create a device in IoT Hub, it doesn't appear in CFS. I've double-checked the configurations as best I can, but I'm still stuck.

Since I'm new to CFS, I'm wondering if there are any common "newbie" mistakes I might be making. Has anyone else experienced similar problems, especially when first starting out? Any tips or troubleshooting steps you could share would be greatly appreciated.

I'm particularly interested in:

* Common pitfalls in the CFS and IoT Hub integration.
* Best practices for device registration and synchronization.
* Any tools or logs that can help diagnose the issue.
* Anything that might be specific to someone just starting out with CFS.

Thanks in advance for your help!

Best regards,

Krish

Categories:

Dynamics 365 Field Service

I have the same question (0)

All responses (3)

Answers (2)

Verified answer

Holly Huffman 6,530 Super User 2025 Season 2 on at

Like (1)

Report
Hi there!

Apologies if you've already checked these things:

First thought is permissions - checking that IoT devices have the right permissions assigned for CFS?

Double checking strings, endpoints to ensure IoT and CFS match

Do devices IDs match in both systems?

Ensuring IoT hub has appropriate security roles assigned

Any networking blocks / firewall ports not opened?

Have you been able to run any logs we could look through?

Was this reply helpful? Yes No
Vahid Ghafarpour 12,090 Super User 2025 Season 2 on at

Like (2)

Report

I think iothub diagnostics would be great option, it is old but can help you

https://github.com/Azure/iothub-diagnostics

Was this reply helpful? Yes No
Verified answer

Muhammad Shahzad Sh... 2,373 Most Valuable Professional on at

Like (1)

Report
1. Common Pitfalls:

Missing IoT Connector (Azure Function App) deployment.

Not enabling IoT Alerts to Work Orders in CFS settings.

Incorrect IoT Hub connection string or shared access policies.

2. Device Sync Best Practices:

Devices must be created in IoT Hub first; CFS pulls them via the Azure Function.

Use the Register Device plugin in CFS only after confirming IoT Hub connectivity.

3. Diagnostics:

Check Azure Function logs in Application Insights.

Review IoT Provider record in Dynamics 365 for correct config.

Use Device-to-cloud message tracking in IoT Hub.

4. Tips for Beginners:

Always deploy via the ARM Template before testing.

Ensure Event Grid and IoT Hub permissions are granted to the function app.

Don’t skip setting up Device IDs properly in IoT Hub before linking in CFS.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Connected Field Service for Azure IoT Hub Setup

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

Featured topics

Product updates

Community site session details

Connected Field Service for Azure IoT Hub Setup

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

Featured topics

Product updates