web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
FastTrack for Dynamics 365 forum
Suggested Answer

Power Platform Architecture for Mobile Purchase Requests – Licensing Considerations

(1) ShareShare
ReportReport
Posted on by 4
As part of a Power Platform project, the objective is to implement a mobile purchase request management solution.
 
The application is based on a Power Apps Canvas app (with PCF), and two architectures are being considered.

In both cases, the application is primarily used to read data from Dynamics 365 Finance & Operations. The only planned write operation concerns the creation of an order in Dynamics 365.
 
The first scenario involves a Power Apps Canvas app that calls an Azure Function. The Azure Function then interacts with Dynamics 365 Finance & Operations (via API or MCP) as well as Dataverse, without a direct connection between Dataverse and D365.
 
The second scenario is based on a Power Apps Canvas app that writes to Dataverse, after which a Power Automate flow transfers the data to Dynamics 365 Finance & Operations, potentially with bi-directional synchronization.
 
In both architectures, what are the licensing implications for the Power Apps users?
I have the same question (0)
  • Suggested answer
    Vahid Ghafarpour Profile Picture
    12,228 Super User 2026 Season 1 on at
    This is a great architecture question because licensing in Power Platform is driven more by data sources and “who is being accessed directly” than by where logic sits.
    If access is only through Dataverse or built-in connectors, licensing is simpler but if access is via premium connectors (Dynamics 365 F&O, Azure Functions, custom APIs) → licensing becomes premium-heavy
  • MiMissel Profile Picture
    4 on at
    Thank you for your insights, this is very helpful.

    To confirm my understanding: if the architecture relies only on Dataverse and Power Automate (without any direct use of premium connectors such as Dynamics 365 Finance & Operations APIs or custom APIs from the Power Apps side), would it be possible to remain within standard Power Apps licensing?

    How should we consider the licensing aspect in a scenario where data is synchronized with Dynamics 365 Finance & Operations in the background? Would this have any impact on the required licenses for end users?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > FastTrack for Dynamics 365

#1
GyozoBarci Profile Picture

GyozoBarci 4

#1
MiMissel Profile Picture

MiMissel 4

#3
Mallesh Deshapaga Profile Picture

Mallesh Deshapaga 3

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans