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

Registry / Llama via Azure AI

Llama via Azure AI

developer: Meta platform: Microsoft Azure (Azure AI Foundry / Models-as-a-Service) category: cloud distribution

Meta's Llama models served as third-party serverless (Models-as-a-Service / standard) deployments on Microsoft Azure AI Foundry. Microsoft hosts the model on Microsoft-managed infrastructure and acts as data processor; Meta remains the model developer and the GPAI provider for EU AI Act purposes.

Watch-outs 7

The cells where this offering is not a clean public yes. This is what to check before you sign.

  • SOC 2 Type II: Partial Azure AI (including Llama) is not listed in the SOC 2 scope, so only the general Azure platform coverage applies.
  • ISO 27001: Partial Azure ISO 27001 certification covers only listed Azure services and does not include the Llama model; no public Meta ISO 27001 cert for Llama found
  • ISO 42001: Partial ISO 42001 certification covers Microsoft Foundry (the platform) but does not extend to the Llama model itself
  • HIPAA BAA: Unclear Microsoft staff cannot confirm model‑specific HIPAA BAA coverage for Azure AI Foundry models such as Llama
  • Retention / ZDR: Yes, sales-gated Zero‑Data‑Retention must be approved per resource via a support request and enterprise agreement.
  • GPAI Code: No, verified Meta, the developer of Llama, is not listed among the signatories on the EU Commission's authoritative GPAI Code of Practice list, confirming a verified no.
  • Art. 53 summary: No public evidence No dedicated Article 53 training‑data summary for Llama is publicly available on Meta’s own site; only a general overview exists.
Vendor trust
SOC 2 Type II Is a SOC 2 Type II report available for this offering?
◔Partial confidence: high · verified 2026-11-17

The Azure SOC 2 Type II report enumerates in‑scope services and does not include Azure AI, meaning the Llama model served via Azure AI is only partially covered by the platform's SOC 2 certification.

Services in scope: Azure, Dynamics 365, Microsoft 365, Power Platform.

source

ISO 27001 Is there an ISO/IEC 27001 certification covering this offering?
◔Partial confidence: high · verified 2026-11-18

The Azure ISO 27001 scope list omits Llama, and no authoritative Meta ISO 27001 certification covering Llama is publicly available, so coverage is partial

Services in scope - Azure - Dynamics 365 - Microsoft 365 - Power Platform

source

ISO 42001 Is there an ISO/IEC 42001 (AI management system) certification?
◔Partial confidence: high · verified 2026-11-19

Microsoft’s ISO 42001 certification applies to the Foundry service that hosts Llama, while Meta does not publicly hold its own ISO 42001 certification, so the offering is only partially covered

## Microsoft AI services in scope for ISO 42001 certification - ... - Microsoft Foundry - ...

source

Trust center Is there a maintained trust center / compliance portal?
●Yes, public confidence: high · verified 2026-11-19

Microsoft's Service Trust Portal publicly lists an AI Resources page that documents compliance, security, and privacy for Azure AI services, confirming a maintained trust/compliance portal for Llama via Azure AI.

Resources describing the approach to Compliance, Security and Privacy in the Artificial Intelligence (AI) solutions such as Copilot and Azure Open AI

source

Data handling
HIPAA BAA Will they sign a HIPAA Business Associate Agreement covering this offering?
?Unclear confidence: medium · verified 2026-11-19

The authoritative Microsoft Q&A response states that coverage for individual models like Llama cannot be confirmed, so the BAA applicability remains unclear

Based on the currently available Microsoft documentation, we cannot confirm which specific AI models (for example, Anthropic Claude Sonnet, Claude Opus, or individual Azure OpenAI models) are covered for processing Protected Health Information (PHI) under the Microsoft General HIPAA Business Associate Agreement (BAA)

source

GDPR DPA Is there a public DPA with SCCs and a published subprocessor list?
●Yes, public confidence: high · verified 2026-11-21

The DPA is publicly downloadable (aka.ms/DPA) and includes the Standard Contractual Clauses; the subprocessor list is published on the Trust Center and linked to the DPA, satisfying both requirements.

Microsoft makes the EU Model Clauses available to customers as described in the Microsoft Online Services Terms (OST) Data Protection Addendum (DPA). ... The Microsoft Online Services Subprocessor List identifies subprocessors authorized to subprocess customer or personal data in Microsoft Online Services. This list is applicable for all Microsoft Online Services governed by the Microsoft Data Protection Addendum.

source

No-training default Is there a public commitment not to train on customer API data by default?
●Yes, public confidence: high · verified 2026-11-20

The Microsoft security blog publicly states that customer data is not used to train models, providing an unrestricted public commitment for Llama via Azure AI.

Customer data is not used to train models, nor is it made available outside of the Azure tenant (unless the customer designs their system to do so).

source

Retention / ZDR Is retention documented, and is zero-data-retention available?
◐Yes, sales-gated confidence: high · verified 2026-11-19

The public Microsoft Q&A page documents the data‑retention policy and confirms zero‑data‑retention is only available through a gated approval process, matching the yes_sales_gated classification.

ZDR requires explicit approval and is not enabled by default. As Zero Data Retention is not a self‑service portal setting, it requires an approved Azure OpenAI resource, a formal support request and business justification, typically an Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA).

source

Residency Can data be pinned to a region (especially the EU)?
●Yes, public confidence: high · verified 2026-11-20

Microsoft’s public Foundry deployment‑type docs state that standard and regional provisioned deployments pin inference data to the chosen Azure geography, enabling EU region pinning for Llama via Azure AI.

Standard and Regional Provisioned types: Prompts and responses are processed within the customer‑specified Azure geography

source

EU AI Act
GPAI Code Is the model developer on the EC's GPAI Code of Practice signatory list?
✕No, verified confidence: high · verified 2026-11-18

Meta, the developer of Llama, is not listed among the signatories on the EU Commission's authoritative GPAI Code of Practice list, confirming a verified no.

## Signatories of the code of practice - AI Studio Delta - Aleph Alpha - Almawave - Amazon - Anthropic - Black Forest Labs - Bria AI - Cohere - Domyn - Dweve - Fastweb - IBM - LINAGORA - Microsoft - Mistral AI - Open Hippo - OpenAI - Pleias - Reflection AI, Inc. - ServiceNow - WRITER In addition, xAI signed up to the Safety and Security Chapter...

source

Art. 53 summary Has the model developer published the Art. 53 training-data summary?
○No public evidence confidence: low · verified 2026-11-21

No dedicated Article 53 training‑data summary for Llama is publicly available on Meta’s own site; only a general overview exists.

The information we use to develop and improve AI at Meta includes a mix of publicly available data, licensed data and information from Meta’s products and services... This page provides a general overview of data sources but does not contain a specific Article 53 training‑data summary.

source

Spotted an error? Submit a correction with evidence, corrections with a primary source are folded in and credited in the changelog.