Your GDPR review is two weeks out. Someone asks whether Azure OpenAI retains prompts. You check the docs. There it is, in plain language: prompts and completions are stored for up to 30 days in Microsoft-operated infrastructure — outside your Azure tenant, not queryable, not deletable. Every internal service name, architecture decision, and business context your team fed into the model has been sitting there since day one.
This is not a privacy policy ambiguity. It is a documented default, and it exists because Microsoft runs abuse monitoring on that data. The feature that removes it is called Modified Abuse Monitoring, and it reduces retention to zero. It is not a toggle in the portal — it is a gated program that requires a formal application, a documented business justification, and Microsoft approval. The approval process alone runs 5–10 business days. If your security review is already scheduled, you are already behind.
Here is how to apply, what to verify when you get approved, and what breaks if you move subscriptions.
1. Understanding the Default Abuse Monitoring Model
By default, Azure OpenAI retains data for the purpose of detecting policy violations and abuse. These logs are stored in Microsoft-operated infrastructure, entirely outside your Azure tenant. You cannot query, export, or delete these logs independently.
This is not a flaw — it is a default designed for onboarding, not production. For many regulated industries, it creates a hard compliance problem. GDPR Article 28 requires that data processors not retain personal data beyond the stated purpose. SOC 2 Type II auditors routinely ask about data transmission to third-party systems and the associated retention policies. Default abuse monitoring is that third-party retention obligation, and it requires explicit controls.
2. Modified Abuse Monitoring — The Technical Effect
Zero Data Retention (ZDR) is technically implemented by opting out of the standard abuse monitoring logs.
What ZDR Eliminates vs. What Functions
| Feature | Standard Mode | Zero Data Retention (ZDR) |
|---|---|---|
| Log Storage | 30 Days (Microsoft Side) | None (Discarded after inference) |
| Content Filtering | Active | Active (Real-time only) |
| Usage Metrics | Token counts logged | Token counts logged |
| Customer Logs | Diagnostic Settings (Optional) | Diagnostic Settings (Optional) |
With ZDR active, data is processed in memory for the inference request and then immediately discarded. Real-time content filtering (Azure AI Content Safety) still runs to prevent jailbreaking or toxicity, but the content of those prompts is never written to a persistent store.
ZDR Data Lifecycle (In-Memory Processing)
ZDR only removes Microsoft’s logs. If you have configured Azure Monitor Diagnostic Settings to send logs to your own Log Analytics workspace, those logs remain active. You keep audit visibility while ensuring Microsoft holds no copy.
Shared Responsibility: ZDR vs. Customer Logs
3. Eligibility Requirements
Microsoft strictly gates the ZDR program based on agreement type and business justification.
Agreement Gating
Standard Pay-As-You-Go (PAYG) subscriptions are not eligible. To apply for ZDR, your subscription must be under one of the following:
- Enterprise Agreement (EA)
- Microsoft Customer Agreement — Enterprise (MCA-E)
- Azure Government (Government-specific provisions)
If you are on PAYG, you need to transition to an enterprise agreement before you can apply. That process has its own timeline, so factor it in early.
Use Case Justification
“We prefer privacy” is not a sufficient justification. Microsoft requires a documented reason tied to a recognized compliance framework or a contractual obligation. Recommended framing includes:
- “GDPR Article 28 compliance requiring zero data processing retention.”
- “SOC 2 Type II audit requirement CC6.7 for data transmission privacy.”
- “Contractual data processing agreement (DPA) prohibiting third-party data retention.”
4. The Limited Access Review Application
The application is submitted via the Azure OpenAI Limited Access intake form at aka.ms/oai/modifiedaccess.
Completion Tips
- Identifiers: You need your Azure Subscription ID and Tenant ID.
- Accuracy: Answering “Yes” to whether the workload processes personal data or trade secrets is often a prerequisite for a successful justification.
- Timeline: Approval typically takes 5–10 business days, though it can stretch to 4 weeks during peak periods.
Approval is granted per Subscription ID. If you have multiple subscriptions, you must apply for each one individually. Getting approved for one does not automatically cover the others in the same tenant. This catches teams off guard when they spin up a new subscription after an initial approval.
5. Technical Verification
After receiving the approval email, you still need to configure it in the portal. The approval email does not activate ZDR — it only unlocks the option. Navigate to Azure AI Foundry (Studio) -> Content Filters.
Portal Activation
Create or edit a custom content filter. If approved, the “Abuse monitoring” checkbox will be available to uncheck. Disabling this checkbox activates ZDR for any deployment using that specific content filter.
CLI/ARM Verification
Verify the ZDR status programmatically by checking the ContentLogging capability on the Cognitive Services resource.
# Verify ContentLogging capability via Azure CLI
az cognitiveservices account show -n <resource-name> -g <resource-group> \
--query "properties.capabilities[?name=='ContentLogging']"
# Expected: [{"name": "ContentLogging", "value": "false"}]
If the value is false, the resource is successfully configured for Zero Data Retention. Do not skip this check — the portal confirmation alone is not sufficient evidence for an audit.
6. Edge Cases and Troubleshooting
- Subscription Migrations: If you move an OpenAI resource to a new subscription, ZDR does not follow. You must re-apply for the new subscription ID.
- Infrastructure as Code (IaC): In your Bicep templates, include the
ContentLogging: falsecapability if the API version supports it. Be aware that redeploying without this property can sometimes reset the resource to the default state. - Toggle Missing: If you have the approval email but the toggle is missing in the portal, wait 24–48 hours for the entitlement to “hydrate” across the Azure backbone.
Key Takeaways
- Retention is the Default: Azure OpenAI retains prompts for 30 days unless you explicitly opt out via the Modified Abuse Monitoring program.
- Eligibility is Strict: Only Managed Customers (EA/MCA-E) are eligible. PAYG accounts must transition to an enterprise agreement before applying.
- Application is the Bottleneck: Submit the ZDR form as early as possible. The approval process is a hard dependency for production compliance.
- Verification is Mandatory: Do not assume approval equals activation. You must disable the toggle in Azure AI Foundry and verify via CLI properties.