Duaer

Integrations

Set up Microsoft Foundry (Entra ID) credentials in Duaer

Store Microsoft Foundry (Entra ID) 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.

Connect to Azure OpenAI with Entra ID

The Duaer Azure Entra ID (Azure Active Directory) API credential lets the Azure OpenAI Chat Model node call with an app identity (client credentials) instead of an API key:

  1. In the Microsoft Entra admin center, create an app registration and put its Directory (tenant) ID and Application (client) ID in Tenant ID and Client ID. Create a client secret under Certificates & secrets and put it in Client Secret.
  2. In the Azure portal, under Access control (IAM) on the Azure OpenAI resource, assign the Cognitive Services OpenAI User role to the app.
  3. With Endpoint Type set to Classic, fill in Resource Name and API Version (the address is *.openai.azure.com). With Azure AI Foundry, put the full address, such as https://<resource>.services.ai.azure.com/openai/v1, in Endpoint.

Microsoft Foundry (Entra ID) fields in Duaer

In Duaer, choose Microsoft Foundry (Entra ID) when you create a credential, then fill in these fields:

  • Client ID (required)
  • Client Secret (required, secret)
  • Endpoint Type: Classic targets *.openai.azure.com (resource name + deployment-based URLs). Microsoft Foundry targets *.services.ai.azure.com/openai/v1 (full endpoint URL). Default: Classic. Options: Classic, Microsoft Foundry.
  • 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 Microsoft Foundry OpenAI-compatible base URL. Shown when Endpoint Type is Microsoft Foundry.
  • Project: Optional. The Microsoft Foundry project that owns your deployments. Duaer uses it to list the deployments. The project overview page in the Foundry portal shows the name. Shown when Endpoint Type is Microsoft Foundry.
  • Endpoint: Optional. Defaults to https://.openai.azure.com. Shown when Endpoint Type is Classic.
  • Tenant ID (required): The Directory (tenant) ID of the Entra app registration.

Duaer uses the OAuth2 Client Credentials grant for this type.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Duaer nodes that use it: Microsoft Foundry Embeddings, Microsoft Foundry Chat Model.

Save the connection in Duaer

Open Credentials and create Microsoft Foundry (Entra ID). 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 Microsoft Foundry (Entra ID) secret values appear in Duaer node parameters?

No. In Duaer, Microsoft Foundry (Entra ID) secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a Microsoft Foundry (Entra ID) 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 Microsoft Foundry (Entra ID) expects, then confirm you can create credentials in that project.

In this section