Episode Details

You know those times when Power Apps just… hit a wall? Maybe a workflow stumbles, or Dataverse can’t quite crunch it. What if I told you there’s a way to break through with almost unlimited processing power—without leaving the Microsoft ecosystem? Today, we’re unpacking how Azure Functions and Power Apps can work together so your apps are never boxed in by low-code limits.Stick around, because we’re not just patching cracks; we’re building a system where every part does what it does best—securely and at scale.Why Fusion? What Power Apps and Azure Functions Each Bring to the TableIf you’ve ever found yourself hitting the upper limits of what Power Apps can handle, you’re not alone. Anyone who’s put together even a modest business app in Power Apps has noticed there’s a ceiling. You can build forms, automate simple workflows, drop in a gallery, maybe connect a few lists or tables in Dataverse, and for many departments, that’s the magic—apps without a developer in sight. But run into anything more demanding, and you’ll see where things unravel. For instance, you want to run a calculation using a custom algorithm built by your analytics team. Power Apps isn’t designed for that sort of heavy lifting. Try to work around it, and you’re suddenly stuck staring at delegation warnings, capped data set queries, or screens that crawl when someone tries to crunch numbers across thousands of records.Things only get more interesting once you venture outside the Microsoft 365 ecosystem. Maybe marketing wants to pull in risk scores from a non-Microsoft API or legal needs to validate data against an external government service. Power Apps, left alone, just isn’t set up for these leaps. Out-of-the-box connectors can take you part of the way, but sooner or later you need something more direct. That’s right about when the suggestion hits: “Why not use Azure Functions?”On the surface, Azure Functions sounds like cheating the system—a way to slip in C# or JavaScript and suddenly let your Power Apps do things Microsoft never planned for. Need to check inventory in a legacy ERP? No need to build an entire back-end. Just have Power Apps call a custom function, get back what you need, and move on. The biggest appeal is you don’t need to overhaul your solution; Azure Functions bolt onto your existing app, letting you layer in power as your requirements evolve. The integration isn’t perfect—but it means you don’t need to throw out weeks of low-code work just because you need a bit of real coding under the hood.Of course, it's worth asking: does this always make sense? Not everyone buys into the Azure Functions hype. Some architects will tell you that the second you start peppering Azure Functions into a low-code project, you’re probably just hiding complexity instead of managing it. Every new function is another endpoint to secure, another piece to document, and another spot where something can break. There are plenty in the Power Platform community who’ll point out cases where adding functions only made support harder, not easier. But then talk to anyone who’s tried scaling a business-critical Power App and they’ll tell you—Frankly, you don’t have a choice. If the CFO is waiting for dashboards that need live calculations from half a million records, you won’t get there with Power Apps alone. The trick is deciding where “just enough” ends and “overkill” begins.Let’s look at something tangible—a loan approval platform, for example. Picture this: your business has a proprietary risk scoring process that’s been tweaked for years by the analytics team. There’s confidential math, there are data pulls from three sources, and the result needs to be calculated instantly, every single time someone submits an application. Power Apps can’t handle that in a single flow or formula. So, you build a slim interface in Power Apps, where users key in application data. That data instantly shoots off to an Azure Function, where the heavy logic runs server-side. Finished resul