For multilingual queue routing, Azure Conversational Language Understanding (CLU) intents (D) provide the optimal balance of capability, cost, and compliance. CLU is designed for robust, multilingual intent classification, is more accurate than simple keywords, and is significantly more performant and cost-effective than using a full generative model for a classification task. It operates within the tenant's Azure boundary, satisfying the data residency and no-new-connector constraints.

A. Standard NLP keyword routing: This is too simplistic and brittle to reliably handle diverse, multilingual customer intents for accurate routing.

B. Generative orchestration with tools and memory: This is excessive and inefficient for a routing task, violating cost targets and adding unnecessary latency.

C. Copilot Studio generative orchestration: Similar to option B, this uses a powerful but expensive and slower technology for a task better suited to a specialized classification service.

1. Microsoft Copilot Studio Documentation, "Use Microsoft Bot Framework skills or Azure CLU models for topic triggering," Section: Use a CLU model for NLU. This page explicitly describes using an external CLU model for more sophisticated natural language understanding and topic triggering (routing) in Copilot Studio.

2. Microsoft Azure AI Language Documentation, "Conversational language understanding (CLU) overview," Section: Multilingual support. This document confirms CLU's built-in capabilities for handling multiple languages within a single model, meeting a key requirement.

3. Microsoft Power Platform Documentation, "Connectors overview," Section: In-tenant vs. cross-tenant connections. Using Azure CLU within the same tenant ensures data stays within governed boundaries, as required.