Having said that, I love that Excel has democratized app-building and made it easier for people to solve their own problems. In terms of alternatives, I think it's more about the UI and mental model that people have when using Excel, not necessarily the functionality. There may be 1-to-1 competitors in terms of functionality, but in terms of UX, Excel is sort of king.
If it were just about any other group than that company's "finance department" that so deeply wanted "just tightly wrap Excel in a web UI and leave the key computations as Excel formulas we can continue to edit in Excel because all we want to understand is Excel" project would probably have been rightfully laughed out of the room. Finance has the keys to a lot of companies and like keeping those keys for comfort in Excel.
If the finance team suggested you have to write all of your code in C using Emacs would you be OK with that?
But to answer the question, that is where I finished. We weren't "okay with it" that the finance team insisted on a C# to Excel files in SharePoint/OneDrive via Microsoft Graph turducken. We lived with it because the finance team had enough of the metaphorical keys to the car to be deeply in the driver's seat of that project. Sometimes you just have to grit your teeth and deliver what the customer wants.