
“We’d love a phone app for site requests, but that means a new system, a new licence for everyone and a team of developers.” Above all, we hear some version of that sentence a lot. However, most of it is a myth. Power Apps for Business Central lets you put simple apps on top of the ERP you already run, so field staff and managers can raise requests, capture data and approve work without opening the full Business Central screens.
So in this guide we take five popular myths and test each one against what Microsoft actually documents. Along the way, you get the real licence prices, a step-by-step approval flow, a realistic project timeline and the best practices that keep these apps fast and safe.
Key takeaways
- Power Apps and Power Automate connect to Business Central through Microsoft’s own connector, so Business Central stays your single source of truth.
- Microsoft lists Power Apps Premium at US$20 per user/month (paid yearly), but licensed Business Central users already get use rights for apps and flows that extend Business Central.
- A focused approval or field-data app can be built in phases: scope, design, build, test, train and go live. The exact timeline is fixed after a free consultation.
What is Power Apps for Business Central, really?
Think of Business Central as the engine room of your business and Power Apps as a set of custom remote controls. First, the engine (your ledgers, items, vendors and documents) stays where it is. Meanwhile, each remote control does one job well, such as “request materials” or “approve this order”, on a phone, in Teams or in a browser.
Technically, Business Central has a connector that lets Power Apps, Power Automate, Copilot Studio and Azure Logic Apps talk to it through its REST APIs. In other words, an API is a safe, standard doorway that other apps use to read and write data. In practice, Power Apps builds the screens, while Power Automate runs the flows, for example sending an approval and waiting for the answer. Now, let’s test the five myths.
| Myth | Fact (from Microsoft’s documentation) |
|---|---|
| 1. “Power Apps replaces Business Central.” | It sits on top. In fact, apps read and write Business Central data through the connector, so postings still happen in Business Central. |
| 2. “Every app user needs an extra licence.” | Not always. Dynamics 365 licences, including Business Central, carry Power Apps use rights in the context of the licensed app. Otherwise, users without one need their own licence. |
| 3. “You need developers for everything.” | Actually, canvas apps are low-code. However, tables that aren’t exposed as standard APIs need a developer to build a custom API. |
| 4. “Approvals need a custom app.” | In reality, Business Central has built-in approval workflows, and Power Automate offers ready templates for purchase, sales, vendor, customer, item and journal approvals. |
| 5. “Field apps stop working without signal.” | Canvas apps can work offline in the Power Apps mobile app, though not in a web browser. Even so, offline needs careful design. |
Why it matters for UAE & GCC businesses
Many GCC companies run teams across several sites, emirates or countries. For example, site supervisors, drivers, technicians and branch managers rarely sit at a desk, yet finance needs their requests and data in the ERP quickly and with an audit trail. That is exactly the gap a small app plus an approval flow fills, because it brings the request to the person instead of the desk.
In addition, data location matters. According to Microsoft, Business Central environments for the UAE, Saudi Arabia, Qatar, Kuwait, Bahrain and Oman are deployed to the UAE Azure geography. Likewise, Power Platform offers a United Arab Emirates region. As a result, you can usually keep your apps and flows in the same region as your ERP data. Finally, there is a timely licensing point: Microsoft says that from February 2027 it will apply stricter licence checks to some Power Apps scenarios, so it is worth reviewing who uses which app now.
How it works: one approval, step by step
Here is the most common pattern we see requested: a purchase request raised on a phone and approved by a manager. Moreover, each step uses standard Microsoft building blocks.
- Capture. A site supervisor opens a canvas app in the Power Apps mobile app, picks the vendor and items, and adds a photo.
- Create. The app uses the Business Central connector to create a purchase order through the standard purchaseOrder API, and attaches the photo.
- Request approval. The order is sent for approval, which triggers the Power Automate flow “When a purchase document approval is requested”.
- Route. Conditions in the flow (for example, the amount) decide who must approve it.
- Decide. The approver gets an email with Approve and Reject buttons and can add a comment.
- Update. The flow’s Yes or No branch acts on the request in Business Central and emails the requester, so the order can move on to purchasing.

