Power Platform + Business Central: The Full Stack for SMEs (2026)

What 'Power Platform for Business Central' actually means

Power Platform is Microsoft's low-code suite: Power Apps, Power Automate, Power BI, Power Pages, and Copilot Studio. Business Central is the ERP. Connecting them means you can extend BC - custom apps, automated workflows, richer reporting, external portals, AI agents - without heavy AL development or a rip-and-replace project.

There are two integration paths and the distinction matters. The first is the Business Central connector, a REST-based premium connector that exposes BC data and business actions to Power Apps, Power Automate, Copilot Studio, and Azure Logic Apps. The second is virtual tables: the Business Central Virtual Table app publishes BC tables into Dataverse so Power Platform can do full CRUD on them at runtime via OData, without copying the data out of BC.

In both cases the data and the business logic stay in Business Central. Power Platform reads and writes through the connector or through virtualized tables. That keeps BC as the system of record and avoids the data-residency and sync-headache problems that come with exporting ERP data into a separate database.

This page is the umbrella hub for the whole stack. For deep dives on individual components, see our dedicated guides on Business Central + Power Automate and Business Central + Power BI.

• →Power Platform = Power Apps, Power Automate, Power BI, Power Pages, Copilot Studio
• →Two integration paths: BC connector (REST APIs) and virtual tables in Dataverse (no data copy, full CRUD)
• →Data and business logic stay in BC; Power Platform reads and writes at runtime
• →Extends BC without heavy AL development or replacing the ERP

Power Apps + Business Central: custom apps on ERP data

Power Apps lets you build canvas apps (free-form, pixel-controlled) and model-driven apps (data-first, generated from Dataverse) that read and write Business Central data. You connect to BC either through the premium BC connector or through virtual tables published to Dataverse.

Canvas apps suit task-specific interfaces - a warehouse picker, a field-service timesheet, a trade-show lead-capture form - where you want a tailored mobile experience without touching BC's role centers. Model-driven apps suit structured, relationship-heavy processes (vendor onboarding, multi-step approvals) where the data model drives the UI.

Because virtual tables expose BC data as if it lived in Dataverse, model-driven apps can do full create-read-update-delete on BC records without a sync job. The trade-off is documented limitations - no support for charts, attachments, images, BLOBs, or multiline strings through virtual tables, and restricted advanced search (no Does Not Equal, Contains, Begin With, or End With; limited AND/OR across columns; no filtering on calculated fields). Plan around these before you commit a screen to them.

• →Canvas apps for task-specific, mobile-tailored experiences (warehouse, field service, lead capture)
• →Model-driven apps for structured, relationship-heavy processes (onboarding, approvals)
• →Virtual tables enable full CRUD on BC data from model-driven apps without copying data
• →Virtual-table limits: no charts, attachments, images, BLOBs, multiline strings; restricted filtering

Power Automate + Business Central: cross-system workflows

Power Automate builds event-driven flows between BC and the rest of your stack - Outlook, Teams, SharePoint, Excel, Dataverse, and thousands of other services. The BC connector is the surface: it provides triggers (record created, modified, deleted, changed; approval requested) and actions (CRUD, find records, run BC business actions, deep links, adaptive cards for Teams).

Flows are embedded in the BC client. On most list, card, and document pages the 'Automate' action group lets users kick off context-aware templates from the record they are already on, and AL developers can add custom page actions that trigger flows for deeper integration.

Two practical notes for SMEs. First, the BC connector is a premium connector - automated and scheduled flows need a Premium license on the owner, and instant ('For a selected record') flows need a Premium license on every user who runs them. Second, records are limited to under 8 MB per call and the connector is throttled at roughly 300 API calls per 60 seconds per connection, so high-volume environments need filtering or batching upstream.

We cover triggers, actions, approval flows, licensing traps, and limitations in depth in our dedicated Power Automate + Business Central guide.

• →Event-driven flows between BC and Outlook, Teams, SharePoint, Excel, and thousands of services
• →Embedded in the BC client via the 'Automate' action group; AL actions can also trigger flows
• →Premium connector - owner-licensed for automated/scheduled flows, invoker-licensed for instant flows
• →~300 API calls / 60 seconds / connection and an 8 MB per-record cap - plan filtering accordingly

Power BI + Business Central: reporting and dashboards

Business Central online ships with built-in Power BI integration. BC maintains a read-only database replica so reporting queries do not impact transactional performance, and it exposes operational data through API pages and queries (preferred) or legacy OData web services, all consumed by the Power BI connector.

The integration is layered. Embedded reports appear inside BC as Role Center parts and list-page FactBoxes. The Power BI service hosts full interactive dashboards that can be shared. Power BI Desktop is where you build custom semantic models and reports on top of the same feeds.

Microsoft publishes a dedicated BC Power BI app for each functional area - Finance, Sales, Purchasing, Inventory, Inventory Valuation, Projects, Manufacturing, Subscription Billing, Sustainability - each bundling a semantic model and a library of reports. Audit the app for your area before building anything custom; the report your finance team is asking for often already exists.

For the connection steps, default reports by area, and the licensing traps that catch SMEs, see our dedicated Business Central + Power BI guide.

• →Built-in integration; BC keeps a read-only replica so reporting does not slow transactions
• →Data exposed via API pages/queries (preferred) or legacy OData web services
• →Three layers: embedded reports in BC, dashboards in the Power BI service, models in Power BI Desktop
• →Pre-built BC Power BI apps per functional area - check before building custom

