If you're in the Office 365 ecosystem, you can do just that (in a sense). The MS Graph API has a workbook endpoint[1] that lets you do nifty stuff with Excel w

If you're in the Office 365 ecosystem, you can do just that (in a sense). The MS Graph API has a workbook endpoint[1] that lets you do nifty stuff with Excel workbooks hosted in OneDrive or Sharepoint. Pair that with non-persistent sessions[2], and you basically get an Excel workbook as a serverless runtime environment. If you structure the workbook with this type of use in mind, it works really handily. Create a non-persistent session, updated named items with the input values, run an explicit calculate on the workbook, and grab whatever result you're after (a table, named range, pivottable, chart graphics, etc), close the workbook session (or let it expire). If you need to keep the data around for historical reasons, you can follow the same process but copy the template workbook and create a persistent session against the copy, so the inputs/outputs are saved. You can also leverage Power Automate[3] (Microsoft's version of Zapier) to create an actual serverless function for your specific workflow that can accept your inputs, call the appropriate Graph endpoints for those steps, and return the output. Although the licensing gets funky, most people with an Office 365 license have some level of usage included already. It's definitely not a solution architecture you want to use for anything mission-critical or high-volume, but it's super handy for anything that's going to be Excel based anyway and you'd like to minimize the surface area for human error during the process. Also nifty for situations where a process/scenario/PoC is still being matured and developed in Excel, but you need to use it for production use cases. Create a stable input/output interface with a Power Automate workflow (or other serverless interface) that consumers can work against, then continue your Excel-based process development without disrupting them. At some point when it's stable/mature, port it over to code that maintains that same input/output structure and cut over the downstream consumers to the new endpoint. [1] https://docs.microsoft.com/en-us/graph/api/resources/excel https://docs.microsoft.com/en-us/graph/api/resources/excel [2] https://docs.microsoft.com/en-us/graph/api/workbook-createsession https://docs.microsoft.com/en-us/graph/api/workbook-createse... [3] https://powerautomate.microsoft.com/en-us/ https://powerautomate.microsoft.com/en-us/