In cloud engineering, tools are easy.

Azure Application Insights. Log Analytics. Key Vault. Entra ID. ADF. Kubernetes. You name it.

But tools don’t create good architecture.

Thinking does.

Over time — across Azure landing zones, identity refactoring, incident recovery, and cost governance work — I noticed something consistent:

Senior Azure architects evaluate systems using a simple mental model.

Not documentation-heavy frameworks.
Not 40-page design templates.

Just four questions.

This article captures that framework for future reference.

---

The 4-Question Azure Architect Framework

You can apply this to:

• A file router
• Monitoring strategy
• Identity design
• Networking segmentation
• SaaS MVP architecture
• Even a small internal utility

---

1️⃣ What Happens When It Fails?

Most engineers ask:

“Does it work?”

Architects ask:

“What happens when it breaks?”

Failure-first thinking changes everything.

For example:

• If a file router crashes, is the file retried?
• If a background job fails silently, who detects it?
• If a dependency times out, does it cascade?
• If logging is disabled, can we reconstruct events?

In Azure environments, this usually translates to:

• Proper use of Azure Application Insights
• Dead-letter queues
• Retry policies
• Correlation IDs
• Alert rules

Resilience is not about uptime — it’s about recoverability and visibility.

---

2️⃣ Who Feels the Impact?

Not all failures are equal.

Ask:

• Is this internal tooling?
• Does it affect customers?
• Is revenue tied to it?
• Is compliance exposure involved?

For example:

If a low-risk internal service fails, default telemetry in Azure Application Insights might be sufficient.

If the system routes financial transactions or regulatory documents, monitoring maturity must increase.

Architecture maturity should match business criticality.

Over-engineering internal tools wastes cost.
Under-engineering customer-facing systems creates risk.

---

3️⃣ Can We Evolve This Without Rebuilding It?

This is where architecture becomes strategy.

Perfect systems don’t exist.
Evolvable systems do.

Ask:

• Can we add custom telemetry later without refactoring?
• Can we scale logging without rewriting the app?
• Can we introduce alerts without redesigning the service?
• Can we move from single-region to multi-region if needed?

Good Azure design allows layering.

For example:

• Start with default App Insights.
• Later add custom events.
• Then introduce dashboards.
• Then configure alerting rules.
• Eventually integrate with SIEM if required.

If improvement requires a rewrite, the original design was brittle.

---

4️⃣ Is Complexity Justified Right Now?

Azure makes it easy to add services.

It’s also easy to overspend and overbuild.

Before adding complexity, ask:

• Are we solving today’s real problem?
• Or anticipating hypothetical risk?
• Is there operational pain?
• Is the cost proportional?

This question protects teams from unnecessary engineering.

Many environments only need:

• Baseline monitoring
• Basic alerting
• Clear logging structure

Not every service needs enterprise-grade observability from day one.

Maturity should evolve with operational pressure.

---

Applying This to a Real Scenario

Imagine someone says:

“We just use default App Insights. We don’t go much further.”

Instead of reacting, run the framework:

1. What happens when it fails?
2. Who feels the impact?
3. Can we evolve monitoring later?
4. Is deeper observability justified now?

The answer might be:

• Baseline telemetry is fine today.
• Add lifecycle logging only if routing becomes business-critical.
• Keep architecture flexible.

That’s architect thinking.

Not reactive.
Not dramatic.
Not tool-obsessed.

---

Why This Framework Matters

In my experience working across Azure infrastructure, identity, DevOps pipelines, and operational recovery scenarios:

The biggest difference between mid-level engineers and senior architects is not tool knowledge.

It’s:

• Systems thinking
• Failure awareness
• Tradeoff evaluation
• Calm decision-making

Architects don’t chase perfection.

They design for evolution.

---

Final Thought

Cloud architecture is not about using more services.

It’s about asking better questions.

Before adding monitoring.
Before redesigning identity.
Before introducing complexity.

Ask the four questions.

They work every time.

Uploading a large file to Azure sounds simple — until you need to process it reliably, at scale, with retries, alerts, and zero surprises at 2AM.

This article walks through how Azure actually handles large file uploads, using a 10-GB video as a concrete example, and then dives into real-world failure modes that show up only in production.

We’ll cover:

• How Azure uploads large files safely
• When and how events are emitted
• How Functions and queues fit together
• Why retries and poison queues exist
• What silently breaks when nobody is watching

---

Azure Blob Storage: Large Files, Small Pieces

Azure Blob Storage supports extremely large files — but never uploads them in a single request.

Most files are stored as block blobs, which are composed of many independently uploaded blocks.

Block blob limits (the important ones)

• Max block size: 4 GiB
• Max blocks per blob: 50,000
• Max blob size: ~190 TiB

Example: Uploading a 10-GB video

A 10-GB video is uploaded as:

• Block 1: 4 GB
• Block 2: 4 GB
• Block 3: ~2 GB

Each block is uploaded with Put Block, and once all blocks are present, a final Put Block List call commits the blob.

Key insight: Blocks are an upload implementation detail. Once committed, the blob is treated as a single file.

Client tools like AzCopy, Azure SDKs, and Storage Explorer handle this chunking automatically.

---

When Does Azure Emit an Event?

Uploading blocks does not trigger processing.

