Replies: 1 comment 2 replies
-
|
Hi @gukoff thank you for detailing the custom domain issue you are facing, let me connect with the team and see if we can dig in further and respond back |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When AI Foundry has a custom domain name which is different from the AI Foundry's name, agent management is broken both on the Portal and when using Python SDK.
Here's an example screenshot from the Portal. Although my AI Foundry has a custom domain name and public network access disabled, Portal tries to interact with it using its regular domain name:
An error in a similar spirit I get when I try to deploy an agent to this AI Foundry. Foundry API itself returns a broken non-JSON response
Name or service not known (aiscxhcg.openai.azure.com:443), suggesting that internally the agent management API does not know to call the custom domain name.Is this a known limitation/bug?
Beta Was this translation helpful? Give feedback.
All reactions