Field guide · Small business · Microsoft Excel

Convert Excel to a web application your team can use

To convert Excel to a web application, match the route to the workbook. A calculator (inputs in, answer out) can be published as a web form by tools that run your formulas. A workbook several people update all day has to be split into records, rules and screens; on Microsoft 365 the shortest route is a SharePoint list plus a Power Apps app.

Published · Get the PDF

Which kind of workbook do you have?

Your workbookWhat it needsUsual route
One sheet of inputs that gives a price, quote or scoreThe same formulas behind a web formA tool that publishes the spreadsheet as a web form
A shared list of jobs, orders or requestsLogins, one record per row, a history of changesSharePoint list plus Power Apps
Linked sheets with approvals, status changes and reportsRules applied for every user, roles, reports on live dataA custom web app

Signs you have the second or third kind:

  • Two people edited at once and one lost their work.
  • You need to know who changed a number and when.
  • Some people should see only their own rows.
  • A step runs by macro on one person’s computer.

What has to change before the workbook can become an app?

  1. List the kinds of records. Jobs, customers, time entries. Each becomes its own table.
  2. Give every record an ID. A job or order number that never changes.
  3. One row per record, one column per fact. Remove merged cells, subtotal rows and typed-in totals.
  4. Format each block as a table. Use Home > Format as Table. Both the Lists import and Power Apps expect an Excel table.
  5. Write down every rule. Each formula, dropdown, conditional format and macro is a rule the app has to take over.
  6. Write down who does what. Who adds records, who approves, who only reads. If nobody has, map how the work runs first.
  7. Keep last month as a test. The app is right when it gives the same totals from the same inputs.

If only one person knows the rules, start with capturing a spreadsheet only one person understands.

Example. A job tracker with one tab per month becomes three tables: Jobs (job number, customer, status, crew, start date), Customers (customer ID, name, billing email) and Time entries (job number, person, date, hours). A filter on start date replaces the monthly tabs. The red highlight on late jobs becomes a rule: status is open and the start date has passed.

How do you build it with SharePoint and Power Apps?

Microsoft says “some Microsoft 365 licenses include limited Power Apps and Power Automate use rights,” meant for Microsoft 365 data and standard connectors. Dataverse tables and premium connectors make an app premium, so this route keeps the data in a SharePoint list.

1. Create the list from the table. In SharePoint, select Create > List, then From Excel. Select Upload file (or choose the file from OneDrive), pick the table, select Next, name the list and select Create. Microsoft says: “You can use tables with up to 5,000 rows to create a list.” An uploaded file is saved to the site’s Site Assets library, where other people can see the original data.

2. Check every column. Compare the list with the workbook column by column and fix any types that came in wrong.

3. Check version history is on. In the list, go to Settings > List settings > Versioning settings and select “Create a version each time you edit an item in the list.” Then ... next to an item, then Version history, shows earlier versions and lets you restore one.

4. Generate the app. Open the list and select Integrate > Power Apps > Create an app. Power Apps Studio opens with an app connected to the list. Select Preview the app, then save and publish it.

5. Test the basics. Create a record, edit it and confirm both in the list, then try saving with a required field blank. Microsoft’s advice: “Don’t treat a notification alone as proof that a data operation succeeded.”

6. Share it. In Power Apps, go to Apps, select the app, select Share and add people as User or Co-Owner. Microsoft says you “must also manage permissions for the data source,” so each person also needs access to the list.

Why not connect Power Apps straight to the workbook?

You can, with Start with data > Excel Online (Business). Microsoft’s connector page lists these limits:

  • Files up to 25 MB.
  • “Simultaneous file modifications made by other connectors, or manual edits are not supported.”
  • A file “may be locked for an update or delete up to 6 minutes since the last use of the connector.”
  • Rows the app adds, changes or deletes can take up to 30 seconds to show up.
  • Every action needs write access to the file, so every app user needs edit rights to the workbook.

Start with data > Upload file copies the workbook into a Dataverse table instead (files up to 5 GB). Dataverse makes the app premium.

What breaks, and how do you check it worked?

  • Views over 5,000 items. A list can hold up to 30 million items, but a view showing more than 5,000 can hit the list view threshold, which “can’t be changed” in SharePoint. Filter views on indexed columns such as status or year.
  • Searches that stop at row 500. When a formula can’t be handed to the data source (Microsoft calls this delegation), Power Apps checks only the first 500 records. You can raise that to 10,000 under Settings > General > Data row limit. Past the limit, the formula “doesn’t return record 501 or higher, even if it matches the criteria.” A yellow warning triangle in Power Apps Studio marks these formulas.
  • Macros. Microsoft says macros “do not run in a browser window,” so each one has to be rebuilt as a button or a flow.
  • Licensing checks from February 2027. Microsoft says that from February 2027, apps used in managed environments require users to have an appropriate premium license. If your admin uses managed environments, check licenses first.

To check it worked:

  1. Enter last month’s inputs into the app and compare every total and status with the workbook. Each difference is a bug or an unwritten rule.
  2. Have two people edit different records at once and confirm both changes saved.
  3. Open Version history on an edited record and confirm the earlier values are there.
  4. Run both for one full cycle, then make the workbook read-only.

What are your options?

OptionGood forWatch for
Publish the spreadsheet as a web form (tools such as SpreadsheetWeb)Calculators and quoting sheetsHow it handles logins, change history and macros
SharePoint list plus Power Apps, built yourselfOne or two kinds of record on Microsoft 365The 5,000-row import, the 500-row search limit, who maintains it
Power Apps on DataverseSeveral related tables and rolesA premium license for every user
Hire a freelancerA small app with clear rulesWho owns the app and data afterward
Bring in an outside team (Custom software)Workbooks with approvals, roles and reportsAgree in writing what “matches the workbook” means

For what a custom build involves, see how custom software gets built.

FAQ

Can we keep the workbook in SharePoint and edit it in the browser? Yes. Microsoft says changes save automatically in a browser window, but everyone can still change any cell and macros don’t run there.

How many rows can a SharePoint list hold? Up to 30 million items. Views that show more than 5,000 items at once need filters on indexed columns.

Does a Power Apps app run in a web browser? Yes. Microsoft says people you share it with can run it from Microsoft 365 in a browser, or in Power Apps Mobile on a phone.

Sources

Have one problem in mind?

Walk us through it on a free 30-minute call. Within two business days you get a one-page note on what we’d fix first, yours to keep.

Walk us through one problemFree 30-minute call.