Events are emitted only after the blob is fully committed.

This is where Azure Event Grid comes in.

BlobCreated event flow

1. Final Put Block List completes
2. Blob Storage emits a BlobCreated event
3. Event Grid routes the event to subscribers

Important: Event Grid fires once per blob, not once per block.

This guarantees downstream systems never see partial uploads.

---

Azure Functions: Reacting to Blob Uploads

Azure Functions does not poll Blob Storage in modern designs. Instead, it reacts to events.

Two trigger models (only one you should use)

• Event Grid trigger (recommended)
  Push-based, near real-time, scalable
• Classic Blob trigger (legacy)
  Polling-based, slower, less predictable

In production architectures, Event Grid–based triggers are the standard.

---

Why Queues Are Inserted into the Pipeline

Direct processing works — until load increases or dependencies slow down.

This is why many designs add a queue:

Azure Storage Queue

Blob uploaded
   ↓
Event Grid event
   ↓
Azure Function
   ↓
Message written to queue

Queues provide:

• Backpressure
• Retry handling
• Isolation between ingestion and processing
• Protection against traffic spikes

---

Visibility Timeouts: How Retries Actually Work

Storage queues don’t use acknowledgments. Instead, they rely on visibility timeouts.

What is a visibility timeout?

When a worker dequeues a message:

• The message becomes invisible for a configured period
• If processing succeeds → message is deleted
• If processing fails → message becomes visible again

Each retry increments DequeueCount.

This is the foundation of retry behavior in Azure Storage Queues.

---

Poison Queues: When Retries Must Stop

Retries should never be infinite.

With Azure Functions + Storage Queues:

• Once maxDequeueCount is exceeded
• The message is automatically moved to: <queue-name>-poison

Poison queues:

• Prevent endless retry loops
• Preserve failed messages for investigation
• Enable alerting and replay workflows

---

Failure Modes: “What Breaks at 2AM?”

This is where systems separate happy-path demos from production-ready architectures.

Most failures don’t look like outages — they look like silent degradation.

---

1️⃣ Event Grid Delivery Failures

Symptom: Blob exists, but processing never starts.

Cause

• Subscription misconfiguration
• Endpoint unavailable
• Permission or auth issues

Mitigation

• Enable Event Grid dead-lettering
• Monitor delivery failure metrics
• Build replay logic

2AM reality: Files are uploaded — nothing processes them.

---

2️⃣ Duplicate Event Delivery

Symptom: Same file processed twice.

Why
Event Grid guarantees at-least-once delivery, not exactly-once.

Mitigation

• Idempotent processing
• Track blob names, ETags, or IDs
• Reject duplicates at the application layer

2AM reality: Duplicate records, duplicate invoices, duplicate emails.

---

3️⃣ Function Timeouts on Large Files

Symptom: Processing restarts or never completes.

Cause

• Large file downloads
• CPU-heavy transformations
• Insufficient plan sizing

Mitigation

• Increase visibility timeout
• Stream blobs instead of loading into memory
• Offload heavy work to batch or container jobs

2AM reality: Queue backlog grows quietly.

---

4️⃣ Queue Backlog Explosion

Symptom: Queue depth grows uncontrollably.

Cause

• Ingestion spikes
• Downstream throttling
• Scaling limits

Mitigation

• Monitor queue length and age
• Scale consumers
• Add rate limiting or backpressure

2AM reality: Customers ask why files are “stuck.”

---

5️⃣ Poison Queue Flood

Symptom: Many messages land in -poison.

Cause

• Bad file formats
• Schema changes
• Logic bugs

Mitigation

• Alert on poison queue count > 0
• Log full failure context
• Build replay workflows

2AM reality: Work is failing — but nobody is alerted.

---

6️⃣ Storage Cost Spikes from Retries

Symptom: Azure Storage bill jumps unexpectedly.

Cause

• Short visibility timeouts
• Repeated blob downloads
• Excessive retries

Mitigation

• Tune visibility timeouts
• Cache progress
• Monitor transaction counts, not just data size

2AM reality: Finance notices before engineering does.

---

7️⃣ Partial or Corrupted Uploads

Symptom: Function triggers but input file is invalid.

Cause

• Client aborted uploads
• Corrupted block lists
• Non-atomic upload logic

Mitigation

• Validate file size and checksum
• Enforce minimum size thresholds
• Delay processing until integrity checks pass

---

8️⃣ Downstream Dependency Failures

Symptom: Upload succeeds — final destination fails (SharePoint, APIs, DBs).

Mitigation

• Exponential backoff
• Dead-letter after max retries
• Store intermediate results for replay

2AM reality: Azure is healthy — the external system isn’t.

---

9️⃣ Silent Failure (The Worst One)

Symptom: System is broken — nobody knows.

Fix
Monitor:

• Function failure rates
• Queue depth and age
• Poison queue counts
• Event Grid delivery failures

---

Final Takeaway

Large files in Azure Blob Storage are uploaded in blocks, but Event Grid emits a single event only after the blob is fully committed. Azure Functions react to that event, often enqueueing work for durable processing. Visibility timeouts handle retries, poison queues stop infinite failures, and production readiness depends on designing for duplicate events, backlogs, cost creep, and observability — not just the happy path.