Integrations
Use Microsoft Foundry Chat Model in Duaer
In Duaer, Microsoft Foundry Chat Model is an AI sub-node. Connect it to the Chat Model input of AI Agent, Basic LLM Chain, or another AI root node.
Connect Microsoft Foundry Chat Model in Duaer
- On the Duaer canvas, select the Chat Model input under AI Agent, Basic LLM Chain, or another AI root node and pick Microsoft Foundry Chat Model.
- Under Authentication, choose API Key or Azure Entra ID (OAuth2), then pick or create the matching credential (Microsoft Foundry (API Key) or Microsoft Foundry (Entra ID)) in Credential to connect with.
- Set Model (Deployment).
- If needed, select Add Option for the optional settings listed below.
- Run AI Agent. Microsoft Foundry Chat Model runs as part of it, and its calls show under that node in the execution.
Microsoft Foundry Chat Model parameters in Duaer
- Project: The Microsoft Foundry project that owns the deployment.
- Model (Deployment): The deployment to use.
- Model Family: The API family the deployment answers on.
Microsoft Foundry Chat Model options in Duaer
Under Add Option, Microsoft Foundry Chat Model offers Frequency Penalty, Maximum Number of Tokens, Response Format, Presence Penalty, Sampling Temperature, Timeout (Ms), Max Retries, Top P, and Extra Body.
Questions
Where does Microsoft Foundry Chat Model connect in Duaer?
In Duaer, Microsoft Foundry Chat Model connects to the Chat Model input of AI Agent, Basic LLM Chain, or another AI root node. It does not run on its own.
Which credential does Microsoft Foundry Chat Model use in Duaer?
Duaer's Microsoft Foundry Chat Model uses Microsoft Foundry (API Key) or Microsoft Foundry (Entra ID), depending on the method you choose under Authentication.
How do you pick a deployment for Microsoft Foundry Chat Model in Duaer?
A Foundry credential can pick the deployment from the list. A classic Azure OpenAI credential uses id and you type the deployment name. For a deployment that only serves the Responses API, turn on Use Responses API when Model Family is OpenAI.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.