Personalized Community is here!
Quickly customize your community to find the content you seek.
‘Better Together’ Integration forum available
We're launching a how-to forum where you can learn and engage about how Dynamics 365 integrates with other Power Platform products.
Read about Better Together forum
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We recently published documentation for Connected Field Service that tells you everything you need to know to use custom IoT providers in Dynamics 365 Field Service. The article is geared toward developers who want to know what capabilities are supported in our IoT extensible framework, and how to make it all happen.
As organizations around the globe continue with a remote workforce, Connected Field Service enables service teams access to important Internet of Things (IoT) data from wherever they are workingensuring the essential businesses they serve are reliably up and running.
Connected Field Service already has integration for IoT signals, device registration, and sending commands with Azure IoT Hub and Azure IoT Central.
However, there are plenty of companies out there where IoT signals are sent to other IoT systems, some of which have been in place for years.
With the extensibility framework, even companies who are using IoT providers other than Azure can still use all the Connected Field Service components to connect and interact with their IoT devices and data.
Organizations may even use multiple IoT systems for different types of assets, for example, in situations where newer assets are deployed on one IoT cloud while legacy assets remain on other systems, or when industry-specific IoT providers are used for different types of assets.
Whether you’re using multiple Azure IoT instances, a mix between Azure and other systems, or a different IoT provider altogether, you can now interact with and use your IoT data within Dynamics 365 and Microsoft Power Platform. Several organizations have put the framework to use and are already live.
Remember, even if your Dynamics 365 Field Service project is not underway or you are early in your implementation, you can still use all the Connected Field Service components to connect and interact with your IoT data within your other Dynamics 365 apps.
Check out the article Extensible IoT data sources for Connected Field Service to learn more.
The post Use custom IoT providers in Connected Field Service appeared first on Microsoft Dynamics 365 Blog.
Business Applications communities