News
In this article we will give you all the information you need to choose the best database for PowerApps. Your final PowerApp solution might be integrating to all kinds of third-party systems such as Facebook, Twitter, Salesforce etc to pull and push data. This article will be useful for people looking to start building a canvas PowerApp solution and a place to store the data from scratch. Scroll down for more information.
One of the key reasons businesses choose Power Apps is that it can be a very cost-effective way of developing software. However, if you rush into the project without considering where your data is going to be stored you could quickly find costs increasing. If cost is your primary reason for choosing Power Apps, then selecting to store your data in Microsoft Excel spreadsheet or SharePoint Lists could be the best option for you as these options are often included in the majority of Microsoft 365 licenses you likely already have.
Another unique selling point of Power Apps is how quickly you can spin up a mobile friendly app. However, often not factored into this time is how long it takes to setup the backend database for storing the relevant data for the Power App. If you are looking to create proof of concept app to pilot quickly then setting up a new SQL server might take too much time. So, you might choose to set this up in Dataverse as it will be a much quicker setup process. Choosing Excel Spreadsheets or SharePoint Lists would also provide a very quick option for storing your data. This would be dependent on the amount of data you need to store.
There are a number of issues that can be caused by not correctly estimating how much data your Power App will be generating. This could lead to delegation issues in your Power Apps, issues with SharePoint views, load times opening Excel documents and so much more. You need to consider how many columns will be in your database and how much data will be submitted over the lifetime of the Power App. If you are expecting thousands of rows of data, then an Excel Spreadsheet would be sufficient. If you are expecting up to a hundred thousand rows of data, then a SharePoint List would be the chosen option. If you need more than that you would look to use Microsoft Dataverse.
Knowing how many people will be using the Power App will help scope which database you choose for your solution. If it will just be a handful of users in a small Team that will be using the Power App, then a Microsoft Excel Spreadsheet can be used. However, this option would not scale well if the Power App was then shared with a wider audience of users. For small to medium sized organisations that want to build solutions that can scale to the wider group of users then selecting Microsoft Lists (SharePoint Lists) would be the best option. If you are building an enterprise solution, then choosing Dataverse should be considered.
It is worth considering not only how and who will be supporting the Power App, but also the database that is supporting it in the background. If you do not have the IT resource or PowerApps Developers to support a new SQL server instance, then this might not be the best option. Using Microsoft Lists (SharePoint Lists) as your database for the Power App will make it much easier for non-technical employees to be able to maintain the data.
Looking for the best Database for Power Apps? Let us Transform Your Data with Microsoft PowerApps Databases!
Unlock the full potential of your business data with Microsoft PowerApps. Create flexible and scalable databases that streamline operations and enhance decision making. Whether you’re building custom apps or optimising workflows, PowerApps databases provide the foundation for seamless data integration and real time insights.
Watch the video (opens in a new tab)
In this article, we will give you all the information you need to choose the best database for PowerApps. We will also introduce you to the various PowerApps data sources, and how they can make your business processes more efficient.
With a functional database that is connected to all of your crucial data sources, everything your businesses need for a seamless operation is at your fingertips. Your final PowerApp solution might integrate all kinds of third-party data sources. This includes Facebook, Twitter, Salesforce and more.
This article will be useful for people looking to start building a canvas PowerApp solution and a place to store the data from scratch. Scroll down for more information.
PowerApps data sources provide your apps with the information that they need to function effectively. These banks of data can be stored in the cloud, allowing you to access them from anywhere in the world.
One example of a PowerApp data source is a table created in Microsoft Excel. The table can be stored in OneDrive for Business, or any other cloud storage, and connected to your PowerApps. You need specific connectors to communicate with the data source. Fortunately, Valto can connect you to many useful services.
The services that we can provide connectors for include SharePoint, Salesforce, SQL server and all the Office 365 products. Talk to Valto today to find out how we can enhance your business efficiency by connecting your PowerApps to useful data sources.
Data sources for PowerApps are stored in the cloud, or locally stored in a specific app. The most common form of data sources used for PowerApps are tables. By connecting to cloud and local data sources, you can read, amend, and reformat tables across all of your apps, with total ease and control. Some of the most common PowerApps data sources include:
It isn’t just tabulated data that PowerApps can connect to. Valto can also link your PowerApps to a host of other useful features. This includes calendars, emails and social media accounts. With your notifications and data easily available to you, everything you need is at your fingertips.
When using PowerApps, all of your data will be stored in the cloud. This makes it easy to access your apps and information from anywhere in the world. The volume of data required by businesses has increased drastically in recent years. As a result, Microsoft has introduced the “Dataverse”.
The Dataverse gives PowerApps users access to three different storage areas, one for databases, one for logs and one for files. The amount of storage you will receive will vary depending on the PowerApps subscription that you pay for.
On a PowerApps per-user plan, you will typically receive 10 GB of database capacity, 20 GB of file capacity, and 2 GB of log capacity. Then, each additional user added to your subscription will come with extra Dataverse storage capacity.
However, if you purchased your PowerApps subscription before April 2019, you will still be using their legacy cloud storage model. This gives you a single data capacity entitlement, as opposed to the three storage segments provided by the Dataverse cloud model.
Another question Valto are often asked by our clients when considering database for PowerApps is if a Power App solution can be used offline. If it is a Canvas Power Apps solution you can control how the data is stored locally and then pushed into a cloud data source once the device reconnects to an internet connection. Microsoft PowerApps can be used offline by leveraging local device storage, how well this works will depend on the specification of the device that you are using to run the Power Apps solution. Offline capabilities of Microsoft Power Apps allows users to continue working without an internet connection. This is made possible through the use of the LoadData and SaveData functions with Canvas PowerApps. Allowing Power Apps developers to cache data locally on the device, enabling seamless access to critical information. It is even possible to do automated checks to see if the device is still offline. We often recommend visually displaying that to the end user with a visual icon. Once the connection is restored, the app can synchronize with the cloud database, and change the connectivity icon to show the Power Apps user the app is now technically back online.
A common mistake that is made when embarking on a PowerApps project is to focus on the user interface design before considering where the data will be stored.
First agree where the data is going to be stored and what columns of data will be required before you start designing your Power App interface.
There are multiple factors to consider to help you choose the best database for PowerApps. As part of your initial project meeting to discuss PowerApps ask your Team the following questions:
There are many different types of databases available on the market. We will not be discussing any of the third-party databases such as MySQL, Oracle, IBM Db2, SAP or AWS (Amazon Relational Database Service) as these are typically not used in combination with PowerApps.
Below we have listed the most commonly used Microsoft products to store data with Canvas PowerApps.
A Microsoft Excel Spreadsheet hosted in either SharePoint Online or a OneDrive for Business is a viable option for small teams to store data. Using Excel would be the smallest scaled database.
This would be sufficient for personal use Power Apps or if you only plan to store up to a few thousand rows of data. Main benefits of this option include being quick to setup and not requiring an Office 365 Admin to setup an area to store your data.
The most commonly chosen place to store data that we recommend is within Microsoft Lists. These Lists are essentially stored on SharePoint sites and are great for small (SMB) organisations to store up to one hundred thousand rows of data.
Using Microsoft Lists within Office 365 as a DataSource is also a chosen option as SharePoint Online is included within the majority of Microsoft 365 licenses, meaning there is no additional cost.
If you need to store hundreds of thousands or more rows of data to use with your PowerApp, then Microsoft SQL could be considered.
However, it will have a few down sides including additional premium licenses that are required for end users to access SQL data.
Your PowerApp might be being built to interface with an existing SQL database. However, it can be a very costly process to setup and support a new Microsoft SQL environment for your new PowerApp.
So, if you require a database to store large volumes of data then consider Dataverse (Formerly Common Data Service) instead.
Dataverse is the best option if you need to store hundreds of thousands of rows of data.
Choose Dataverse if you are looking for a database that will scale to enterprise levels over time.
The key difference of Dataverse is that it is a relational database just like Microsoft SQL compared with the other options. This will allow you to form relationships and lookups to other tables of data.
The downside of this option is that it will require premium licenses which can be quite costly.
PowerApps Whitepaper
I hope you found this content useful, if you are interested in getting some assistance with Power Apps, please feel free to contact me with any questions using our contact us form.
If you are interested in PowerApps then please download our free PowerApps white paper.
“We work with organisations across many sectors of different shapes and sizes from 10 to 100,000 employees.”
Organisations are increasingly rethinking their intranet platforms. As Microsoft 365 evolves, many are moving back to SharePoint to reduce cost, simplify governance, integrate with Teams and prepare for AI with Copilot.
15 May 2026
All NEW Microsoft AI tools announced at Microsoft Build 2025 . Discover Microsoft CEO's AI vision to scale businesses with AI Chatbot Agents.
23 May 2025
Struggling with document versioning, policy visibility or outdated files? Learn how Valto’s SharePoint-based Controlled Documents Solution solves the most common document control challenges.
7 May 2025
