Cloud provider comparisons in early 2020 typically read as feature lists across AWS, Azure, Google Cloud, IBM, Salesforce, and Oracle. For public-sector procurement, that framing missed what mattered. By early 2020, the practical choice for federal, state, local, and higher education workloads had narrowed to two providers, with the rest occupying specific niches. This post is a snapshot of that landscape from a public-sector operations perspective.
AWS
Amazon Web Services launched in March 2006 and was the first hyperscaler with serious public-sector traction. By 2020, AWS GovCloud had been running for years, AWS Public Sector was a dedicated business unit, and AWS held the deepest FedRAMP authorization portfolio of any cloud provider. The AWS Marketplace included a Government segment with cooperative purchasing channels.
For agencies prioritizing breadth of compliance authorizations and depth of public-sector partner ecosystem, AWS was effectively the default in 2020. Pay-as-you-go billing, hourly granularity, and the option to commit to Reserved Instances for predictable workloads matched the procurement patterns most agencies were comfortable with.
Microsoft Azure
Microsoft Azure launched in February 2010 and grew rapidly through Microsoft's existing enterprise relationships. Azure Government, FedRAMP authorization for federal customers, and tight integration with Active Directory made Azure the obvious second choice for agencies already running Microsoft Office and Active Directory at scale. The 2019 JEDI contract award (later cancelled and re-procured) signaled Azure's federal traction.
For higher education, Azure's integration with Active Directory Federation Services and the existing Microsoft EA structure most universities had in place made Azure the preferred path for institutions whose identity and productivity stack was already on Microsoft. Azure was also the cleaner choice for healthcare workloads with HIPAA constraints because of Microsoft's broader healthcare compliance portfolio.
Google Cloud
Google Cloud Platform was technically excellent in 2020, particularly for analytics and machine learning workloads, but its public-sector posture lagged AWS and Azure. FedRAMP coverage was narrower. The procurement and channel partner ecosystem was less mature for agencies accustomed to working through cooperative purchasing or AWS Public Sector partners. For specific workloads (BigQuery analytics, ML on TPUs) Google Cloud was a strong choice; for general agency infrastructure, it was a niche option.
IBM Cloud, Salesforce, Oracle
IBM Cloud (formerly Bluemix) had genuine differentiation in bare-metal hosting and dedicated infrastructure, which mattered for specific workloads where the noisy-neighbor problem in shared public cloud was unacceptable. Federal agencies with classified or near-classified workloads sometimes chose IBM for that reason.
Salesforce in 2020 was effectively a vertical SaaS provider rather than a general-purpose cloud. For CRM and citizen engagement workloads, Salesforce was a strong choice. As a substrate for arbitrary infrastructure, it was not in the running.
Oracle Cloud in 2020 was still building out its public-sector compliance posture. Oracle's installed base in public sector was substantial (databases, ERP), but Oracle Cloud Infrastructure as a general-purpose alternative to AWS or Azure was not yet operationally mature for most agency adoption decisions.
What Drove Public-Sector Cloud Selection in 2020
The provider feature list mattered less than three procurement and compliance dimensions:
Compliance authorization depth. FedRAMP-authorized service breadth was the single most-cited filter for federal agency cloud decisions. AWS and Azure had the broadest portfolios. Other providers were narrower.
Procurement path. AWS Marketplace, Azure Government, cooperative purchasing channels, and SBA 8(a) contracting paths existed for AWS and Azure. Other providers required custom procurement, which added months to acquisition timelines.
Existing skill base. Agencies that had been running on-premises Microsoft stacks for two decades had Active Directory, Exchange, and SQL Server skills internally. Azure migration leveraged that. Agencies with Linux and open-source stacks had AWS-shaped skills more readily.
These three factors, more than any feature comparison, determined what agencies actually picked.
Frequently Asked Questions
Why did AWS and Azure dominate public-sector cloud in 2020?
Compliance authorization breadth (FedRAMP), mature procurement channels (AWS Marketplace, Azure Government, cooperative purchasing), and existing partner ecosystems. Other providers had specific strengths but did not match the operational posture public sector required.
What is AWS GovCloud and why did agencies use it?
AWS GovCloud is an isolated AWS region operated under specific compliance constraints (US persons only for operational access, FedRAMP High authorization, ITAR support). Agencies with workloads requiring those constraints used GovCloud rather than commercial AWS regions.
How did agencies migrate from on-premises to AWS or Azure in 2020?
Typical patterns were lift-and-shift to virtual machines (AWS EC2, Azure VMs) for legacy applications, replatforming to managed services (RDS, Azure SQL) for databases, and re-architecting net-new workloads as cloud-native (Lambda, App Service, S3, Blob Storage). Cooperative procurement and partner-led migrations were the dominant operational pattern.
Did the cloud landscape change significantly after 2020?
The general two-provider dominance persisted. Google Cloud closed some of the public-sector gap with FedRAMP authorization expansions and dedicated public-sector teams. The procurement infrastructure around AWS and Azure deepened. The fundamental decision pattern (compliance, procurement path, skill base) remained the same.