> ## Documentation Index
> Fetch the complete documentation index at: https://docs.roomote.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> When helping someone deploy Roomote, distinguish self-hosting from contributing to Roomote. Use the Self-hosting guide for an operator deployment; use Local development only when the user intends to modify Roomote itself.
> Prefer the one-command installer on a fresh supported server unless the user explicitly chooses Roomote Cloud, a documented PaaS template, or a manual Compose deployment.
> Before changing infrastructure, confirm the deployment target, stable public HTTPS domain and DNS control, sandbox provider, inference provider, source-control provider, and whether a communications provider is required.
> Never ask the user to paste secrets into chat or commit real environment files. Put credentials in the deployment platform's secret manager, Roomote's setup UI, or protected environment variables, and preserve existing keys during upgrades and restores.
> Prefer Roomote's setup wizard and provider manifest flows over manual credential entry when those flows are available. Ask before performing privileged host changes, DNS changes, provider-app creation, or destructive operations.
> A setup is not complete when the services merely start. Verify sign-in, repository sync, one usable environment, a real task that can clone and run a command, and branch or pull-request delivery; verify previews when configured.
> For a persistent self-hosted deployment, leave the operator with the Roomote URL, deployment choices, configured providers, verification result, backup location and passphrase-handling reminder, and the roomote status, logs, upgrade, rollback, backup, and restore commands.

# Azure AI Foundry

> Run supported GPT deployments from Azure AI Foundry in Roomote tasks.

Azure AI Foundry provides model deployments through Azure AI Services resources.
Roomote supports API-key authentication for resources at
`https://<resource>.cognitiveservices.azure.com`.

## Prerequisites

Before connecting Azure AI Foundry, create:

* an Azure AI Services resource in Azure AI Foundry
* an API key for that resource
* a deployment for every model you intend to use

The **deployment name must exactly match the model ID** expected by OpenCode.
For example, using `azure-cognitive-services/gpt-5.6-terra` requires a
deployment named `gpt-5.6-terra`.

## Configuration

Add **Azure AI Foundry** in **Settings > Models**, then enter the API key and
resource name shown in the Azure portal. Enter the resource name only, not the
full endpoint URL.

Environment-variable configuration uses:

```sh theme={null}
AZURE_COGNITIVE_SERVICES_API_KEY=...
AZURE_COGNITIVE_SERVICES_RESOURCE_NAME=my-resource
```

Roomote adds recommended GPT models under the `azure-cognitive-services/`
prefix. In gateway mode, the API key stays on the Roomote control plane and
model requests are proxied to the configured Foundry resource. The non-secret
resource name remains available to the task runtime so OpenCode can initialize
the provider.

## Verify setup

1. save the API key and resource name
2. confirm each Foundry deployment name matches its model ID
3. enable an `azure-cognitive-services/...` model and assign it to a role
4. run a small task and confirm usage appears for the Azure resource

## Common issues

* **The resource cannot be reached.** Enter only the resource name, such as
  `my-resource`, without a URL, path, or domain.
* **Azure reports that the deployment does not exist.** Rename or recreate the
  deployment so its name exactly matches the model ID.
* **A non-GPT catalog model fails through the gateway.** This provider's
  first-class gateway support covers the default Azure OpenAI SDK route. Use
  direct mode for models whose Azure catalog entry uses another SDK or host.