Best approach to integrate a Dynamics 365 F&O ISV with Microsoft Teams

Hi @nadhira thembavani
Based on the information you provided, I understand that your company develops ISV solutions for Dynamics 365 Finance & Operations (F&O) and you are exploring the best approach to integrate deeper with Microsoft Teams. Your core scenarios include receiving Teams notifications for business events, launching approval workflows from Teams, and performing CRUD operations on F&O records.

For an ISV scenario in Dynamics 365 F&O, the recommended approach is to prioritize Power Platform combined with F&O Business Events, and then adopt custom Teams apps, Bots, or Graph APIs when you need a more advanced and native Teams experience.

A foundational pipeline you can follow is: Dynamics 365 F&O business event > Power Automate cloud flow > Teams / Approvals / Write data back to F&O.

F&O Business Events are specifically designed to send notifications to external systems when a business process occurs (such as workflow actions or non-workflow events). Microsoft emphasizes that these business events can be consumed via Power Automate or Azure messaging services, but they should be kept lightweight and not used for large data exports.

Here is the technical approach for each specific scenario:

-Teams notifications from business events: Trigger an F&O business event, route it through Power Automate, and then send a standard Teams message or an Adaptive Card. If you need a highly customized UX, you can route it through a custom Teams notification bot.

Send notifications

-Launching approval workflows from Teams: Use Power Automate Approvals triggered by the F&O Business Event or workflow engine. The flow looks like this: F&O triggers the event > Power Automate starts and validates the workflow > Launches the Teams approval card > Updates the result back into F&O.

Business events and workflow approvals

-Creating or updating data directly from Teams: Utilize F&O Data Entities / OData endpoints or the native F&O connector within Power Automate. F&O provides a robust REST OData endpoint for CRUD operations. For complex or ISV-specific logic, it is best to expose these via F&O Custom Services (APIs) or run them through Azure middleware.

When your integration requires a rich user experience (such as proactive messages, native Teams UI, or a reusable packaged application for your ISV customers), you should build a Custom Teams App utilizing tabs, bots, Adaptive Cards, and the Graph API.

To choose between Power Automate, Microsoft Graph, and Custom Development, consider the following situations:

• Use Power Automate when you need event-driven logic, simple business workflows, low-code solutions that are easy to maintain, and quick deployment utilizing standard Teams and approval connectors.
• Use Microsoft Graph when you need deep interactions with the Teams environment (such as managing apps, channels, or user context), building custom teams apps/bots, or when Power Automate doesn't offer enough flexibility. For example, Teams proactive messaging documentation states that the app/bot must have the required access, and for some scenarios the app may need to be proactively installed using Microsoft Graph.
• Use Custom Development when you are packaging a final product as an ISV solution, requiring robust retry mechanisms, advanced logging, complex security architectures, multi-tenant support, and professional deployment capabilities.

I hope this information helps.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click ""Comment"".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.