CanFlow Global
When Microsoft Goes Down, Paper Comes Back Up: CBSA SOCP Fallback in Practice
← All insights
carmcbsasystem-outagerelease-procedurescontingency

When Microsoft Goes Down, Paper Comes Back Up: CBSA SOCP Fallback in Practice

A November 12 Microsoft outage triggered CBSA's paper-based System Outage Contingency Plan, reverting electronic cargo reports and CAD releases to manual processing. Here's what importers should expect when the messaging layer fails.

The CBSA Trade Compliance Communiqué TCC26-0169 landed on November 12, 2026: a global Microsoft outage knocked out messaging between external clients and CBSA systems. No CBSA systems themselves went offline, but the transmission layer did. If your broker couldn’t send an eManifest cargo report or receive a release notification electronically, you’re filing paper under the System Outage Contingency Plan (SOCP).

This is not a theoretical drill. It’s a real operational shift that matters for anyone moving commercial goods across the border this week.

What the SOCP Actually Means

The SOCP is CBSA’s fallback protocol when electronic systems can’t exchange messages. It doesn’t mean the border stops processing imports. It means the workflow reverts to paper documentation for the report and release steps.

For PARS and RMD shipments normally filed electronically, you’re presenting physical cargo control documents at the first point of arrival. Carriers submit paper manifests. Importers or their brokers present paper CADs or paper release requests. CBSA officers manually review and stamp releases instead of transmitting electronic authorizations.

This works, but it’s slower. Manual review takes longer than automated risk scoring. Officer availability at a specific CBSA office becomes the bottleneck, not system uptime. If your usual release timeline is same-day on a morning arrival, expect afternoon or next-business-day under paper fallback.

The Release Prior to Payment Angle

One piece that doesn’t get enough attention: RPP bond releases under SOCP still go through, but the release confirmation step changes. Normally CBSA transmits an electronic release message to the carrier and the importer’s broker. Under paper fallback, that message is a stamped document handed back at the counter or faxed to the broker of record.

If your supply chain depends on real-time release status (automated gate-out at a warehouse, tight cross-dock windows), that visibility gap matters. Your carrier might have the stamped paper release but your internal systems won’t know it until your broker manually updates you. We’ve seen Montreal inbound drayage sit an extra half-day at the port just because the release confirmation didn’t auto-trigger the next step.

Why This Outage Is Worth Tracking

Microsoft outages affecting CBSA messaging aren’t routine, but they’re not unheard of either. The bigger context here is that CARM Release 3, which went live on October 21, 2024, shifted Canada’s entire trade accounting and payment infrastructure onto a web portal and electronic messaging backbone. When that backbone has a dependency on a third-party cloud provider, an outage at Microsoft becomes an outage for Canadian import operations.

This isn’t a CBSA systems failure. CBSA’s own infrastructure stayed up. But the integration layer that connects external brokers, carriers, and warehouse operators to CBSA went dark, and that’s enough to trigger paper fallback. The contingency procedures are built for exactly this scenario, but they weren’t built for speed or automation.

What Importers Should Expect

If your broker is filing under SOCP this week:

  • Expect manual coordination. Your broker will call or email you for release confirmations instead of sending automated status updates.
  • Expect slower turnaround. Paper reviews don’t have the same throughput as electronic PARS releases. If you’re used to release within hours of arrival, budget a business day.
  • Expect less real-time visibility. The cargo control number and release status that normally populate your shipment tracking dashboard won’t auto-update. Your broker has the information, but it’s on stamped paper, not in a system feed.

If you’re an NRI (non-resident importer) or you self-file CADs, you’re presenting paper documentation directly to CBSA at the office of first arrival. That means you need someone physically available to submit and retrieve the stamped release. If your usual process is fully electronic and you don’t have a contact at the CBSA office, this is where things stall.

The Compliance Side Stays the Same

One thing the SOCP doesn’t change: your duty and tax obligations, your origin claims, your HS classification, and your admissibility requirements all stay exactly the same. A paper CAD still needs the same data fields as an electronic CAD. SIMA subject goods still need country-of-origin declarations. CFIA-regulated imports still need import permits and OGD release.

The SOCP is a process fallback, not a regulatory holiday. CBSA officers reviewing paper documentation are applying the same admissibility rules, the same tariff treatment, the same risk assessment. If your shipment would have triggered an examination under electronic PARS, it’ll trigger an examination under paper SOCP.

Where this gets tricky is amendments and adjustments. If you file a paper CAD under SOCP and later need to amend it (wrong tariff classification, missed CUSMA claim, incorrect value for duty), you’re filing that amendment into CARM once electronic systems are back. The paper trail and the electronic record need to reconcile, and that’s usually a manual broker task. We track these closely because a mismatch between what CBSA stamped on paper and what shows up in the CARM Client Portal later is a red flag for verification.

How Long Does This Last?

The TCC26-0169 notice says Microsoft is investigating, with no end time posted as of November 12. Most Microsoft Azure outages resolve within hours to a day, but the return-to-service step for CBSA messaging depends on Microsoft’s fix, CBSA’s validation that messaging is stable again, and a formal stand-down notice from CBSA.

Until CBSA issues a follow-up communiqué saying electronic messaging is restored, brokers and importers stay on paper. That could be later today, tomorrow, or into next week. The SOCP stays in place until CBSA explicitly cancels it.

If your shipments are sitting at the Montreal sufferance warehouse waiting for release, the paper fallback timeline matters for dwell fees and onward delivery schedules. A one-day CBSA paper processing delay can push a just-in-time delivery into a weekend hold, which turns into Monday earliest release, and your dwell clock keeps running.

Operational Takeaway

System outages like this are a reminder that CARM, for all its centralization and digital-first design, still has points of failure outside CBSA’s direct control. The SOCP works as a fallback, but it’s not a like-for-like replacement for electronic speed and visibility.

If your customs brokerage relationship is built around automated status feeds and same-day electronic releases, make sure your broker has a manual coordination path that actually works when the system goes down. That means phone and email contact, not just API integrations. It means someone at your broker who knows how to walk a paper CAD through a CBSA office and get the stamped release back to you without waiting for the electronic all-clear.

Microsoft’s outage will end. CBSA will restore electronic messaging. But the lesson sticks: paper is still the floor, and your supply chain needs to work when the system falls back to it. If you want to walk through what SOCP filing looks like for your specific release types and CBSA offices, get in touch.

Source: CSCB

Talk to a broker