
Dear @山本 悦崇,
Thank you for posting your question in the Microsoft Q&A forum. Migrating your Access back-end to Dataverse is a smart move, and I’m happy to clarify the licensing options to help you choose the most suitable and cost-effective path.
- If you won’t use any Power App, the Power Apps Per App license won’t apply, it must be tied to a specific app.
- The compliant choice for Access-only usage is Power Apps Per User (Premium).
- If you want to minimize cost, you can use Per App licenses only if you publish and assign a minimal Power App.
Licensing options explained:
Option A: Power Apps Per User (Premium)
- Fully compliant for Access-only usage.
- Each user can access Dataverse via Access without needing to run a Power App.
- Adds pooled capacity: 250MB DB + 2GB file per user.
- Cost: ~$20/user/month.
Option B: Power Apps Per App (Lower Cost)
- Requires at least one Power App (canvas or model-driven) published and assigned to users.
- Users can then use Access linked tables in parallel.
- Adds pooled capacity: 50MB DB + 400MB file per user.
- Cost: ~$5/user/month.
- Important: Microsoft does not explicitly confirm that Per App licenses cover Access-only usage. Many organizations use this pattern, but Per User is safer for compliance.
Relevant Microsoft documentation on the cost of standard Dataverse: Power Platform licensing FAQs - Power Platform | Microsoft Learn
Option C: Dataverse for Teams
- Included in many Microsoft 365 plans.
- Not suitable for Access desktop usage outside Teams.
- Only valid if all data access happens inside Teams apps.
Quick cost/fit comparison for your case (10 users, ~50 MB DB)
Choice | Licensing fit with “Access-only” | Typical list price* | Dataverse DB capacity added |
---|---|---|---|
Per user (Premium) | Fully compliant | $20/user/mo (lower at volume) | 250 MB/user → 2.5 GB total + default 10 GB |
Per app | Requires at least one app to assign/run | $5/user/app/mo | 50 MB/user → 0.5 GB total + default 10 GB |
Dataverse for Teams | Not for Access desktop (outside Teams) | Included with many M365 plans | Teams‑scoped; typically, 2 GB per team env |
For full details, please review the official Microsoft documentation on this topic:
- Import or link to Dataverse tables - Microsoft Support
- About the Microsoft Dataverse for Teams environment - Power Platform | Microsoft Learn
For your scenario (10 users, 50MB DB):
- If you don’t plan to build any app, go with Per User licenses.
- If you’re open to publishing a minimal Power App, Per App licenses may reduce cost, just ensure each user is assigned to that app.
I hope this provides the clarity you need to move forward with your project.
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.