Get started with conversational language understanding integration
Important
Power Virtual Agents capabilities and features are now part of Microsoft Copilot Studio following significant investments in generative AI and enhanced integrations across Microsoft Copilot.
Some articles and screenshots may refer to Power Virtual Agents while we update documentation and training content.
This article includes the step-by-step procedures you need to get started with conversational language understanding (CLU) integration. Let’s get started.
To create a copilot using an existing CLU model:
- Prepare your environment.
- Prepare your conversational language understanding project.
- Map CLU intents and entities.
Prepare your environment
Before you begin, make sure that you have your CLU model project name, deployment name, Cognitive Services account key, and site URL for Azure Cognitive Service for Language.
Create a new Microsoft Copilot Studio copilot.
Note
Ensure the environment for your copilot has been created in a region supported by Microsoft Copilot Studio and which has an equivalent CLU region.
Not all regions supported by Microsoft Copilot Studio have an equivalent CLU region.
With your copilot open, expand Settings on the side navigation pane and select Language understanding.
Note
If you have already enabled a CLU connection, skip to step 8.
Note
If you you see the following, then you are not connected to Azure Cognitive Service for Language. Follow steps 3-7 to connect.
To create a new connection, from within Power Apps, open the Connections menu by selecting ...More and then Connections.
Select New connection and search for Azure Cognitive Service for Language. You are taken to an authentication settings page.
Select API key for authentication type, enter account key and site URL, then select Create.
To view the connection in the Connections list, select the Azure Cognitive Service for Language connector and select Edit in the More commands menu.
Change the display name to something else to distinguish it from other CLU connectors. The name you enter to change can be any name you choose. With the connector created and configured in Power Apps, you can return to your Microsoft Copilot Studio copilot.
In the Language understanding tab in Copilot Studio, choose Microsoft Copilot Studio NLU from the NLU Resource drop-down list.
Choose the display name you chose earlier for the CLU connector, then select Save. A Delete example trigger phrases? window opens.
Select Save snapshot. Saving a snapshot saves the copilot content, including trigger phrases and bot dialogues into a backlog file in YAML format. Select Yes, delete my trigger phrase and then select Continue.
Enter your project name and deployment information, and select Save.
In Microsoft Copilot Studio, on the Language understanding tab, select Save. Changing the NLU configuration removes the Analyze text system topic. It also requires you to manually add example phrases for topics currently mapped to external intents.
Now that you’re done preparing your environment, you’re ready to map intents and entities to CLU model data.
Prepare your conversational language understanding project
If you don't have an Azure subscription, create a free account before you begin.
Then create a language resource in Language Studio, with the conversational language understanding feature enabled.
To ensure Copilot Studio functions correctly, you need to create intents for Copilot Studio system topics and for any custom topics you want to create.
Author any custom entities you want to use in your Microsoft Copilot Studio project.
Train and deploy the project in the same region as your Microsoft Copilot Studio resource.
Map CLU intents and entities to Microsoft Copilot Studio prebuilt data types
You create a new Microsoft Copilot Studio copilot by mapping existing topics to CLU intents. You can manually map intents and entities, or for bulk mapping, see Use the Bulk tool wizard.
Manually map intents
Open your Microsoft Copilot Studio copilot.
From the left navigation, select Topics and plugins and select an intent.
In the Phrases section of the Trigger node for the intent, select the Edit link.
In the Add phrases box, enter the name of the CLU intent that you want to map to.
Note
The CLU intent name must be typed exactly as stored in the CLU model, including matching case as uppercase and lowercase characters.
To save the intent, click the + (plus) sign to the right of the Add phrases box.
Repeat for the other intents.
Manually map entities:
Open your Microsoft Copilot Studio copilot.
From the left navigation, select Entities.
Select New entity on the Entities page.
In the New entity pane, Add a name, description (optional), and Data Type for your entity.
To access CLU prebuilt entities, from the Data Type drop-down menu, select From sample data, and choose one of the CLU prebuilt JSON code snippets.
(Optional) If you want to import JSON schema from a sample file, choose Get schema from sample JSON to access the external file.
Use the Bulk tool wizard
You create a new copilot by bulk mapping existing topics to CLU intents using the Map intents and entities wizard. With the wizard, your copilot can automatically utilize existing intents from your CLU model rather than trigger phrases to determine which topic to map to.
Begin by uploading your CLU model data file and automatically map CLU intents to your Microsoft Copilot Studio copilot.
From the left navigation, select Language, then Add topics and entities from model data.
In the File name option, select Choose file to select the data file from which you want to upload your CLU model.
You then see your model data file in the Preview window. Select Next to continue.
select Add intents and entities.
In the Map existing topics to CLU intents screen, choose a CLU intent to map to the corresponding article.
Review your selections, then select Save.
(Optional) For those intents that aren't mapped to an existing topic, you can create new topics for each intent. In the wizard, you can see a list of CLU intents that are not yet mapped to a topic. In the field Create a new topic, enter a name for each of the topics that you want to create, and then select Next.
Note
Any fields that you leave blank are ignored by the wizard.
Once all CLU intents and entities are mapped to Microsoft Copilot Studio topics, select Done.
Once you are done with this procedure, your copilot topics now appear in the Microsoft Copilot Studio Topics pane. For more information, see Managing topics.
Related topics
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for