What does Power Apps for Business Central cost?
The good news is that you may already own part of this. Microsoft states that Business Central includes a licence to Power Automate for using your Business Central data in flows. In addition, Dynamics 365 licences include Power Apps use rights within the context of the licensed Dynamics 365 app. Note, though, that Microsoft classes the Business Central connector as Premium in Power Apps and Power Automate, so anyone outside those use rights needs a Premium licence.
| Licence | Typically for | Microsoft list price |
|---|---|---|
| Business Central Essentials | Finance, sales and purchasing users | US$80 per user/month, paid yearly |
| Business Central Premium | Essentials plus manufacturing and service | US$110 per user/month, paid yearly |
| Business Central Team Members | Light users who read data and approve workflows | US$8 per user/month, paid yearly |
| Power Apps Premium | App users without a qualifying Dynamics 365 licence | US$20 per user/month, paid yearly |
| Power Automate Premium | Flows outside an app or Dynamics 365 context | US$15 per user/month, paid yearly |
| Power Apps Developer Plan | Building and testing only | Free |
What else drives the total cost?
Beyond licences, several things drive the total cost:
- Who uses the app. First, count users per role. Staff with a Business Central licence and staff without one are licensed differently.
- Data you need. Generally, standard APIs are quick to use. Custom tables or fields need a custom API, which means developer time.
- Offline and photos. Similarly, working without signal needs extra design and testing on real devices.
- Approval rules. Likewise, each extra condition, approver level or exception adds build and test effort.
- Training and support. Short role-based training and someone to own the app after go-live.
Microsoft also notes that the Power Apps per app plan is no longer available to new customers through some purchasing channels since 2 January 2026. Therefore, confirm the right licence mix with your partner and the Power Platform Licensing Guide before you buy.
How long does Power Apps for Business Central take?
In short, it depends on scope. For instance, one approval flow on a standard document is a very different job from an offline field app with photos and custom data. That is why we fix the timeline after a free consultation. Here is what each phase involves:
| Phase | What happens | Who is involved |
|---|---|---|
| Scoping | First, pick one process, its users, and the data and approvals it needs | Process owner, finance, Mohila |
| Design | Sketch the screens, approval rules and licence plan | Key users, Mohila |
| Configuration | Build the canvas app and flows on the Business Central connector | Mohila |
| Data | Check APIs; add a custom API only if a table isn’t exposed | Mohila, developer if needed |
| Testing | Test in a sandbox and on real phones, online and offline | Key users, Mohila |
| Training | After that, short sessions for requesters and approvers | All users |
| Go-live | Publish, share, monitor flows and fix early issues | Admin, Mohila |
What speeds it up? Using standard APIs and Microsoft’s approval templates, one clear process owner, and clean vendor and item data. On the other hand, custom APIs, offline needs, many approval levels and late scope changes slow things down.
A practical example: a contractor’s material requests
This scenario is illustrative; it isn’t a real client. Imagine a contracting company with sites across Abu Dhabi and Dubai. At first, a site supervisor called the office, the buyer typed a purchase order, and the project manager approved it by replying “OK” on a chat app. Consequently, nobody could prove who approved what, and nothing was recorded in the ERP.
Now, instead, the supervisor opens a small request app on her phone, chooses the items, takes a photo of the shortage and taps Submit. Right after that, the purchase order appears in Business Central with the photo attached. Next, a Power Automate approval flow checks the amount: small orders go to the site manager, larger ones go to the project manager. Meanwhile, the project manager approves from his inbox between meetings. Finally, the buyer sees an approved order, and the approval is recorded in Business Central.
Best practices for Power Apps for Business Central
- Start with one process. To begin with, choose a single, painful, high-volume task, prove it, then grow.
- Use standard APIs first. Microsoft’s documentation says other tables need a custom API, so check what’s exposed before you design.
- Keep queries delegable. Microsoft recommends delegation so the data source does the filtering. By default only 500 records are processed locally, so set the limit to 1 while testing to catch problems early.
- Mind the connector limits. Specifically, Microsoft lists 300 API calls per connection every 60 seconds. Load data once into collections instead of calling Business Central for every row.
- Design offline on purpose. Keep in mind that offline works in the Power Apps mobile app only. For non-Dataverse data, SaveData and LoadData don’t resolve conflicts automatically, and devices typically have 30–70 MB of app memory.
- Go easy on photos. In particular, Microsoft advises keeping only the latest captured image in memory. Note the Camera control captures at 640 x 480; use Add picture for full resolution.
- Review licences before February 2027. Then use the Power Platform admin center licensing reports to see which users need a licence.
How Mohila can help
To start with, Mohila is a Microsoft Partner in Dubai that builds Power Apps solutions around Dynamics 365 Business Central. We start with business discovery, design the app and approval flow around your real process, connect it to your ERP, and then train your team and support it after go-live. If you are still planning your ERP, our implementation approach covers scoping and design through data migration, testing, training and go-live.
Talk to an Expert
Book a free 1-hour consultation with a certified consultant to map your first Business Central app and its licences.
Frequently asked questions
Often, yes, for users who already have a Business Central licence. Microsoft says Dynamics 365 licences include Power Apps use rights in the context of the licensed app. Users without a qualifying licence need one, such as Power Apps Premium.
Microsoft lists Power Apps Premium at US$20 per user/month and Power Automate Premium at US$15 per user/month, both paid yearly, as shown on 9 November 2026. Partner build work, training and support are extra and depend on scope.
It depends on scope. A single approval on a standard document is far quicker than an offline field app with custom data. Mohila fixes the timeline after a free consultation.
Canvas apps can run offline in the Power Apps mobile app on iOS, Android and Windows, but not in a web browser. For Business Central data, you use SaveData and LoadData and plan how changes sync.
Yes. Microsoft provides approval flow templates for purchase and sales documents, vendors, customers, items and general journals. Approvers can respond from an email with Approve and Reject buttons.
Sources
- Microsoft Learn: Integrating Business Central with Microsoft Power Platform
- Microsoft Learn: Connect to your Business Central data to build a business app using Power Apps
- Microsoft Learn: Create automated flows (Business Central)
- Microsoft Learn: Dynamics 365 Business Central connector reference
- Microsoft Learn: Power Apps licensing FAQs
- Microsoft Learn: Develop offline-capable canvas apps
- Microsoft: Power Apps pricing
- Microsoft: Business Central pricing




