Source-check dates are not included in the accepted public sample. Full-cohort source dates and statement-age limits remain in the package. The package-check date records offline acceptance, not a source refresh.
100 reviewed Microsoft Azure company accounts. Organization-published Azure infrastructure or AI-service relationships. Evidence applies to the recorded website, product or workload and its source date; current paid use and whole-organization deployment remain unverified. Claims apply only to the recorded property, product or workload.
Microsoft Azure source composition | Source class | Count | Scope |
|---|
| Provider/subprocessor registers | 54 | Published attribution within the stated source, product and date scope; current runtime and paid use are unverified. |
|---|
| Company statements | 21 | Published attribution within the stated source, product and date scope; current runtime and paid use are unverified. |
|---|
| Legal/security disclosures | 14 | Published attribution within the stated source, product and date scope; current runtime and paid use are unverified. |
|---|
| Operational documentation | 11 | Published attribution within the stated source, product and date scope; current runtime and paid use are unverified. |
|---|
Contexts in the Microsoft Azure research: Report functional distinction, 96 infrastructure versus 4 AI/model-only roles; company claims rather than independent runtime. WhosBuilt review of the saved accepted report and approved examples; no source refresh.
Accepted report describes the retained list. Qualitative roles show presence, not prevalence. Counts refer only to the named recorded classifications; no source-by-context intersections are released. The displayed date is the package date. Source dates remain as recorded in the package; no source was refreshed for this analysis.
- Public sources do not verify paid subscriptions, organization-wide deployment or purchasing intent.
- Source retrieval dates record access; they do not make an older statement or historical deployment current.
- Published contact channels do not establish outreach permission, mailbox deliverability or purchasing authority.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.