# @pleach/transport-azure-openai (/docs/transport-azure-openai)



<Callout type="warn">
  **Not yet published.** `@pleach/transport-azure-openai` is marked
  `private` in this monorepo and is not on npm —
  `npm install @pleach/transport-azure-openai` will not resolve today.
  This page documents the planned surface; the package publishes in a
  later cut.
</Callout>

`@pleach/transport-azure-openai` is the Azure OpenAI Service
route for a Pleach session whose buyer reaches OpenAI models
through their Azure tenancy rather than the direct OpenAI API.
It implements the `AgentProvider` interface from `@pleach/core`
against Azure OpenAI's REST surface, so the cascade decisions
and audit shape are the same as any other provider — only the
transport and the credential source change.

## What it provides [#what-it-provides]

* An `AgentProvider` implementation against the Azure OpenAI
  Service per the `cloud-routed-agent.mdx` transport-vs-family
  split.
* Managed-identity credential resolution — workload-bound,
  short-lived tokens from the Azure identity layer, per the
  IAM-federated credentials section of `cloud-routed-agent.mdx`.
* Deployment-name routing, since Azure OpenAI's resource model
  addresses models by deployment name rather than vendor model
  id (`cloud-routed-agent.mdx` roadmap entry for this SKU).
* Azure-specific cost-event emission so the audit row carries
  the cloud, region, and deployment dimensions Azure Cost
  Management rolls up by.

## Where it fits [#where-it-fits]

`@pleach/transport-azure-openai` plugs into the same `provider`
slot on `SessionRuntime` that the direct-API providers fill — it
satisfies the `AgentProvider` contract documented in
[Providers](/docs/providers). For the architectural shape of a
cloud-routed deployment — transport vs family, IAM federation,
region as a hard constraint, cost reconciliation — see
[Cloud-routed agent](/docs/cloud-routed-agent).

## Install [#install]

```bash
npm install @pleach/transport-azure-openai
```

## API surface [#api-surface]

The provider factory signature, the managed-identity credential
option shape, the deployment-name routing fields, and the
emitted cost-event payload all live on the package's npm page:
[`@pleach/transport-azure-openai`](https://www.npmjs.com/package/@pleach/transport-azure-openai).
This page is placement orientation — what the SKU is for and
where it slots into the substrate. The npm README is the source
of truth for the constructor and option shapes; if a claim here
disagrees with the published README, the README wins.

## Where to go next [#where-to-go-next]

<Cards>
  <Card title="Cloud-routed agent" href="/docs/cloud-routed-agent" description="Transport-vs-family, IAM federation, region pinning, and cost reconciliation to the cloud invoice." />

  <Card title="Providers" href="/docs/providers" description="The AgentProvider contract this transport implements and the cascade rules it threads through." />

  <Card title="Multi-tenant SaaS agent" href="/docs/multi-tenant-saas-agent" description="Per-tenant runtime construction when each tenant reaches its own Azure tenancy." />
</Cards>