Licenses requirements for Copilot, Power pages Integration with Dynamics 365 Customer Service

In this blog, we are going to see the licenses needed for accessing or using the published copilot chatbot embedded in Power pages portal that connects to Dynamics 365 customer service.

To access or use the Copilot chatbot embedded in the Power Apps portal that connects to Dynamics 365 Customer Service, you typically need appropriate licenses from Microsoft that cover the following components:

1.     Dynamics 365 Customer Service License: This license allows users to access the Customer Service functionality within Dynamics 365, including managing cases, knowledge base, queues, and other customer service-related features.  Dynamics 365 Customer Service

·       Dynamics 365 Customer Service Professional $50.00 user/month

·       Dynamics 365 Customer Service Enterprise $95.00 user/month

2.      Power Pages License: Depending on the specifics of your implementation, you may need a Power Pages license that includes the ability to embed apps (like your chatbot) within portals. Common licenses include Power Pages Portal plans.

3.      Azure Bot Service (if applicable): If your Copilot chatbot is powered by Azure Bot Service, you might need relevant Azure licenses or subscriptions that allow hosting and interaction with the bot.

4.      Microsoft 365 License: In many cases, access to Dynamics 365 services is included or supplemented by Microsoft 365 licenses, which provide additional features such as collaboration tools and Office applications.

Compare Microsoft 365 Enterprise Plans | Microsoft 365

For exact details, it's advisable to consult with a Microsoft licensing specialist or your Microsoft representative. They can provide guidance based on your organization's specific needs, the scale of deployment, and any additional integrations or customizations involved.

Scenarios to use Virtual Table in Dataverse (Power Platform)

Virtual tables in Dataverse provide a way to access external data sources without requiring data replication or synchronization. Here are some business scenarios where virtual tables can be used in Dataverse: 

Consolidating Data from Multiple Systems: Many organizations use different systems to manage various parts of their business, such as sales, customer service, and finance. Virtual tables can be used to consolidate data from these systems into a single view within Dataverse. This can help organizations gain a better understanding of their business and make more informed decisions.  Real-Time Data Integration: Organizations that need to integrate data in real-time can use virtual tables to access external data sources. For example, an organization that needs to monitor inventory levels across multiple warehouses in real-time can use virtual tables to access data from their warehouse management system.  Simplified Reporting: Virtual tables can be used to simplify reporting by providing a single view of data across multiple systems. For example, an organization that needs to generate a report on customer orders can use virtual tables to access data from their sales system and customer relationship management (CRM) system.

Business Process Automation: Virtual tables can be used to automate business processes that require data from external systems. For example, an organization that needs to generate a purchase order when inventory levels fall below a certain threshold can use virtual tables to access data from their inventory management system.  External Data Integration: Organizations that need to integrate with external data sources, such as social media platforms, can use virtual tables to access data from these sources. For example, an organization that needs to analyze customer sentiment on social media can use virtual tables to access data from their social media monitoring tool.   At the same time, there are lots of limitations in using Virtual Tables. Those limitations are mentioned in this link: Consideration when we use virtual tables with Microsoft Dataverse