Microsoft architects demonstrated Connected Field Service with IoT alerts and HoloLens-based remote assistance in Dynamics 365.
This 2019 recording is part 3 of 3 from an event held by ProsessPilotene and Microsoft Norway on Dynamics 365 Field Service. An architect from Microsoft's Technology Center, together with colleagues, demonstrated how Connected Field Service links IoT sensors on machinery to Dynamics: abnormal readings, such as vibration outside normal range, automatically trigger an alert that can become a case and a work order.
The solution shows all IoT alerts in a dashboard, and work orders can be assigned to technicians based on defined skills, experience and geographic proximity. Two-way communication with the equipment was also shown, including the ability to send an emergency-stop command directly from Dynamics.
The second part of the demo showed HoloLens-based remote assistance: a field technician received hands-free, visual guidance from an expert over Teams to stop and repair a machine with abnormal vibration, and screenshots from the session were saved with the work order as documentation.
The demonstration closed with examples of use beyond the Field Service scenario itself, such as predictive maintenance based on sound patterns from failing motors, planning in the power grid industry, and a Norwegian hospital project that used HoloLens to plan paediatric heart surgery.
Ask a question or share what helped you.
Project management | Konferanse
DynUG brought the Dynamics 365, Power Platform and Fabric communities together in Oslo.
Artificial intelligence | Webinar
Frode Stenstrøm and Adrian Sjøholt tested Google, OpenAI and Anthropic AI models on real project-planning tasks, from requirements to a presentation.
Analytics and insight | Webinar
Yuliia Kamkova showed Frode Stenstrøm how Power BI can pull data from Dynamics 365 Project Operations and be embedded back into CRM.
Project management | Webinar
Terje Melheim and Ida Langdalen Kristiansen from Moelven told Frode Stenstrøm about active leadership and internal communication at the group.

Automation | Article
OpenAI’s Data agent could investigate company data and build shareable interactive dashboards. Access controls and source trails needed to follow analysis and action through the workflow.

Customer Service | Article
WEM MCP tools enabled time-off requests, shift swaps and shift bids in Service Agent. Administrators could enable each tool for a role, team or pilot group.

Automation | Article
Power BI reports and semantic models became grounding in Copilot Chat and Cowork. Shared chats, synced notebooks and Planner status connected analysis with collaboration.

Automation | Article
Microsoft replaced twice-yearly release waves with continuous roadmap publication. Customer processes needed to track status from development through rollout to launch.

Project management | Article
Copilot Notebooks and Cowork gained more ways to share project context. Agent metrics and cost controls expanded in the admin centre.

Customer Service | Article
Sales and Service Agent became generally available in Microsoft 365 Copilot. Dynamics described MCP actions across sales, service, field work and projects.
Share a question or reflection.
Be the first to contribute.