Why a simple Power Automate flow can quietly consume thousands of Power Platform Requests? The Biggest Misconception One of the biggest misunderstandings in Power Platform is believing that: One Flow = One Request Unfortunately... That's almost never true. A single business action can trigger dozens or even hundreds of Power Platform requests, depending on how … Continue reading What Actually Counts as a Power Platform Request?
Understanding Flow Owners, Connections, Service Accounts, and Application Users The Four People Behind Every Flow Imagine a warehouse. Power Platform works the same way. Identity 1 - The Triggering User This is the person or system that starts the journey. Examples: A user updates a Case. A customer submits a form. An email arrives. A … Continue reading Who Actually Pays for the Request?
Opening Hook Imagine a customer raises a support ticket. "Our Power Automate flow is suddenly slow." As developers, our instinct is usually to open the flow designer. Sometimes one of those fixes works. Most of the time... We are fixing the wrong thing. Because we don't actually understand what happens after a flow is triggered. … Continue reading The Journey of a Single Request
Every few months I see another discussion where someone says: "Dataverse API limit is 6000." "No, it's 40,000 requests." "Actually it's 250,000." "Power Automate allows 500,000." Everyone sounds correct. Yet everyone is talking about a completely different limit. That is exactly why Power Platform limits are so confusing. Microsoft hasn't created one limit. They have … Continue reading There Is No Such Thing as “The Power Platform API Limit”
There is a quiet tax on most Power Automate flows: unnecessary loops. You retrieve 500 items from SharePoint. You need 12 of them. So you loop through all 500, checking a condition on each one, building a new array one item at a time. The flow works. It's also doing 488 units of work it … Continue reading Power Automate Data Operations What They Actually Do and When to Use Each One
Here's a scenario that plays out on almost every Power Platform project. You have three approval workflows: one for project proposals, one for leave requests, one for expense submissions. Each one needs to look up the list of approvers from a SharePoint group. So you build that lookup logic into the first flow, then copy … Continue reading Stop Copying Logic Across Flows. Use Child Flows
Power Automate gives every action a default name the moment you drop it onto the canvas. "Apply to each", "Condition", "Send an email (V2)". Then you move on, wire up the logic, and ship the flow. Six months later, someone maybe you, maybe a colleague opens it for the first time. They see twelve nested … Continue reading Stop Naming Your Flow Actions “Scope” and “Apply to Each”
If you’ve worked with older Dynamics 365 or CRM SDK codebases, you’ve probably seen this: AuthType=Office365 Or worse silent authentication failures after Microsoft tightened security policies. This post explains: Why legacy authentication was deprecated What breaks in old solutions How to migrate safely How to modernize your tooling If you're maintaining older code, this post … Continue reading Connecting to Dataverse: Migrating from Office365 / WS-Trust to Modern OAuth
In the previous post, we covered multi-tenant Server-to-Server (S2S) authentication the pattern for backend SaaS platforms. Now we switch to the opposite extreme: A browser-only app (React / Angular / Vue) that calls Dataverse directly. No backend proxy.No middleware.Just JavaScript, OAuth tokens, and the Dataverse Web API. This is the SPA + CORS pattern. When … Continue reading Connecting to Dataverse from a Single Page App (SPA) using MSAL + CORS
In the previous post, we implemented Server-to-Server authentication for a single tenant. That works perfectly when: You own the tenant. The app runs internally. It serves one organization. But what if: You are building a commercial product? Multiple customers must connect their own Dataverse environments? You’re publishing to AppSource? Your app needs to scale across … Continue reading Connecting to Dataverse: Multi-Tenant Server-to-Server (SaaS / ISV Architecture)
