Loading feed…
We Are .NET0 Hot0 comments3 min read
Jaliya's Blog: Using Azure AI Foundry resource for .NET Azure.AI.TextAnalytics and Azure.AI.Translation.Text Clients
Migrating .NET TextAnalyticsClient and TextTranslationClient from separate Azure AI Language and Translator resources to a single consolidated Azure AI Foundry (multi-service AIServices) endpoint causes TextTranslationClient to fail with a 404 Resource Not Found, while TextAnalyticsClient works fine. The root cause traces to Azure.AI.Translation.Text SDK's UriExtensions.IsPlatformHost check, which looks for the substring 'cognitiveservices' in the host to decide whether to append the '/translator/text' path prefix. Since the new Foundry endpoint uses 'services.ai.azure.com' instead of 'cognitiveservices.azure.com', the SDK skips the prefix and posts to the wrong path. The workaround is to manually append '/translator/text' to the endpoint URI when constructing TextTranslationClient. A related GitHub issue on azure-sdk-for-net (#61912) tracks the behavior for a possible fix.
Source: https://jaliyaudagedara.blogspot.com/2026/08/using-azure-ai-foundry-resource-for-net.html. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.
