This chapter compares Microsoft Access and Power Apps, two tools for building data-driven applications but with vastly different architectures and use cases. For the MS-900 exam, you need to understand when to use each, their licensing, and their integration with Microsoft 365. This topic appears in roughly 5-8% of exam questions, often in scenario-based items asking which tool to recommend. We’ll cover core differences, step-by-step creation processes, real-world deployment scenarios, and common exam traps.
Jump to a section
Imagine you want to build a custom house. Microsoft Access is like a complete blueprint and construction kit: it includes a detailed floor plan (the database schema), a set of standard room templates (tables, forms, reports), and all the tools (queries, macros) needed to build and furnish the house yourself. You can directly modify the blueprint, add rooms, and change the structure. However, the house is built on your own land—you control everything, but it’s only accessible to people who come to your property. Power Apps, on the other hand, is a workshop that lets you design and build custom furniture (apps) that can be shipped to any house—on-premises, in the cloud, or even to other workshops (like SharePoint, SQL Server, or Excel). You don’t modify the house itself; you build modular pieces that connect to the house’s rooms (data sources) through standard connectors. The workshop provides pre-built components (controls, templates) but you assemble them using a visual drag-and-drop interface—no need to cut wood yourself. The key difference: Access is a self-contained database with a built-in app layer; Power Apps is a separate app layer that can connect to many databases, including Access. For the exam, think of Access as a single-family home, Power Apps as a modular furniture kit that can furnish any home.
What Are Microsoft Access and Power Apps?
Microsoft Access is a desktop relational database management system (RDBMS) bundled with Microsoft 365 Business and Enterprise plans (and available standalone). It combines a database engine (Access Database Engine, ACE) with a graphical user interface for creating tables, queries, forms, reports, and macros. Access stores data in a single .accdb file (or .mdb for older versions) and supports up to 2 GB of data per file (excluding system objects and linked tables). It is primarily a client-server database where the database file resides on a local machine or network share, shared among users.
Power Apps is a low-code application development platform as part of the Microsoft Power Platform (alongside Power Automate, Power BI, and Power Virtual Agents). It allows users to build custom apps that run on web browsers, mobile devices, or within Microsoft Teams. Power Apps connects to over 200 data sources, including SharePoint, SQL Server, Dataverse (formerly Common Data Service), Excel, and yes, Access databases. Apps are built using a drag-and-drop canvas and formulas (similar to Excel formulas) and do not require traditional programming. Power Apps uses connectors to interface with data; each connector has specific capabilities and limits.
How They Work Internally
Access Architecture: - Database Engine: ACE (Access Database Engine) is a Jet-based engine that processes SQL queries, manages record locking, and enforces referential integrity. It supports multi-user access through file-level locking (LDB files) and page-level locking. - Data Storage: All objects (tables, queries, forms, reports, macros, modules) are stored in a single .accdb file. Tables can be local or linked to external sources (e.g., SQL Server, SharePoint lists). - Application Layer: Forms and reports are designed using a visual designer. VBA (Visual Basic for Applications) provides scripting capabilities for complex logic. - Deployment: Typically, the .accdb file is placed on a shared network drive. Each user runs the Access client application (installed locally) to open the file. Concurrency is managed through record locking; maximum practical concurrent users is about 20-25 (higher with SQL Server backend).
Power Apps Architecture: - Canvas Apps: Built using the Power Apps Studio (web or desktop). Apps consist of screens, controls (buttons, galleries, forms), and formulas that bind controls to data sources. Formulas are written in Power Fx, a low-code language that is declarative and reactive. - Model-Driven Apps: Built on Dataverse, using a metadata-driven architecture. The app automatically generates forms, views, and dashboards based on the data model. - Connectors: Power Apps uses connectors to communicate with data sources. Each connector has a set of actions and triggers. For example, the SQL Server connector can execute stored procedures, while the SharePoint connector can read/write list items. - Hosting: Apps are hosted in the Microsoft cloud (Azure). Users access them via web browser, mobile app (iOS/Android), or embedded in Teams. No client installation is required. - Licensing: Power Apps requires per-user or per-app licenses. Standalone plans start at $5/user/month (Power Apps per user plan) or $10/app/month (per app plan). Power Apps can also be included in Microsoft 365 plans (e.g., E3/E5 include limited use rights for customizing SharePoint and Teams).
Key Differences in Capabilities
Data Capacity: Access has a 2 GB per file limit (including all objects). Power Apps can handle much larger datasets because it relies on backend data sources (e.g., SQL Server, Dataverse) that can scale to terabytes.
Concurrency: Access supports limited concurrent users (20-25) due to file-level locking. Power Apps scales to hundreds or thousands of users because it uses server-side data sources with row-level locking.
Mobility: Access apps are desktop-only (Windows). Power Apps apps run on any device with a browser or mobile app.
Integration: Access integrates tightly with Microsoft 365 (Export to SharePoint, link to Outlook). Power Apps integrates with the entire Power Platform, Dynamics 365, and hundreds of third-party services via connectors.
Customization: Access offers deep customization via VBA and macros. Power Apps uses Power Fx and has a steeper learning curve for complex logic but is more accessible for non-developers.
Deployment: Access requires distributing the .accdb file and ensuring all users have Access installed. Power Apps is centrally managed via the Power Platform admin center; updates are published instantly to all users.
Security: Access security is limited to user-level permissions on the file system and optional database passwords. Power Apps leverages Azure Active Directory (now Entra ID) for authentication and role-based access control (RBAC) via Dataverse.
When to Use Each (Exam Focus)
Use Microsoft Access when: - You need a standalone desktop database for a small team (under 20 users). - The application is not web-based and does not require mobile access. - You need to quickly create a database with forms and reports without coding. - The data volume is under 2 GB. - The user base already has Access licenses (included in many M365 plans).
Use Power Apps when: - You need a web or mobile app that can be accessed from anywhere. - You need to connect to multiple data sources (e.g., SQL, SharePoint, Excel online). - You anticipate scaling to hundreds or thousands of users. - You want to leverage AI Builder, Power Automate, or Power BI integration. - You need to embed the app in Teams or SharePoint. - You want to avoid client installation (zero-footprint deployment).
Licensing and Cost Considerations
Access: Included in Microsoft 365 Business Standard, Business Premium, Enterprise E3/E5, and Access 2019/2021 standalone. No additional cost if the user already has one of these plans.
Power Apps: Included with Microsoft 365 E3/E5, but only for limited use (customizing SharePoint and Teams). Full usage requires a Power Apps per user or per app license ($5-$10/user/month). For Dataverse, additional storage costs apply.
Integration Between Access and Power Apps
You can use Power Apps to build a front-end for an Access database that is stored in SharePoint (via linked tables) or use the Access connector (currently in preview) to connect directly to an .accdb file. However, for production scenarios, it is recommended to migrate Access data to Dataverse or SQL Server for better performance and scalability.
Exam Traps
Trap 1: Thinking Power Apps is a database. Power Apps is an app platform; it does not store data itself (unless using Dataverse). It connects to data sources.
Trap 2: Assuming Access is web-based. Access web apps (Access Services) were deprecated and removed; Access is now desktop-only.
Trap 3: Believing Power Apps requires coding. Power Apps uses low-code (Power Fx), no traditional coding.
Trap 4: Confusing Power Apps with Power Automate. Power Automate is for workflow automation; Power Apps is for building apps.
Trap 5: Overlooking the 2 GB limit for Access. Many questions test this specific number.
Default Values and Limits
Access file size limit: 2 GB (excluding system objects).
Access concurrent users: 20-25 recommended maximum.
Power Apps per user plan: $5/user/month.
Power Apps per app plan: $10/app/month (up to 2 apps, unlimited users).
Power Apps run limits: 600 API requests per user per day (per app plan) or 2000 (per user plan).
Dataverse storage: 10 GB base for each tenant, additional storage can be purchased.
Define the Business Requirement
Start by identifying the core problem: number of users, data volume, mobile need, and existing licenses. For example, if you have 10 users needing a desktop inventory system, Access might be sufficient. If you need a mobile sales app for 200 reps connecting to SQL Server, Power Apps is the choice. Document the data sources and required integrations.
Choose the Right Tool
Based on the requirement, decide between Access or Power Apps. Consider factors like concurrency, scalability, and deployment. If the decision is Access, proceed to design the database schema (tables, relationships). If Power Apps, choose the app type (canvas or model-driven) and select the data source (e.g., Dataverse, SharePoint).
Design the Data Structure
For Access: Create tables in the .accdb file, define primary keys, relationships, and indexes. Use the Table Designer to set field types (Text, Number, Date/Time, etc.) and validation rules. For Power Apps: If using Dataverse, create entities (tables) and columns in the Power Platform maker portal. If using SharePoint, create lists with appropriate columns. Ensure normalization to avoid data redundancy.
Build the User Interface
Access: Use the Form Designer to build forms by dragging fields onto the canvas. Add buttons, list boxes, and subforms. Customize with VBA if needed. Power Apps: In Power Apps Studio, add screens and controls (labels, text inputs, galleries). Bind controls to data sources using formulas like `Filter(Accounts, Status = "Active")`. Use the template gallery for quick starts.
Add Logic and Automation
Access: Use macros or VBA to automate tasks (e.g., sending emails, validating data). Macros are simpler; VBA offers more power. Power Apps: Use Power Fx formulas for logic (e.g., `If(IsBlank(TextInput1.Text), Notify("Field required"))`). For advanced automation, integrate Power Automate flows (e.g., send approval email when a record is created).
Test and Deploy
Access: Test the database on a local machine, then copy the .accdb file to a shared network location. Ensure all users have Access installed and appropriate file permissions. Power Apps: Use the 'Save' and 'Publish' buttons in Power Apps Studio. Share the app with users via email or embed in Teams. Assign licenses if needed. Monitor usage via the Power Platform admin center.
Scenario 1: Small Business Inventory Management
A local bakery with 5 employees needs a simple inventory system to track ingredients and finished goods. They have Microsoft 365 Business Basic licenses, which include Access (desktop) but not Power Apps per user licenses. The owner creates an Access database with tables for ingredients, products, and orders. Forms allow staff to update stock levels; reports show low-stock alerts. The .accdb file is stored on a shared network drive. Challenges: occasional file corruption due to simultaneous access, and the owner must manually backup the file. This works well for their scale, but if they grow to 30 users, they would need to migrate to a server-based solution like Power Apps with SQL Server.
Scenario 2: Enterprise Field Service App
A multinational company with 500 field technicians needs a mobile app to log service calls, capture signatures, and sync with an on-premises SQL Server database. They choose Power Apps (canvas app) because it provides mobile offline capability (via Dataverse or SQL connector with offline sync). The app connects to SQL Server using the on-premises data gateway. Technicians use the Power Apps mobile app on their company iPhones. The app includes a gallery of pending jobs, a form to update job status, and a camera control to upload photos. Power Automate workflows send email notifications to managers when a job is completed. The solution scales to hundreds of users with no performance issues. The IT department manages the app centrally, pushes updates, and monitors usage. The total cost includes Power Apps per user licenses ($5/user/month) and an on-premises data gateway (free).
Scenario 3: Migration from Access to Power Apps
A non-profit organization used an Access database for donor management for years. As they grew to 50 users, they experienced performance issues and file corruption. They decided to migrate to Power Apps with Dataverse. The migration involved exporting Access tables to Excel, importing them into Dataverse, and rebuilding forms in Power Apps. The new solution provides web access, role-based security, and integration with their fundraising platform. The migration took 2 months and required training for staff. The result: no more file corruption, better data security, and the ability to access donor records from any device. This scenario is common on the exam where they ask about legacy Access modernization.
The MS-900 exam tests your ability to differentiate between Microsoft Access and Power Apps under objective 2.4 (Describe collaboration and productivity solutions of Microsoft 365). Specifically, you must understand:
The core functionality of each tool.
Licensing requirements.
When to recommend each based on scenario.
Common wrong answers: 1. "Power Apps is a database." This is false. Power Apps is an app platform that connects to data sources; it does not store data itself (except Dataverse, which is a separate component). 2. "Access can be used to build web apps." Access Services was deprecated in 2017 and removed in 2018. Access is now strictly desktop-only. The exam may present a scenario requiring a web app and expect you to choose Power Apps. 3. "Power Apps requires coding." Power Apps is low-code; it uses Power Fx formulas, not traditional programming languages like C# or JavaScript. The exam tests this distinction. 4. "Access is included in all Microsoft 365 plans." Access is included in Business Standard, Business Premium, Enterprise E3/E5, and Education plans, but not in Business Basic or Enterprise E1. Know the specific plans.
Specific numbers and terms that appear verbatim:
Access file size limit: 2 GB.
Power Apps per user license: $5/user/month.
Power Apps per app license: $10/app/month (up to 2 apps, unlimited users).
Power Apps included in M365 E3/E5 only for customizing SharePoint and Teams.
Dataverse storage: 10 GB base.
Edge cases:
If a scenario mentions needing a database for a single user with complex reporting, Access is often the best answer.
If a scenario requires offline mobile capability, Power Apps with Dataverse or SQL connector (offline sync) is the answer.
If a scenario mentions integrating with Power Automate or Power BI, Power Apps is the likely choice.
How to eliminate wrong answers:
If the question mentions "web browser" or "mobile device," eliminate Access.
If the question mentions "large number of users" (e.g., 100+), eliminate Access.
If the question mentions "storing data in a file," think Access.
If the question mentions "connecting to multiple data sources," think Power Apps.
Always check licensing: if the organization only has Microsoft 365 Business Basic, they do not have Access, so Power Apps might be the only option (but they would need additional licenses).
Access is a desktop database; Power Apps is a low-code app platform.
Access file size limit is 2 GB; Power Apps relies on backend data storage.
Access supports limited concurrent users (20-25); Power Apps scales to thousands.
Power Apps uses connectors to connect to over 200 data sources.
Access is included in M365 Business Standard, Premium, E3/E5; not in E1 or Business Basic.
Power Apps requires a per-user ($5/user/month) or per-app ($10/app/month) license.
Power Apps can embed in Teams and SharePoint; Access cannot.
For mobile and web apps, choose Power Apps; for simple desktop DB, choose Access.
These come up on the exam all the time. Here's how to tell them apart.
Microsoft Access
Desktop-only application (Windows).
Data stored in a single .accdb file (2 GB limit).
Supports up to ~20-25 concurrent users.
Included in many M365 plans (Business Standard, E3, etc.).
Deep customization via VBA and macros.
Power Apps
Web and mobile apps (cross-platform).
Connects to external data sources (SQL, SharePoint, etc.).
Scales to hundreds/thousands of users.
Requires separate Power Apps license (or limited use via M365).
Low-code with Power Fx formulas.
Mistake
Power Apps is a database like Access.
Correct
Power Apps is an app platform that connects to various data sources; it does not store data itself. Dataverse is a data storage option but is separate from Power Apps.
Mistake
Access can be used to build web apps.
Correct
Access web apps were deprecated in 2017 and removed. Access is now desktop-only. For web apps, use Power Apps.
Mistake
Power Apps requires traditional programming skills.
Correct
Power Apps uses Power Fx, a low-code language similar to Excel formulas. No traditional coding (C#, JavaScript) is required.
Mistake
Access is included in all Microsoft 365 plans.
Correct
Access is included in Business Standard, Business Premium, Enterprise E3/E5, and Education plans. It is not included in Business Basic or Enterprise E1.
Mistake
Power Apps can handle unlimited data without additional cost.
Correct
Power Apps itself does not store data; data storage costs depend on the backend (e.g., Dataverse storage is 10 GB base; additional storage costs extra).
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
No, Power Apps is not a database. It is an app platform that connects to data sources like Dataverse, SharePoint, SQL Server, or Excel. You can create a Dataverse database within the Power Platform, but that is separate from Power Apps. For the exam, remember that Power Apps itself does not store data.
Yes, Microsoft Access is still supported and included in certain Microsoft 365 plans. However, Access web apps (Access Services) were deprecated and removed. The desktop version remains active and is updated regularly.
The maximum file size for an Access database (.accdb) is 2 GB. This includes all objects except linked tables and system objects. The exam may test this specific number.
Microsoft 365 E5 includes limited use rights for Power Apps to customize SharePoint and Teams. For full Power Apps capabilities (e.g., connecting to Dataverse, SQL Server), you need a Power Apps per user or per app license.
Yes, you can migrate data from Access to Dataverse or SQL Server and then build a Power Apps front-end. However, you cannot directly use the Access file as a data source for Power Apps (the Access connector is in preview but not production-ready).
Power Apps supports offline capability when using Dataverse or certain connectors (e.g., SQL connector with offline sync). Access is desktop-only and cannot run on mobile devices offline.
Power Fx is the low-code language used in Power Apps. It is similar to Excel formulas and is used to bind controls to data sources, add logic, and create expressions. It is not a traditional programming language.
You've just covered Microsoft Access and Power Apps Comparison — now see how well it sticks with free MS-900 practice questions. Full explanations included, no account needed.
Done with this chapter?