AI Provider Trust Registry evidence verified as of 2026-11-21

Registry / compare

OpenAI API vs Azure OpenAI Service

The same dimension can grade differently depending on who serves the model. Every cell links to its source; grades are evidence grades, not endorsements.

Dimension OpenAI API Azure OpenAI Service
SOC 2 Type II ◐Yes, sales-gated OpenAI's Trust Portal confirms the SOC 2 Type II report is available but only to authenticated customers, fitting the yes_sales_gated classification. ◐Yes, sales-gated The provider’s own blog confirms SOC 2 coverage and directs users to the Service Trust Portal, a gated portal, so the report is available but not publicly without login.
ISO 27001 ●Yes, public OpenAI’s own security and privacy page publicly lists ISO/IEC 27001:2022 certification covering the OpenAI API. ✕No, verified The provider’s official ISO 27001 offering page lists the services in scope and Azure OpenAI Service is not among them, so the certification does not cover this offering.
ISO 42001 ●Yes, public OpenAI’s own public security and privacy page explicitly states the ISO/IEC 42001 certification for its AI products, confirming the claim. ●Yes, public The Microsoft blog publicly confirms Azure OpenAI models are covered by the ISO/IEC 42001:2023 certification.
Trust center ●Yes, public The OpenAI Trust Portal is publicly accessible and provides compliance documentation for the API, confirming a maintained trust center. ●Yes, public Microsoft's Service Trust Portal publicly hosts an AI Resources page that includes Azure OpenAI, confirming a maintained trust center.
HIPAA BAA ●Yes, public OpenAI publicly documents a self‑serve flow to accept a BAA for the API without a sales‑managed agreement, confirming they will sign a HIPAA BAA for this offering. ●Yes, public Microsoft's authoritative Azure HIPAA offering page confirms the BAA is publicly available by default through the DPA/Product Terms with no gate, so yes_public is correct;...
GDPR DPA ●Yes, public OpenAI’s public DPA includes SCC language and references a publicly viewable Sub‑Processor List, satisfying the requirement. ●Yes, public Replaces the third-party shl.com copy with Microsoft's own pages: the DPA is publicly downloadable on microsoft.com/licensing, Microsoft's white paper states it "released an...
No-training default ●Yes, public OpenAI’s own help article publicly states that API data is not used for model training by default, satisfying the commitment. ●Yes, public The Azure OpenAI data‑privacy page publicly states that prompts and completions are not used to train foundation models without explicit customer permission, confirming a...
Retention / ZDR ◐Yes, sales-gated OpenAI’s public developer guide documents data retention and states Zero Data Retention requires sales‑team approval, so the claim is correct as yes_sales_gated. ◔Partial Docs confirm data retention is described (human‑review storage) and that zero‑data‑retention is only available via a sales‑gated modified abuse monitoring request, so the claim...
Residency ●Yes, public OpenAI’s own public page describes self‑service creation of a Project with Europe selected, allowing API data to be processed and stored in the EU. ◔Partial Microsoft’s official data‑privacy page confirms processing is limited to the chosen geography but not to a specific region, matching the rubric’s definition of partial.
GPAI Code ●Yes, public The European Commission’s GPAI Code of Practice signatory list on the official page includes OpenAI, confirming the model developer is a signatory. ●Yes, public The EC’s official GPAI Code of Practice signatory list, hosted on the European Commission site, includes OpenAI, confirming the model developer is a public signatory.
Art. 53 summary ●Yes, public OpenAI provides an unrestricted PDF on its own cdn.openai.com domain titled “Public Summary of Training Content for GPT-6 Astra”, satisfying the Article 53 requirement. -Not applicable The Art. 53 training-content summary is a developer obligation, and per the knowledge base serving-platform rows (e.g. Azure OpenAI Service) are not_applicable, even though...