Skip to main content

D365 CE / Power Platform - Designing for Supportability: What Happens at 2 AM?

 

Designing for Supportability: What Happens at 2 AM?

Every architecture looks clean at 2 PM.

It’s only at 2 AM, when something breaks in Production, that the truth appears.

  • An integration silently stops

  • A flow fails halfway

  • An order never reaches ERP

  • A customer is stuck in limbo

And someone asks the most important question in enterprise IT:

“How do we know what happened?”

If your honest answer is:

  • “Check the flow run history.”

  • “Enable tracing and retry.”

  • “We’ll reproduce it in UAT.”

  • “Let’s ask the vendor.”

…then your system is functional—but not supportable.

Supportability is not an operations problem.
It is an Architectural Outcome.

The Invisible System Problem

Many Power Platform solutions fail in production not because logic is wrong—but because failures are:

  • Silent

  • Distributed

  • Non-deterministic

  • Hard to correlate

  • Impossible to replay

You may have:

  • Plugins in Dataverse

  • Flows in Power Automate

  • Azure Functions

  • Service Bus queues

  • External APIs

Each has its own logs. 
None tell the story.

At 3 AM, support doesn’t need logs.
They need narrative:

“This Opportunity was approved at 01:12.
The event was published.
ERP processing failed due to credit check.
It retried twice.
It is now in dead-letter awaiting review.”

If your Architecture cannot tell that story, it is incomplete.

Architect for Observability

Supportable systems are designed to speak.

That means:

  • Every business event has an ID

  • Every integration carries correlation

  • Every failure is captured centrally

  • Every async process reports state

  • Every message has a lifecycle

Pattern:


Now support can answer:

  • What happened?

  • Where did it fail?

  • Has it retried?

  • Can we replay?

  • Who owns it?

Without guessing.
Without redeploying.
Without waking developers.

Functional Impact

For the business:

  • Fewer “black holes”

  • Faster resolution

  • Clear ownership

  • Trust in automation

  • No mystery failures

For IT:

  • Deterministic recovery

  • Auditability

  • Root cause analysis

  • No hero debugging

  • Predictable operations

Your system becomes operable, not just correct.

The Takeaway

If your architecture cannot answer:

“What happened to this business transaction?”

…in under 60 seconds, then it is not enterprise-grade.

Power Platform makes it easy to build solutions.
Enterprise architecture makes them survivable.

Because in the real world, systems are not judged by how they work at 2 PM. They are judged by how they fail at 3 AM.


Comments

Post a Comment

Popular posts from this blog

Automation using Azure DevOps for Dynamics 365 CE / CRM / Dataverse

In enterprise Dynamics 365 CE / CRM / Dataverse projects, manual deployments create long-term problems such as: inconsistent releases missing components in Production unmanaged customization pollution deployment failures due to dependencies rollback complexity lack of traceability That is why modern organizations implement Azure DevOps automation for Dynamics 365 CE / CRM using CI/CD pipelines. This blog explains how to architect a complete automation strategy using Azure DevOps for D365 CRM projects. Why Azure DevOps for D365 CRM? Azure DevOps provides: version control (Git repos) build & release pipelines approvals and governance artifact management deployment automation integration with Power Platform tools 📌 Architect Callout If you don’t have CI/CD, you don’t have enterprise ALM. 1. Target ALM Architecture (Enterprise Standard) Recommended Environment Setup A proper CRM ALM environment chain: ...
Post a Comment
Read more

Solution Layering in Dynamics 365 CE / CRM / Dataverse (Managed vs Unmanaged Explained)

Solution layering is one of the most misunderstood concepts in Dynamics 365 CE / CRM / Dataverse . Many production issues happen because architects and developers don’t fully understand which customization “wins” when multiple solutions modify the same component. This blog explains solution layering in a simple and practical way. ✅ What is Solution Layering? Solution layering means: When multiple solutions modify the same component (form, field, view, etc.), Dataverse decides which customization is applied based on the solution layer order. Every customization sits on a “layer”. 🔥 Types of Layers in D365 There are two major types: 1. Unmanaged Layer Created when you customize directly in the environment Highest priority (usually overrides managed) 2. Managed Layer Created when you import a managed solution Multiple managed solutions can stack on each other 📌 Architect Callout: Unmanaged layer is like “local override”. ...
Post a Comment
Read more

Architecting Beyond the Box: D365 CE, Power Platform & Azure in the Real World

  Architecting Beyond the Box: D365 CE, Power Platform & Azure in the Real World In most enterprise programs, Dynamics 365 CE and the Power Platform are not the system—they are part of a much larger digital ecosystem. CRM is expected to orchestrate processes, surface insights, integrate with core platforms, and scale with the business. This is where architecture matters more than features. As architects, our job is not to “make it work,” but to make it sustainable . The Common Trap: Overloading the Platform A frequent anti-pattern I see is treating Dataverse and Power Apps as a full replacement for enterprise integration or processing layers: Heavy synchronous plugins for complex business logic Power Automate flows performing batch processing CRM used as a reporting engine Direct point-to-point integrations between systems It works—until it doesn’t. You start seeing: Timeouts in plugins and flows API throttling ...
Post a Comment
Read more