Migration changes for the omnichannel messaging platform
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 might refer to Power Virtual Agents while we update documentation and training content.
As part of the migration to the omnichannel messaging platform, we released a new bot service channel and chat SDK version to extend our messaging capabilities. To successfully migrate to the omnichannel messaging platform, you need to make the following changes to your omnichannel implementations:
If you have network policies in your organization, be sure to update your Omnichannel for Customer Service system requirements to include the domains that the omnichannel platform uses.
If you're using the Omnichannel Chat SDK to customize the live chat widget, download the latest version of the chat SDK package from GitHub. You need Omnichannel Chat SDK 1.1.0 or later to make sure that your widget works on the platform.
If you're integrating an Azure bot, connect and register your bot with the omnichannel messaging channel.
If you're using a Copilot Studio bot or Azure Health Bot, there's nothing you need to do. The necessary changes are applied automatically.
If you're a bot author or developer, download the latest middleware NuGet package.
If you've enabled downloading file attachments in chats, you must program your Azure bot to download file attachments properly in the omnichannel messaging channel.
Note
These changes won't impact your existing omnichannel experience. We'll work with you to help you navigate and test the changes to ensure a smooth transition.
Related information
Introduction to Omnichannel for Customer Service
Omnichannel for Customer Service system requirements
Develop a custom live chat widget
Customize live chat widgets for mobile apps
Integrate an Azure bot