{"id":954,"date":"2025-06-03T15:20:12","date_gmt":"2025-06-03T22:20:12","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/foundry\/?p=954"},"modified":"2025-08-25T14:11:14","modified_gmt":"2025-08-25T21:11:14","slug":"enhancing-conversational-agents-with-azure-ai-language-conversational-language-understanding-and-custom-question-answering","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/foundry\/enhancing-conversational-agents-with-azure-ai-language-conversational-language-understanding-and-custom-question-answering\/","title":{"rendered":"Enhancing Conversational Agents with Azure AI Language Conversational Language Understanding and Custom Question Answering"},"content":{"rendered":"<p><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">As we focus our work on empowering the agent design experience, a list of the new features in the we published earlier this week, including the\u00a0<a href=\"https:\/\/github.com\/azure-ai-foundry\/foundry-samples\/tree\/main\/samples\/agent-catalog\/msft-agent-samples\/foundry-agent-service-sdk\/intent-routing-agent\">intent triage agent\u00a0<\/a>and the\u00a0<a href=\"https:\/\/github.com\/azure-ai-foundry\/foundry-samples\/tree\/main\/samples\/agent-catalog\/msft-agent-samples\/foundry-agent-service-sdk\/exact-qna-agent\">exact question-answering agent<\/a>, utilizing <a href=\"https:\/\/learn.microsoft.com\/en-us\/azure\/ai-services\/language-service\/conversational-language-understanding\/overview\">Conversational language understanding (CLU)<\/a> and <a href=\"https:\/\/learn.microsoft.com\/en-us\/azure\/ai-services\/language-service\/question-answering\/overview\">Custom question answering (CQA)<\/a>. We\u2019re excited to share new enhancements to the customization experiences in CLU and CQA that are officially available today.<\/span><\/p>\n<h1><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">Customization in AI Foundry<\/span><\/h1>\n<p><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">We\u2019re excited to announce that both Conversational Language Understanding (CLU) and Custom Question Answering (CQA) are now fully integrated into the AI Foundry, unlocking powerful new customization capabilities for building intelligent agents.\u00a0With the growing need for multi-modal intelligence, you can now manage all of your Azure AI models in a single place. Now, AI developers and business stakeholders can fine-tune custom multilingual language models with the powerful unified user experience in the AI Foundry. From fine-tuning task setup to AI model deployment, language model customization has never been more robust or more efficient.<\/span><\/p>\n<p><figure id=\"attachment_955\" aria-labelledby=\"figcaption_attachment_955\" class=\"wp-caption alignnone\" ><a href=\"https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Fine-Tuning-Page-1.png\"><img decoding=\"async\" class=\" wp-image-955\" src=\"https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Fine-Tuning-Page-1.png\" alt=\"Navigation steps for AI Services Fine Tuning \" width=\"1305\" height=\"771\" srcset=\"https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Fine-Tuning-Page-1.png 2500w, https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Fine-Tuning-Page-1-300x177.png 300w, https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Fine-Tuning-Page-1-1024x605.png 1024w, https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Fine-Tuning-Page-1-768x454.png 768w, https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Fine-Tuning-Page-1-1536x908.png 1536w, https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Fine-Tuning-Page-1-2048x1210.png 2048w\" sizes=\"(max-width: 1305px) 100vw, 1305px\" \/><\/a><figcaption id=\"figcaption_attachment_955\" class=\"wp-caption-text\"><em style=\"font-size: 16px;\"><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">Figure 1 &#8211; Three easy steps for language fine-tuning in AI Foundry<\/span><\/em><\/figcaption><\/figure><\/p>\n<h1><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">Smart Intent Routing with CLU<\/span><\/h1>\n<p><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">The Intent Triage Agent is powered by CLU, which enables you to build custom natural language understanding models in over 100 languages to predict the overall intent of an utterance and extract important information from it quickly and accurately.<\/span><\/p>\n<p><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">We\u2019re announcing new features to empower your agent-building <strong>experience<\/strong>:<\/span><\/p>\n<ul>\n<li><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\"><strong>Deploy CLU Faster with AOAI<\/strong>: CLU authoring now offers two options for designing and deploying your custom CLU model:<\/span>\n<ul>\n<li><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\"><strong>Quick Deploy (Option #1):<\/strong> This new feature allows you to <a href=\"https:\/\/learn.microsoft.com\/en-us\/azure\/ai-services\/language-service\/conversational-language-understanding\/how-to\/deploy-model?tabs=language-studio\">deploy a CLU model<\/a> with just your list of intents and a plain text description of each intent. This LLM-powered configuration allows you to see your agent in action without requiring any training of machine learning models. Even with this LLM-approach, you still get access to the structured JSON CLU output that allows your agents and workflows to understand the AI prediction. This option is best to use when you want to get started quickly and want to understand a broad spectrum of topics with open-ended text.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><figure id=\"attachment_957\" aria-labelledby=\"figcaption_attachment_957\" class=\"wp-caption alignnone\" ><a href=\"https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Quick-Deploy-Page.png\"><img decoding=\"async\" class=\" wp-image-957\" src=\"https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Quick-Deploy-Page.png\" alt=\"Quick Deploy Page image\" width=\"880\" height=\"465\" srcset=\"https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Quick-Deploy-Page.png 2014w, https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Quick-Deploy-Page-300x159.png 300w, https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Quick-Deploy-Page-1024x541.png 1024w, https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Quick-Deploy-Page-768x406.png 768w, https:\/\/devblogs.microsoft.com\/foundry\/wp-content\/uploads\/sites\/89\/2025\/06\/Quick-Deploy-Page-1536x812.png 1536w\" sizes=\"(max-width: 880px) 100vw, 880px\" \/><\/a><figcaption id=\"figcaption_attachment_957\" class=\"wp-caption-text\"><em><span style=\"font-family: tahoma, arial, helvetica, sans-serif; font-size: 16px;\">Figure 2 &#8211; Deploy CLU quickly the power of LLMs in the new Quick Deploy feature<\/span><\/em><\/figcaption><\/figure><\/p>\n<ul>\n<li style=\"list-style-type: none;\">\n<ul>\n<li style=\"list-style-type: none;\">\n<ul>\n<li><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">Here are some tips for creating intents and descriptions with the Quick Deploy option:<\/span>\n<ul>\n<li><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\"><strong>Ensure your resource has the correct access.<\/strong> In the Azure Portal, be sure your AI Foundry resource has the Cognitive Services User role assigned to the resource containing the AOAI deployment. This access is required even if you are using a single AI Foundry resource (by providing this role assignment to itself). If you are using CLU with a Language resource, you should assign the Cognitive Services User role assignment to the AOAI Resource.\u00a0<\/span><\/li>\n<li><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\"><strong>Use clear and concise intent names. <\/strong>Choose intent names that resemble natural language expressions. Limit them to 2-3 words and format them using either camelCase (e.g. bookFlight) or underscore_separated (e.g. check_order_status) styles.<\/span><\/li>\n<li><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\"><strong>Provide a focused description.<\/strong> Each intent should include a brief definition (ideally 1-2 sentences) that clearly explains its purpose. Aim for 50\u2013100 characters to strike a balance between clarity and processing efficiency. However, longer descriptions are also supported if needed.<\/span><\/li>\n<li><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">If you\u2019d like, <strong>include a few carefully selected example utterances<\/strong> for each intent to help your LLM understand how users might naturally express their intent. This is not required for the Quick Deploy option, but it can help the model predict a user\u2019s intent even better.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\"><strong>Customization with Machine Learning (Option #2): <\/strong>CLU continues to offer state-of-the-art model training for when you\u2019re looking for a context-specific, low-latency, deterministic model for more control in your intent classification. While this feature can take a little more time during model training, this machine learning approach offers additional enhancements, like model performance evaluation, prediction confidence scoring, on-prem container support, and world-class entity recognition. This option is best to use when you\u2019re looking for more control during inference time.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">With either model deployment option, you can see your prediction results in action in the AI Foundry playground. These features make the intent triage agent a game-changer for teams looking to scale intelligent routing across complex conversational flows.<\/span><\/p>\n<h1><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">Answer Questions with Precision with CQA<\/span><\/h1>\n<p><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">The exact question-answering agent is powered by <a href=\"https:\/\/learn.microsoft.com\/en-us\/azure\/ai-services\/language-service\/question-answering\/overview\">Custom Question Answering (CQA)<\/a>, which lets you build AI systems that can accurately respond to user questions by extracting answers from your own content, like documents, websites, or knowledge bases, tailored to your specific business needs. In addition to <a href=\"https:\/\/techcommunity.microsoft.com\/blog\/azure-ai-services-blog\/announcing-azure-ai-language-new-features-to-accelerate-your-agent-development\/4415216\">the new authoring experience in the Azure AI Foundry portal that we announced earlier this week<\/a>, today we\u2019re also announcing a few enhancements to CQA to improve the model prediction experience. First, CQA now offers exact match answering, for when a user asks a question identical to a question answering pair regardless of the score. Last, CQA now supports the same scoring available in QnA Maker, providing more flexibility for you to choose between the CQA ranking algorithms and the familiar scoring logic from QnA Maker, based on your use case.<\/span><\/p>\n<p><span style=\"font-family: tahoma, arial, helvetica, sans-serif;\">empower developers to build agents that not only understand but also respond with confidence and clarity. For more information, check out our Agents blogpost, <a href=\"https:\/\/github.com\/azure-ai-foundry\/foundry-samples\/tree\/main\/samples\/agent-catalog\/msft-agent-samples\/foundry-agent-service-sdk\/exact-qna-agent\">Agent Template GitHub repo<\/a> for the <a href=\"https:\/\/github.com\/azure-ai-foundry\/foundry-samples\/tree\/main\/samples\/agent-catalog\/msft-agent-samples\/foundry-agent-service-sdk\/intent-routing-agent\">intent triage agent<\/a> and <a href=\"https:\/\/github.com\/azure-ai-foundry\/foundry-samples\/tree\/main\/samples\/agent-catalog\/msft-agent-samples\/foundry-agent-service-sdk\/exact-qna-agent\">exact question-answering agent<\/a>, and Microsoft learn documentation.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>As we focus our work on empowering the agent design experience, a list of the new features in the we published earlier this week, including the\u00a0intent triage agent\u00a0and the\u00a0exact question-answering agent, utilizing Conversational language understanding (CLU) and Custom question answering (CQA). We\u2019re excited to share new enhancements to the customization experiences in CLU and CQA [&hellip;]<\/p>\n","protected":false},"author":190874,"featured_media":1563,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[45,1],"tags":[10,16,31,47,46,48,44,34],"class_list":["post-954","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure-ai-services","category-microsoft-foundry","tag-ai-agents","tag-ai-applications","tag-azure","tag-azure-ai-language","tag-azure-ai-services","tag-conversational-ai","tag-azure-ai-foundry-labs","tag-microsoft-build"],"acf":[],"blog_post_summary":"<p>As we focus our work on empowering the agent design experience, a list of the new features in the we published earlier this week, including the\u00a0intent triage agent\u00a0and the\u00a0exact question-answering agent, utilizing Conversational language understanding (CLU) and Custom question answering (CQA). We\u2019re excited to share new enhancements to the customization experiences in CLU and CQA [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/foundry\/wp-json\/wp\/v2\/posts\/954","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/foundry\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/foundry\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/foundry\/wp-json\/wp\/v2\/users\/190874"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/foundry\/wp-json\/wp\/v2\/comments?post=954"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/foundry\/wp-json\/wp\/v2\/posts\/954\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/foundry\/wp-json\/wp\/v2\/media\/1563"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/foundry\/wp-json\/wp\/v2\/media?parent=954"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/foundry\/wp-json\/wp\/v2\/categories?post=954"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/foundry\/wp-json\/wp\/v2\/tags?post=954"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}