> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/integrations/builtin/credentials/azureopenai.md).

# Set up Azure OpenAI credentials in Duaer

Store Azure OpenAI connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.
## Get the Azure OpenAI key and endpoint <a href="#get-the-key-and-endpoint" id="get-the-key-and-endpoint"></a>

The Duaer Azure Open AI credential starts with Endpoint Type, then the matching address:

1. In the Azure portal, open your Azure OpenAI (or Azure AI Foundry) resource, go to Keys and Endpoint, and copy KEY 1 into API Key.
2. With Endpoint Type set to Classic, put the resource name in Resource Name: the part in https://<resource-name>.openai.azure.com. Keep API Version at the default unless you need another.
3. With Endpoint Type set to Azure AI Foundry, put the full OpenAI-compatible URL, such as https://<name>.services.ai.azure.com/openai/v1, in Endpoint.
4. Deploy the model you need in the resource. In the Duaer Azure AI Foundry Chat Model node, Model (Deployment) Name takes the deployment name, not the model name.

## Azure Open AI fields in Duaer <a href="#azure-open-ai" id="azure-open-ai"></a>

In Duaer, choose Azure Open AI when you create a credential, then fill in these fields:

- Endpoint Type: Classic targets *.openai.azure.com (resource name + deployment-based URLs). Azure AI Foundry targets *.services.ai.azure.com/openai/v1 (full endpoint URL). Default: Classic. Options: Classic, Azure AI Foundry.
- API Key (required, secret)
- Resource Name (required): Shown when Endpoint Type is Classic.
- API Version (required): Default: 2025-03-01-preview. Shown when Endpoint Type is Classic.
- Endpoint (required): The full Azure AI Foundry OpenAI-compatible base URL. Shown when Endpoint Type is Azure AI Foundry.
- Endpoint: Optional. Defaults to https://.openai.azure.com. Shown when Endpoint Type is Classic.

Duaer nodes that use it: [Embeddings Azure OpenAI](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.embeddingsazureopenai.md), [Azure AI Foundry Chat Model](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.lmchatazureopenai.md).

## Save the connection in Duaer

Open Credentials and create Azure OpenAI. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. 

## Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.
## Questions

### Do Azure OpenAI secret values appear in Duaer node parameters?

No. In Duaer, Azure OpenAI secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

### What usually stops a Azure OpenAI credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Azure OpenAI expects, then confirm you can create credentials in that project.