Azure OpenAI
Azure OpenAI lets companies use OpenAI's models through Microsoft's Azure cloud, with Azure billing, safety filters and data controls.
Azure OpenAI is a way for companies to use OpenAI’s models without leaving Microsoft’s Azure cloud. OpenAI makes the models. Microsoft runs copies of them on its own computers and sells access as part of Azure. The bill arrives on the company’s normal Azure account, and Microsoft gives support if something breaks.
Why not just call OpenAI directly? Microsoft’s terms say your prompts and answers are not shown to other customers or to OpenAI. They are not used to train models unless you agree. The models here also do not talk to OpenAI’s own services. Microsoft does still store and process data to run the service and to watch for misuse.
Using it starts with a deployment. First a team creates a resource, which is like its own account space inside Azure. Then it deploys a model into it, which means switching on a copy the team can call. The deployment type decides two things: where the prompt is processed, and how you pay. You can pay per token (a token is a small chunk of text), reserve capacity, or send big jobs in a cheaper batch. For place, “Global” may use any Azure region (a region is a group of data centres in one part of the world), while “Data Zone” keeps processing inside an area such as the EU. Microsoft suggests Global Standard as the starting point for most work.
Here is an everyday example. A school’s help desk wants a bot that answers questions about timetables. Its developer already wrote code for OpenAI. With the newer v1 API (the set of rules programs use to talk to the service), they keep the same OpenAI code library and change the web address to their own Azure resource, ending in /openai/v1. When a student types a question, a content filter checks it first. The filter uses classifier models, which sort text into categories. It looks for hate, sexual content, violence and self-harm, at four levels from safe to high. Then the model writes an answer, and the filter checks that too before the student sees it.
There are limits. Filters are automatic classifier models. They also skip embedding models and Whisper audio models. Each Azure subscription has quotas that cap how much it can use. And not every model is offered in every region.
Companies want OpenAI's models, but on their own cloud terms.
Follow one request through Azure OpenAI.
- 1 · deployA team creates a resource in Azure and deploys a model, choosing a deployment type.
- 2 · sendThe app sends a prompt to the resource's own web address, and it can use OpenAI's own client library.
- 3 · filterA content filter checks the prompt for harmful content.
- 4 · generateThe model, hosted by Microsoft inside Azure, writes the completion.
- 5 · checkThe filter checks the completion too before the answer returns.
Same models, different host: Microsoft runs them inside Azure, not OpenAI.
| Who | What they ask | What it works with |
|---|---|---|
| Hospital IT team | “Can we summarise notes without our text reaching OpenAI or other customers?” | The data, privacy and security terms for models sold by Azure |
| Developer with OpenAI code | “How few lines must change to point our app at Azure?” | The v1 API and the OpenAI client library |
| European bank | “Can prompts be processed only inside the EU?” | A Data Zone deployment type |
| Support chatbot team | “Why did the service block that reply?” | Content filter categories and severity levels |
- It runs OpenAI models inside Microsoft's Azure cloud.
- It keeps prompts and answers away from other customers and from OpenAI.
- It adds content filters on both the prompt and the answer.
- It lets teams choose where prompts are processed and how they pay.
- Filters are automatic classifier models.
- The filter does not check embedding or Whisper audio models.
- Throughput is capped by quotas on your Azure subscription.
- Model choice varies by region, so not every model is everywhere.
Sources used
This explainer is written in original language. The links below support its factual claims.
- officialAzure OpenAI in Foundry Models, Microsoft Azure · read 28 Sept 2026
- docsFoundry Models sold by Azure, Microsoft Learn · read 28 Sept 2026
- docsData, privacy, and security for Models sold by Azure in Microsoft Foundry, Microsoft Learn · read 28 Sept 2026
- docsContent filtering for Microsoft Foundry Models (classic), Microsoft Learn · read 28 Sept 2026
- docsDeployment types for Microsoft Foundry Models, Microsoft Learn · read 28 Sept 2026
- docsAzure OpenAI in Microsoft Foundry Models v1 API, Microsoft Learn · read 28 Sept 2026
- docsAzure OpenAI quotas and limits, Microsoft Learn · read 28 Sept 2026