Azure OpenAI Service

Microsoft · AI model API

Ayliea's assessment: Medium RiskAyliea recommends: MonitorIn Ayliea's curated list

Public sources reviewed . Risk classification and recommended policy are Ayliea's subjective assessments — not vendor certifications.

Scope of this recommendation

Azure-hosted OpenAI models in the selected Foundry deployment; not direct OpenAI or all third-party marketplace models.

Public documentation review only. Current audit reports, certificate scope, executed contracts and customer settings were not independently examined. An omitted assurance claim is not evidence that the vendor lacks it.

Storage and processing locations
Regional, DataZone and Global deployments have different processing boundaries; resource location alone does not fix inference location.
Retention and ZDR scope
Abuse monitoring and stateful features can retain data. Review modified abuse monitoring eligibility and feature storage; no blanket ZDR guarantee.
Vendor-reported audits / certifications
Not established in this public-source review

Why this rating

Microsoft documents no training of foundation models on customer prompts without permission. Azure controls can support regulated deployments, but do not make it universally safer than direct APIs or guarantee in-region processing for Global deployments.

Considerations before deploying

  • Select deployment type to match storage and inference-location requirements.
  • Review abuse monitoring, stored state, content filters, identity and private endpoints.
  • Verify service/model/region coverage in the current BAA, audit or authorization; infrastructure assurance is not universal product approval.

Sources

Need a vendor review for your use case?

A scoping call defines the systems, data flows and vendor evidence to review for your use case.