An Azure offering that provides a suite of purpose-built technologies for protected health information in the cloud.
Hello Xavier Serrano,
Greetings! Thanks for raising this question in the Q&A forum.
You have accurately described the situation, and I want to be direct with you about what is possible through this forum and what the correct escalation path is.
The Q&A forum is a community and moderator space and does not have a direct channel to the Azure OpenAI Gating or Trust and Safety teams. Moderators here cannot route your case or Application ID to those internal teams. The only supported path to reach them is through a formal Azure Support request, which I will explain below. That said, there are concrete steps you can take right now to escalate this effectively.
The core constraint you have already identified is accurate: Zero Data Retention is not a self-service setting in the Azure portal. It is a gated capability that requires Microsoft approval, and is only available to customers on an Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA). Your current subscription type determines your eligibility, and the Gating team's decline of your application reflects this structural requirement rather than a judgment on your use case.
Here are the steps most likely to move your request forward given your deadline.
Raise an Azure Support request citing your clinical research use case explicitly. In the Azure portal, navigate to Help + support > New support request. Set the Issue type to Technical, select your Azure OpenAI resource, and describe your ZDR/Modified Abuse Monitoring requirement. Include your Application ID (3636178), the executed HIPAA BAA reference, your Statistical Analysis Plan's ZDR mandate, and the fact that your prior application was declined on managed customer grounds rather than on the merits of the use case. A Microsoft Support Engineer will coordinate with the Azure OpenAI product team and can flag your case for manual review even without a managed account designation in some circumstances. After submission, allow approximately 5 to 7 business days for the team to review and respond.
Pursue an Enterprise Agreement or Microsoft Customer Agreement to unlock formal eligibility. Both Modified Abuse Monitoring and ZDR require approval and are available to customers on an Enterprise Agreement or Microsoft Customer Agreement. They are not self-service portal settings. If your organisation does not already have an EA or MCA, contacting a Microsoft sales representative to establish one is the structural fix that removes the managed customer barrier entirely. Given your clinical research timeline, frame the urgency explicitly when engaging the sales team, as health-tech and research workloads are a recognised use case for expedited agreement processing.
Contact your Microsoft account team if one exists. If your organisation has any existing Microsoft relationship — through a CSP partner, an ISV programme, or a prior enterprise agreement of any kind — engage that contact directly and ask them to escalate your Modified Abuse Monitoring request internally. A Microsoft account team member can submit the request on your behalf, which is the standard intake path for managed customers.
In the interim, consider architectural mitigations to reduce PHI exposure. While your escalation is in progress, you can reduce risk by ensuring your GPT-4o prompts are de-identified before they reach the Azure OpenAI endpoint, with re-identification happening in your own infrastructure after the completion is returned. This does not satisfy a strict ZDR mandate but can serve as a documented interim control in a clinical research protocol. Additionally, confirm that your Azure OpenAI resource is deployed in a standard (non-Global, non-DataZone) deployment type in your required region to enforce data residency at the infrastructure level regardless of ZDR status.
Verify ZDR status once approved. When and if approval is granted, you can confirm it is active on your resource using the Azure CLI:
az cognitiveservices account show \
-n <resourceName> -g <resourceGroup> \
--query "properties.capabilities[?name=='ContentLogging'] | [0].value" \
-o tsv
A result of false confirms that content logging and abuse monitoring storage have been disabled for that resource.
If this answer helps you kindly accept the answer which will help others who have similar questions.
Best Regards,
Jerald Felix.