procurementtrade-pressNewsThe Broadside2 min read

Microsoft outage exposes agencies’ vendor lock-in

Procurement policy already warns against single-vendor dependence; the outage showed agencies still live inside it.


TL;DR

FedScoop commentary by former Office of Management and Budget and Office of Science and Technology Policy leader Christopher Steven Marcum ties the Nov. 12 Microsoft outage to vendor lock-in, citing nearly 140,000 Downdetector Outlook reports from 74 countries and government disruptions. Agencies buying artificial intelligence and cloud collaboration tools are the audience: OMB M-25-22 and Cybersecurity and Infrastructure Security Agency guidance can warn about portability, but contracts decide whether anyone can move.

FedScoop published an argument from Christopher Steven Marcum, a former Office of Management and Budget and Office of Science and Technology Policy official: the Nov. 12 Microsoft outage is evidence that federal dependence on single-vendor cloud platforms is an operational risk. It doesn't create a new mandate. It does give contracting officers a clean failure mode to put next to the anti-lock-in language agencies already have.

The outage facts are ugly enough without over-reading them. The piece says it began around 1 p.m. Eastern and ran past 12 hours into Friday. Downdetector logged nearly 140,000 Outlook reports in 74 countries.

That matters for federal procurement because the affected services are not exotic edge systems. They are the communications layer agencies use to route work. FedScoop says the U.S. House was affected. In London, the Metropolitan Police lost some online crime-reporting capability; Michigan warned residents that email replies would be delayed. When the fallback plan includes fax machines, the continuity plan is admitting something the acquisition file probably describes more elegantly.

The policy story is already on paper. The article points to Office of Management and Budget memorandum M-25-22 for artificial intelligence buying: contracts should address vendor sourcing, data portability, long-term interoperability, licensing scope and rights to code or models produced under the award. The Cybersecurity and Infrastructure Security Agency has been making the open-source case from the security side too; its 2023 roadmap says open source can improve collaboration while warning that vulnerable or malicious open source can create systemic risk, https://www.cisa.gov/news-events/news/cisa-announces-open-source-software-security-roadmap.

Monday's work is less glamorous. Contracting officers should look for portability language and exit rights before the next outage. If custom code is being built, counsel should check who can reuse, modify or release it. Engineers should know what telemetry and architecture details the contract entitles them to see. If the answer is “wait for Microsoft,” that may be commercially normal. It’s still a dependency, and the outage made it visible.


Published ·Deep Fathom