Registry / Llama via Azure AI
Llama via Azure AI
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 6
The cells where this offering is not a clean public yes. This is what to check before you sign.
- SOC 2 Type II: Partial Microsoft's SOC 2 Type II report covers Azure platform services but not the Llama model itself, and the report is accessed via the Service Trust Portal.
- ISO 27001: Partial Meta (Llama developer) provides no public ISO/IEC 27001 certification for the Llama model
- ISO 42001: Partial ISO IEC 42001 cert applies to Azure AI Foundry service, not specifically to Meta's Llama model.
- Retention / ZDR: Yes, sales-gated Zero‑Data‑Retention only available after EA/MCA‑level approval
- GPAI Code: No, verified Meta, the developer of Llama, is absent from the European Commission's complete signatory list, confirming a verified no.
- Art. 53 summary: No public evidence no formal EC‑template training‑data summary found on Meta’s site
The Azure SOC 2 Type 2 attestation is a platform certificate whose audit-scope list (Azure, Dynamics 365, Microsoft 365, Power Platform) does not individually include the Llama model, so the model-via-platform offering is only partially covered.
For a list of Microsoft cloud services in audit scope, see the Azure SOC 2 Type 2 attestation report or Cloud services in audit scope: - Azure - Dynamics 365 - Microsoft 365 - Power Platform
Azure’s ISO 27001 certification applies to Azure services but does not specifically include the third‑party Llama model, and no public ISO 27001 evidence exists from Meta for Llama.
The Azure ISO/IEC 27001 certificate covers Azure, Dynamics 365, Power Platform, and select Microsoft 365 cloud services.
Azure’s blog confirms ISO IEC 42001 certification for the Foundry service, and no public evidence shows Meta’s Llama itself holds the certification, so coverage is partial.
By achieving this certification, Microsoft demonstrates that Azure AI Foundry Models, including Azure OpenAI models, and Microsoft Security Copilot prioritize responsible innovation and are validated by an independent third party.
Microsoft's public Trust Center page is openly accessible and confirms a maintained compliance portal covering AI services such as Azure AI, which includes Llama via Azure AI.
Security and privacy in the age of AI
Microsoft's own compliance page states the HIPAA BAA requires no separate contract or sales step — it is included by default in the Microsoft Product Terms for all covered-entity/business-associate customers using in-scope Azure services (including Azure AI Foundry, which hosts Llama) — so the offer
There is no separate contract to sign to enter into a HIPAA Business Associate Agreement (BAA) with Microsoft because the HIPAA BAA is available via the Microsoft Product Terms (formerly Online Services Terms) by default to all customers who are covered entities or business associates under HIPAA.
Public DPA download is available and includes EU SCCs per Microsoft compliance page; Microsoft also publicly publishes the Online Services Subprocessor List as shown on the Trust Center page.
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 Products and Services Data Protection Addendum.
The Microsoft Foundry FAQ publicly states that customer data is not used to train models, covering Llama offered via Azure AI.
Foundry Models don't use customer data to retrain models, and customer data is never shared with model providers.
Microsoft publicly documents the retention policy and states that zero‑data‑retention is gated behind enterprise‑agreement approval, so the claim is sales‑gated.
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).
The page confirms Standard/Regional deployments process data in the chosen Azure region and that Llama-3.3-70B-Instruct is available in Sweden Central, meeting EU data residency requirements.
"Standard/Regional types: Processed in the region associated with your deployment" and "For all deployment types, data stored at rest remains in the designated Azure geography (Americas, Europe, Asia Pacific, and Middle East and Africa)." ... "Llama-3.3-70B-Instruct" ... "Sweden Central"
Meta, the developer of Llama, is absent from the European Commission's complete signatory 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 - ServiceNow - WRITER In addition, xAI signed up to the Safety and Security Chapter; this means that it will have to demonstrate compliance ...
Search of Meta’s official site and repository shows only a brief training‑data line, not the required Article 53 public summary
Training Data | ... | Llama 3 | A new mix of publicly available online data.
Spotted an error? Submit a correction with evidence, corrections with a primary source are folded in and credited in the changelog.