Power Pages + Business Central: external B2B portals

Power Pages is the website-building component of Power Platform - external-facing pages built on Dataverse. To reach Business Central data you go through the same two paths as the rest of the suite: the BC premium connector (good for read-heavy and workflow-triggered pages) or BC virtual tables published into Dataverse (good when the portal needs full CRUD on live ERP records without a sync job).

Typical SME use cases are B2B self-service: a customer portal for order status, invoice history, and statement download; a vendor portal for purchase-order acknowledgement and invoice submission; a dealer or agent portal for quoting. Because Power Pages is licensed per authenticated user per month, it suits portals with a manageable external user count rather than high-volume public traffic.

The guardrails matter. Virtual tables still carry their documented limits (no attachments, images, BLOBs, or multiline strings), so anything involving document upload or binary content needs a workaround - typically a flow that writes the attachment directly to BC through the connector while the portal stores only metadata in Dataverse.

• →External-facing portal builder on Dataverse; reaches BC via connector or virtual tables
• →Strong fit for B2B self-service: customer, vendor, and dealer portals
• →Per-authenticated-user monthly licensing - plan for manageable external user counts
• →Attachment/binary limits on virtual tables usually need a Power Automate workaround

Copilot Studio + Business Central: AI agents on ERP data

Copilot Studio is where you build agents and copilots that ground their answers in your Business Central data. An agent connects to BC through the same premium connector, through virtual tables, or through the BC API, then uses that knowledge source to answer questions, summarize records, and trigger actions inside a conversation.

For SMEs the realistic patterns are internal productivity copilots (an operations person asks 'what's the status of this customer's open orders and credit hold?' and gets a grounded answer with deep links) and lightweight external copilots on a Power Pages site (a customer asks 'where is my invoice?' without opening a ticket). Copilot Studio is also the surface that orchestrates plugin actions - so a copilot can run a BC business action, kick off a Power Automate flow, or hand off to a human via Teams.

Two cautions. First, agents are only as good as their grounding - point them at scoped BC tables or API pages, not the whole company database, or they hallucinate. Second, generative answers consume capacity-based licensing (Copilot Studio message packs, or the Microsoft 365 Copilot license for full tenants), so estimate conversational volume before you commit to a tier.

• →Build agents grounded in BC data via the connector, virtual tables, or the BC API
• →Internal productivity copilots and lightweight external copilots on Power Pages
• →Plugin actions let an agent run BC business actions or trigger Power Automate flows
• →Scope the knowledge source and estimate message-pack volume before you commit a tier

BC connector vs virtual tables: choosing the integration path

Almost every architectural question on Power Platform + Business Central reduces to which of the two integration paths you lean on. The table below is the decision summary we walk SMEs through.

Power Platform + Business Central licensing in 2026

Licensing is where SME budgets leak. The rule of thumb: Business Central itself (Essentials or Premium) does not include Power Platform per-user licensing beyond what attaches to a Microsoft 365 plan, so most non-trivial Power Platform work on BC needs a separate Power Apps Premium or Power Automate Premium per-user plan, or a Pay-As-You-Go meter.

Microsoft's 2025 consolidation folded the old Power Apps per app and Power Automate per flow standalone offers into a single Power Apps Premium per-user plan (US$19.75/user/month) and a Power Automate Premium per-user plan (US$19.75/user/month). Power BI Pro is US$9.99/user/month; Power BI Premium Per User (PPU) is US$19.75/user/month. Power Pages is licensed per authenticated user per month. Copilot Studio is consumed via message packs or via Microsoft 365 Copilot.

Two traps catch SMEs every time. First, instant flows ('For a selected record') require every user who runs them to have a Premium license, not just the flow owner - that quietly multiplies cost across a sales or warehouse team. Second, Pay-As-You-Go (US$0.50/user/month billed against an Azure subscription) looks cheap but is unbounded; it suits pilots, not steady-state production. Treat the per-user Premium plan as the default for any flow or app that more than two people run.

• →BC Essentials/Premium do not bundle Power Platform Premium per-user licensing
• →Power Apps Premium and Power Automate Premium are US$19.75/user/month each (2025 consolidation)
• →Power BI Pro US$9.99; PPU US$19.75; Power Pages per authenticated user/month; Copilot Studio via message packs or M365 Copilot
• →Instant flows need Premium on every invoker - the #1 SME licensing surprise

Limitations and gotchas to plan around

Every Power Platform component that touches Business Central has a documented limit that becomes a project risk the day you ignore it. The ones below are the recurring offenders across SME implementations.

Virtual tables: no charts, attachments, images, BLOBs, or multiline strings; restricted filtering (no Does Not Equal, Contains, Begin With, End With; limited AND/OR across columns; no filtering on calculated fields). Connector: ~300 API calls per 60 seconds per connection, sub-8 MB per record. Power Automate: action/request limits per license tiers, 5-minute conversation timeout on-demand, and per-flow daily limits on seeded plans. Power BI: the BC connector is read-only against the API replica, so real-time OLTP is not what it gives you - it gives you near-real-time operational reporting.

• →Virtual tables: no attachments, images, BLOBs, multiline strings, or calculated-field filtering
• →BC connector throttled at ~300 calls/60s/connection; sub-8 MB records
• →Power Automate: per-license action/request limits and on-demand 5-minute conversation timeout
• →Power BI against BC is read-only operational reporting, not real-time OLTP