Microsoft Power Platform (Power Apps, Power Automate, Power BI, Power Pages) extends D365FO beyond its standard UI — enabling mobile apps, intelligent automation, embedded analytics, and self-service portals. This guide covers the integration architecture for each Power Platform component.
Integration Architecture Overview
D365FO and Power Platform share the Microsoft Dataverse (formerly Common Data Service) as a common data layer when using Dual-write. There are multiple integration patterns, each with different trade-offs:
| Integration Method | Use Case | Latency | Complexity |
|---|---|---|---|
| Dual-write | Real-time bidirectional sync of master data | Near-real-time | Medium |
| Virtual tables | Read D365FO data directly in Power Apps without ETL | Real-time (read) | Low |
| OData / REST API | Custom integrations, write operations from Power Automate | Real-time | Medium |
| Data Export Service | Analytics, Power BI, read-heavy scenarios | Batch (configurable) | Low |
| Azure Service Bus | Event-driven integration, decoupled architecture | Near-real-time | High |
Power Apps Integration with D365FO
Option 1: Virtual Tables (Recommended for Read Scenarios)
Virtual tables allow Power Apps to query D365FO data entities directly — without replicating data to Dataverse. Setup requires:
- D365FO Finance Insights virtual table solution installed in your Dataverse environment
- Virtual table configuration linking your D365FO instance
- Appropriate security roles in both D365FO (data entity access) and Dataverse
Virtual tables are ideal for canvas apps showing D365FO data (orders, inventory, invoices) without write-back requirements.
Option 2: Dual-write for Master Data
Dual-write synchronizes master data (customers, vendors, products, contacts) between D365FO and Dataverse in near-real-time. This is ideal when:
- You need the same customer/vendor records available in both D365FO and D365 CRM
- Changes made in either system should reflect immediately in the other
- You're building Power Apps that both read and write master data
Power Automate Integration Patterns
Power Automate connects to D365FO through two primary mechanisms:
D365FO Connector (OData-based)
The D365FO connector in Power Automate exposes standard actions for creating, reading, updating, and deleting D365FO entity records. Common use cases:
- Purchase requisition approval: Route D365FO purchase requisitions through Teams-based approval flows
- Customer onboarding: When a new customer is created in CRM, automatically create the corresponding customer record in D365FO
- Invoice notification: When a D365FO invoice is posted, trigger an email or Teams notification to the relevant stakeholder
Business Events
D365FO Business Events are the most robust integration pattern for event-driven workflows. When something happens in D365FO (invoice posted, PO confirmed, payment made), a Business Event fires to Azure Service Bus or Event Hub, triggering downstream actions in Power Automate or other systems.
Power BI Integration: Embedded Analytics
Power BI integration with D365FO provides executive dashboards and operational reports directly within the D365FO interface. Two deployment options:
Analytical Workspaces (Recommended)
D365FO supports embedding Power BI reports directly into workspace forms. This provides:
- Context-aware analytics alongside operational D365FO forms
- No need for users to leave D365FO for reporting
- Row-level security inherited from D365FO security model
External Power BI Service
For enterprise BI deployments, connect Power BI Desktop to D365FO via:
- Entity Store (aggregate measurement cubes) for pre-aggregated analytical data
- BYOD (Bring Your Own Database) for near-real-time operational reporting
- Azure Data Lake for large-scale analytics with Azure Synapse
Power Pages: Self-Service Portals
Power Pages (formerly Power Apps portals) enables external-facing web portals connected to D365FO data through Dataverse virtual tables or Dual-write. Common portal scenarios include:
- Vendor portals: Vendors submit invoices, track payment status, update bank details
- Customer portals: Customers view orders, invoices, delivery status, and submit returns
- Employee self-service: HR portals for expense submission, leave requests, pay slip access
At Innovegens, we've built Power Pages portals for clients including UniPro (vendor portal) and CBW (customer-facing order status portal). The key to a successful portal implementation is getting the security model right — ensuring external users can only see their own data.