Architecture

🧠 Overview Power Automate provides a seamless low-code experience for building automation workflows. However, behind the scenes, it is powered by the Azure Logic Apps runtime, a distributed workflow orchestration engine. While this abstraction simplifies development, it can obscure how triggers actually execute, especially for time-based triggers like Recurrence. Errors such as: WorkflowTriggerNotReady are not caused by flow logic, they originate from the underlying scheduling infrastructure. 🏗️ Execution Architecture At a high level, a Power Automate flow executes through multiple backend layers: ...

🎯 The Problem Power Automate enables rapid workflow creation, but it lacks a standardized approach for: Error handling Failure propagation Observability Cross-flow traceability As solutions scale, this leads to hidden failures and operational blind spots. 🧱 The Missing Layer Enterprise systems typically separate: Execution Logging Monitoring Alerting In Power Automate, these concerns are often mixed or inconsistently implemented. 🛡️ Introducing FlowArmor FlowArmor is a lightweight framework designed to standardize: Error handling Telemetry generation Correlation tracking Failure propagation 🧭 Architectural Pattern FlowArmor enforces a structured execution model: ...

Introduction For over a decade, the “Alert Me” feature in SharePoint served a simple purpose: it told you when something changed. It worked well for a long time, until the way we work became more complex. As organizations grew and collaboration moved faster, these simple alerts became a bottleneck. They were personal, invisible to IT teams, often noisy, and impossible to manage at scale. Replacing them isn’t just about picking a new tool. It is an architectural evolution. We are moving away from isolated file alerts and toward a centralized notification system built on Power Automate. ...

If you’re still typing string values like "Primary", "Center", or "Bold" into your Power Apps formulas, you’re working with “technical debt” by design. With the latest ** 2026 Modern Control updates**, Power Apps has officially shifted toward Typed Enums. This isn’t just a UI change, it’s a fundamental shift toward robust app architecture. The Problem with “Loose Strings” In classic Power Apps, we used patterns like: Button1.Appearance = "Primary" As an architect, here is why this is brittle: ...

If you’ve logged into Power Apps recently looking for the classic “Expense Reimbursement” or “Budget Tracking” templates to study their UI or logic, you might have noticed a glaring change: The Template Gallery as we knew it is gone. As of March 2026, Microsoft has pivoted away from standalone “starter apps” in favor of more robust, enterprise-grade deployment methods. If you are an architect or a developer trying to find these learning resources, here is the new map. ...

In the modern enterprise landscape, Perceived Performance is as critical as actual execution speed. As we scale Power Platform solutions to thousands of users, the traditional “loading spinner” often fails to provide the seamless experience users expect from world-class SaaS products. To address this, I developed PowerShimmer Ultra-Light—a PCF (Power Apps Control Framework) component designed to bridge the gap between heavy data-loading states and high-fidelity user interfaces. The Problem: The “Loading” Friction Standard loading indicators in Power Apps (spinners or progress bars) often create a “stop-and-go” psychological effect. Users perceive the app as “broken” or “stuck” when a screen is completely blank during a ClearCollect or Filter operation. ...