Supported Excel formulas and functions

Every vendor in this category says it supports Excel formulas. Below is the count, measured against Microsoft's own function categories, so you can check it rather than take our word for it. Of the 512 functions Microsoft lists across all 13 categories, Hub supports 497, and coverage is complete in 8 categories.

Coverage by category

Denominators taken from Microsoft, Excel functions (by category), revised 7 January 2026, which applies to Excel for Microsoft 365, Excel 2024, 2021, 2019, 2016. Microsoft's alphabetical function index is longer than the sum of its category pages, because some Microsoft 365 only functions carry no category assignment. Function counts also vary between Excel versions and update channels, so the ratio is stated against that specific reference rather than against "Excel" in general.

Uncategorised functions

Hub supports 501 functions. The table above accounts for 497 of them. The remaining 4 are supported but Microsoft files them under no category at all, so there is no denominator to score them against:

497 + 4 = 501. The three regular expression functions are Microsoft 365 only and carry no category assignment in Microsoft's documentation, so there is nothing to measure them against. Hub supports all three, which means real coverage is marginally better than the table shows.

What is not supported, and why

Beyond individual functions

Workbook features, as opposed to formulas, that do not carry over: macros and VBA, third-party add-ins, pivot tables, conditional formatting, slicers, filters, group and ungroup outlining, subtotals, external workbook references, ActiveX controls, and some cell formats including custom number formats, background fill effects, background patterns, and any text orientation other than horizontal.

A macro-enabled workbook still uploads and calculates; it runs as though macros were switched off. The FAQ below sets out how interface and calculation macros are each handled.

Not being supported out of the box does not mean a dead end. Much of what these features do, including conditional display and formatting, filtering, grouping behaviour, and interactive controls, can be reproduced with the Scripts module, which runs JavaScript against the application at runtime and ships with a library of ready-made snippets. Scripts require some programming and are available on private Hub servers and Pro workspace licences.

Current with recent Excel releases

The function set tracks Microsoft's recent additions rather than stopping at a legacy baseline. Supported as of build 26.6.0:

Beyond formulas

Models often depend on features that are not worksheet functions. These are built-in event types in the App Designer, so a model that relies on them does not need restructuring:

Plan note. Solver and Goal Seek are documented as not available on Public Cloud accounts. Confirm your plan covers them.

The complete function list

This page is the summary. Every supported function is listed individually with its description in the Hub documentation, which is generated from the same source as the counts above. To check a workbook against it, download the full list as a CSV and compare it with the functions your model uses. No form to fill in.

The fastest way to know whether your model will run is to check it. Send the file and we will run the comparison against the supported list and tell you what, if anything, needs attention.

Frequently asked questions

Do I need to rewrite my formulas?

No. Hub reads the .xlsx file and executes the formulas as written. There is no porting step and no second copy of the logic to keep in sync.

What happens when I update the model?

You upload the revised workbook and the application uses the new logic. The calculation model stays in Excel, where the people who own it maintain it.

Are macros and VBA supported?

It depends on what the macros do. The VBA code itself does not execute, but the workbook still uploads and calculates. It runs as though macros were switched off. So the question is never whether the file works, only what the macros were doing. In practice they fall into two groups.

Interface macros, meaning showing and hiding sections, navigation, validation, formatting, and button behaviour, usually need no conversion at all. The App Designer provides those behaviours natively, so the macro is replaced by configuration rather than rewritten. See Controlling User Interface with VBA.

Calculation macros do need converting, and the two common cases are documented end to end. VBA user-defined functions convert to LAMBDA, which Hub supports along with the full set of lambda helpers: see Converting VBA-based UDFs to LAMBDA functions, which covers simple formulas, optional arguments, and loops rewritten as recursion. Iterative and Monte Carlo routines map onto the built-in Simulation event rather than code: see Monte Carlo simulations.

For behaviour that neither approach covers, the Scripts module runs JavaScript at defined points in the application lifecycle, using hooks that fire on events and actions that drive the runtime. It is an advanced feature and available on private Hub servers and Pro workspace licences. Heavier logic can also be rebuilt in C# as a Custom Application.

The fastest way to find out where your own macros land is to send us the workbook. Much of what looks like a blocker turns out to be interface code that the platform already handles.

Which Excel version are the totals measured against?

Microsoft, Excel functions (by category), revised 7 January 2026, which applies to Excel for Microsoft 365, Excel 2024, 2021, 2019, 2016. Microsoft adds functions over time and counts differ between update channels, so the comparison is pinned to that reference rather than to "Excel" generally.

How do I check my own workbook?

Download the CSV and compare it against the functions your model uses, or send us the file and we will run the comparison.