Azure Tenders and Contracts

Search live procurement portals for Azure-specific notices, or work earlier: on Stotles you can see which buyers already run Microsoft Azure, track Enterprise Agreement renewal dates, and read the strategy documents behind a migration before it reaches tender. A large share of Azure spend renews through an existing agreement rather than a fresh competition, so knowing who is already on Azure is often more useful than watching for a new notice.

Mostly through Microsoft Enterprise Agreements and G-Cloud call-offs rather than standalone tenders. A buyer typically renews or extends licensing and consumption terms with a Microsoft partner, with DevOps, integration and migration work bought separately as project-based call-offs against the same or a related framework. Open competitions do happen for larger migration or managed-service programmes, but licensing renewals rarely go out to fresh tender.

687 of the 1,438 Azure notices tracked to date have reached award. The rest are a mix of closed competitions, pre-tender activity and a small number open now, which reflects how much Azure spend moves through licensing renewals and framework call-offs rather than public advertisement.

Azure work is filed under broad IT services codes rather than a cloud-specific one: CPV 72000000 (IT services: consulting, software development, Internet and support) and 48000000 (Software package and information systems) are the two most common in the sample. Neither is unique to Azure, so the keyword filter, not the CPV code, does the real work of separating Azure notices from the rest of the IT category.