Extend Copilot capabilities with plugins   

Extend Copilot capabilities with plugins   

This article is contributed. See the original author and article here.

In Dynamics 365 Customer Service, agents use Copilot to resolve issues based on the corpus of data in their organization’s knowledge base or SharePoint. Additionally, we are introducing prompt plugins, enabling agents to securely access Dataverse data such as customers, products, and cases, through Copilot. This enables agents to gain a better understanding of customer needs, preferences, and history, which empowers them to provide more personalized and effective support. 

With Copilot Studio, we enable customers to build and manage their prompt plugins to address various types of customer scenarios based on the organization’s needs. Plugins reduce the need for customer service representatives to switch to other tabs and tools to do their work. The result is improved resolution time and customer satisfaction. Organizations can build a single plugin and use that plugin in all copilots. So, regardless of where an agent asks a service-related question, they benefit from a consistent experience. 

Create prompt plugins

You can create a prompt plugin using Copilot Studio and choose the data from Dataverse based on your needs.  

graphical user interface, application, email

Once you generate prompt plugins, the Customer Service administrator can manage plugins in the Customer Service admin center.

Administrators have the following capabilities:

  • Turn on and turn off the plugins
  • Provide access to all Copilot users or manage user access by roles
  • Map data field input parameters for the plugin, reducing how much context agents have to manually add to the prompt during plugin use
  • Manage the plugin data storage in Dataverse

Use prompt plugins

Empower agents to access solutions from multiple entities through Copilot, offering unified and enlightening experience. Agents can use targeted phrases in Copilot to get responses from plugins to quickly gather information about a case.

Copilot automatically identifies the plugin based on the agent’s question. With deep understanding of the user’s intent, Copilot can select the right plugin to help the agent, resulting in better experience for customers who have their issues addressed faster.

When the agent clicks Check sources, they can see the plugin used to generate the response. They can also click the Learn about plugins documentation link to understand how plugins work and their use in Copilot.

If Copilot didn’t identify a plugin, it falls back to the knowledge source to create a response to the agent.

graphical user interface, text, application

Coming soon: Other types of plugins

Connector plugins extend Copilot’s value by connecting to a variety of external data sources and applications that agents rely on to answer customer queries. The plugins let your agents securely access data from those systems through Copilot without juggling multiple different systems to deliver service. For example, the agents can retrieve information like purchase orders and shipping details via Copilot without logging in to order management systems. The agents simply ask for what they need, and Copilot responds, resulting in decreased time to resolution.

Learn more

Below are the detailed steps to create and configure prompt plugins for your organization.

  1. Create prompt plugins in Copilot Studio
  2. Configure plugins in Customer Service admin center
  3. Use plugins in Copilot in Dynamics 365 Customer Service

The post Extend Copilot capabilities with plugins    appeared first on Microsoft Dynamics 365 Blog.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

Extend Copilot capabilities with plugins   

Extend Copilot capabilities with plugins   

This article is contributed. See the original author and article here.

In Dynamics 365 Customer Service, agents use Copilot to resolve issues based on the corpus of data in their organization’s knowledge base or SharePoint. Additionally, we are introducing prompt plugins, enabling agents to securely access Dataverse data such as customers, products, and cases, through Copilot. This enables agents to gain a better understanding of customer needs, preferences, and history, which empowers them to provide more personalized and effective support. 

With Copilot Studio, we enable customers to build and manage their prompt plugins to address various types of customer scenarios based on the organization’s needs. Plugins reduce the need for customer service representatives to switch to other tabs and tools to do their work. The result is improved resolution time and customer satisfaction. Organizations can build a single plugin and use that plugin in all copilots. So, regardless of where an agent asks a service-related question, they benefit from a consistent experience. 

Create prompt plugins

You can create a prompt plugin using Copilot Studio and choose the data from Dataverse based on your needs.  

graphical user interface, application, email

Once you generate prompt plugins, the Customer Service administrator can manage plugins in the Customer Service admin center.

Administrators have the following capabilities:

  • Turn on and turn off the plugins
  • Provide access to all Copilot users or manage user access by roles
  • Map data field input parameters for the plugin, reducing how much context agents have to manually add to the prompt during plugin use
  • Manage the plugin data storage in Dataverse

Use prompt plugins

Empower agents to access solutions from multiple entities through Copilot, offering unified and enlightening experience. Agents can use targeted phrases in Copilot to get responses from plugins to quickly gather information about a case.

Copilot automatically identifies the plugin based on the agent’s question. With deep understanding of the user’s intent, Copilot can select the right plugin to help the agent, resulting in better experience for customers who have their issues addressed faster.

When the agent clicks Check sources, they can see the plugin used to generate the response. They can also click the Learn about plugins documentation link to understand how plugins work and their use in Copilot.

If Copilot didn’t identify a plugin, it falls back to the knowledge source to create a response to the agent.

graphical user interface, text, application

Coming soon: Other types of plugins

Connector plugins extend Copilot’s value by connecting to a variety of external data sources and applications that agents rely on to answer customer queries. The plugins let your agents securely access data from those systems through Copilot without juggling multiple different systems to deliver service. For example, the agents can retrieve information like purchase orders and shipping details via Copilot without logging in to order management systems. The agents simply ask for what they need, and Copilot responds, resulting in decreased time to resolution.

Learn more

Below are the detailed steps to create and configure prompt plugins for your organization.

  1. Create prompt plugins in Copilot Studio
  2. Configure plugins in Customer Service admin center
  3. Use plugins in Copilot in Dynamics 365 Customer Service

The post Extend Copilot capabilities with plugins    appeared first on Microsoft Dynamics 365 Blog.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

Have a safe coffee chat with your documentation using Azure AI Services | JavaScript Day 2024

Have a safe coffee chat with your documentation using Azure AI Services | JavaScript Day 2024

This article is contributed. See the original author and article here.

image.png


 


In the Azure Developers JavaScript Day 2024, Maya Shavin a Senior Software Engineer at Microsoft, presented a session called “Have a safe coffee chat with your documentation using Azure AI Services”. And she introduced innovative approaches for integrating AI technologies to ensure the safety of document-based Q&A systems.


 


Let’s dive into the content!


 


What was covered during the session?


 


Now let’s talk about what was covered during the session! If you wish, you can watch the video of the session at the link below:


 



 


 


Introduction to AI-Powered Safety in Documentation


 


Maya opened her presentation by introducing her background in Microsoft’s industrial AI division, where she focuses on incorporating AI technologies into industry-specific applications. With over a decade of experience in both Front-End and Back-End development, she also highlighted her contributions to the Tech Community as an author and Community Organizer.


 


Concept of Document Q&A Assistant


 


Maya described the document Q&A assistant as a straightforward interaction system where an AI, not a human, responds to user queries. The system processes in two primary phases:


 



  1. Injection Phase: here, documents are uploaded, segmented, indexed with metadata and stored in a searchable database.

  2. Query Phase: the phase where the AI retrieves and summarizes relevant document sections in response to user queries.


 


querying-injection.png


 


 


The Importance of Content Moderation


 


A significant portion of her talk focused on content moderation, crucial for preventing inappropriate or harmful content from undermining the AI system’s integrity. She explained how AI responses could potentially reflect, or be influenced by, the offensive content within user inputs. To combat this, Microsoft promotes responsible AI practices structured around in:


 



  • Fairness: AI systems should treat all people fairly.

  • Reliability and safety: AI systems should perform reliably and safely.

  • Privacy and security: AI systems should be secure and respect privacy.

  • Inclusiveness: AI systems should empower everyone and engage people.

  • Transparency: AI systems should be understandable.

  • Accountability: People should be accountable for AI systems.


 


For more information on Microsoft’s Responsible AI Practices, visit the link.


 


Azure AI Content Safety


 


Maya introduced Azure AI Content Safety, a pivotal service for detecting harmful content in both user inputs and AI-generated responses. This service supports multiple programming languages and offers a studio experience for testing various content sensitivity levels. Its primary features include:


 




  • Text Analysis API: Scans text for sexual content, violence, hate, and self-harm with multi-severity levels.




  • Image Analysis API: Scans images for sexual content, violence, hate, and self-harm with multi-severity levels.




  • Text Blocklist Management APIs: The default AI classifiers are sufficient for most content safety needs; however, you might need to screen for terms that are specific to your use case. You can create blocklists of terms to use with the Text API.




 


To understand how Azure AI Content Safety works, there’s a video below about the service:


 



 


Demonstrating Azure AI Content Safety in Action


 


Maya demonstrated how to integrate Azure AI Content Safety into a JavaScript project. She showcased a function that analyzes content and adjusts responses based on predefined sensitivity levels, thus preventing the system from providing harmful output.


 


This function works by categorizing content into several types of sensitive material—like hate speech, sexual content, and violence—and filtering them accordingly.


 


She also mentioned the use of the Azure AI Content Safety SDK for JavaScript/TypeScript, which you can find at the link


 


Comparing Azure AI Content Safety and Azure OpenAI Content Filters


 


Maya also compared the Azure AI Content Safety with OpenAI’s content filtering features. She highlighted that while Azure AI Content Safety is versatile and can be integrated into various AI workflows, OpenAI’s content filtering is bundled with their services and might not incur additional costs.


 


However, Azure AI Content Safety offers more control over the moderation process and supports more languages.


 


Final Thoughts and Steps Forward


 


Concluding her talk, Maya stressed the ongoing need for manual oversight in content moderation to ensure that AI interactions remain appropriate and effective. She encouraged attendees to implement Azure AI content safety in their projects to enhance the security layers of their AI applications.


 


Maya Shavin’s session provided valuable insights into the mechanisms of safeguarding AI-driven document assistants, ensuring that they operate within the realms of safety and ethics dictated by modern AI standards.


 


Azure Developers JavaScript Day Cloud Skills Challenge


 


Don’t forget to participate in the Azure Developers JavaScript Day Cloud Skills Challenge to test your knowledge and skills in a series of learn modules and learn more about Azure services and tools. As I mentioned in the previous articles, besides the challenge is over, you can still access the content and learn more about the topics covered during the event.


 


image-6.png


 


Link to the challenge: JavaScript and Azure Cloud Skills Challenge


 


Additional Resources


 


If you want to learn more about Azure AI Content Safety Services, especially if you’re JavaScript Developer, you can access the following resources:



 


Stay Tuned!


 


If you wish, you can follow what happened during the two days of the event via the playlist on YouTube. The event was full of interesting content and insights for JavaScript developers!


 


If you are a JavaScript/TypeScript developer, follow me on Twitter or LinkedIn Glaucia Lemos for more news about the development and technology world! Especially if you are interested in how to integrate JavaScript/TypeScript applications with the Azure, Artificial Intelligence, Web Development, and more!


 


And see you in the next article! 

Introducing Single Sign-On (SSO) for Sensor Console: Enhanced Security and Streamlined Access

Introducing Single Sign-On (SSO) for Sensor Console: Enhanced Security and Streamlined Access

This article is contributed. See the original author and article here.

We are excited to announce the release of Single Sign-On (SSO) for the Defender for IoT Sensor Console! This powerful feature simplifies the login process, enhances security, and provides a seamless experience for all users. Let’s dive into the details: 


 


What’s New? 


 


SSO Support on the sensor console 


 


With SSO, users can log in once and gain access to the sensor console without the hassle of re-entering credentials.  


 


Figure 1: Defender for IoT login pageFigure 1: Defender for IoT login page


New integration with Microsoft Entra ID 


 


By using Entra ID, your organization ensures consistent access controls across different sensors and sites. SSO simplifies onboarding and offboarding processes, reduces administrative overhead, and strengthens security. 


 


Getting Started


Ready to set up SSO for your sensor console?  


 


Follow this step-by-step guide by visiting our documentation:  Set up single sign-on for Microsoft Defender for IoT sensor console. 


 


Learn More 


What’s new in Microsoft Defender for IoT? 


 


Get ready to experience enhanced security and seamless access with SSO for the Sensor Console. If you have any questions, feel free to comment below!

Enabling fast, flexible, cost-effective service with Microsoft Copilot in Dynamics 365 Field Service

Enabling fast, flexible, cost-effective service with Microsoft Copilot in Dynamics 365 Field Service

This article is contributed. See the original author and article here.

This post was co-authored by Safiyyah O’Quinn, Senior Product Marketing Manager and Ghazanfar Riaz, Head of Digital Consulting, Visionet

Fast, efficient service, it’s what everybody wants. And today’s field service organizations are answering the call by adopting next-generation AI technologies that can help them be more flexible and responsive to customers while also driving revenue, reducing overtime, and ensuring more predictable arrival and completion times. Service managers, field technicians, and customers all benefit.

Streamlining work order and resource management to improve service metrics is always top of mind for field service managers. Microsoft Copilot in Dynamics 365 Field Service brings the power of next-generation AI to field service managers, enabling them to automate work order management and optimize scheduling with data-driven recommendations based on travel time, resource availability, and skill sets. Recently, we announced new capabilities in the Microsoft Dynamics 365 Field Service web app that enable field managers to interact with Copilot using natural language to find pertinent information about work orders. Copilot can assist in retrieving work order details, summarizing them, and presenting them in an easily digestible format. Copilot can also go beyond searching work orders to searching other Microsoft Dataverse records including accounts, contacts, opportunities, and more. In addition, field service managers can now configure data that Copilot uses to generate work order summaries in Dynamics 365 Field Service for more advanced reviews before closing work orders to ensure they’re meeting customer needs.

Resource Scheduling Optimization (RSO) is an add-in to Dynamics 365 Field Service that automatically suggests the technicians, equipment, and facilities (such as warehouses) best equipped to handle a given job. Ghazanfar Riaz, Head of Digital Consulting at Visionet, a Microsoft Managed Partner, believes that having the ability to extend Field Service in conjunction with Resource Scheduling Optimization and Microsoft Copilot Studio can help service organizations be more customer-centric, flexible, and efficient.

“Dynamics 365 Field Service has catalyzed a shift towards smarter, more efficient field services management. With the integration of Microsoft Copilot into Dynamics 365 Field Service, service organizations are now more equipped to consistently exceed customer expectations and build long-lasting relationships at every point of interaction.”

Ghazanfar Riaz, Head of Digital Consulting, Visionet

Microsoft’s latest update to Dynamics 365 Field Service introduces enhanced Copilot capabilities, designed to serve as a field service manager’s AI assistant. Using natural language, managers can now converse with Copilot to swiftly extract essential details and summaries from work orders and transform complex data into clear, actionable insights. Field service managers can also use Copilot to adeptly navigate Dataverse records, including accounts, contacts, and opportunities, for a more holistic view of the customer landscape.

Additionally, field service managers can tailor how Copilot generates work order summaries to help ensure the best possible schedules for field technicians and the best possible outcomes for customers. By using Copilot in Dynamics 365, field service management becomes a more intuitive and intelligent experience, ensuring customer needs are not just understood but anticipated and met.

Let’s take a closer look at how Visionet extended Dynamics 365 Field Service and RSO capabilities to achieve a more customized, adaptable system and greater efficiency in resource scheduling scenarios.

Optimizing schedules for field service technicians

With rising customer expectations, many service organizations have opted to supplement their operations by using contractors or other third-party services to address any gaps in service. In these cases where contractors or third parties are involved, knowing what resources to use—especially when automating resource scheduling for efficiency—can be tricky and time consuming. In addition, contractors and third-party resources are often more expensive than in-house technicians, so many service organizations want to ensure they’re using those resources strategically.

Service managers often find themselves manually reallocating contractors or other third-party resources, consuming valuable time. Visionet identified an opportunity to enhance Field Service RSO, which facilitates automated schedule creation, by extending its capabilities to offer improved scheduling insights and enable automation on a larger scale.  Service managers can efficiently assign bookings by setting preferences for factors such as cost (weighing the use of in-house technicians against contractors), skill set, territory, and availability. With these preferences established, service managers and dispatchers can use this enhanced RSO feature to optimize daily or weekly schedules more effectively and generate precise recommendations.

Visionet is collaborating with service organizations to further augment Field Service RSO by integrating Copilot automation capabilities. Using natural language interactions, field service managers can quickly pinpoint specific resources or assets needed for jobs. This helps ensure that work orders are evenly distributed, skill sets are appropriately matched to tasks, and more costly resources are employed judiciously to maintain cost efficiency.

Managing downtime for field service technicians

Downtime for field technicians, particularly when it’s unexpected, can disrupt service and revenue. Service managers often find themselves needing to reorganize schedules due to unforeseen circumstances such as illness, emergency calls, mandatory training, or meetings that prevent technicians from being in the field. Recognizing this challenge, Visionet enhanced the Field Service RSO by incorporating customizations that improve scheduling flexibility.

Now, service managers can specify planned, non-productive events like mandatory training sessions, weekly team meetings, work breaks, and other time off directly within the system and specify whether they are one-time or recurring. The RSO uses this information to automatically adjust schedules accordingly and ensure no service interruptions occur.

Responding in real time to daily schedule changes

For many service organizations, things can change from minute to minute. Customers can experience outages due to weather, utility maintenance, road construction—the possibilities are endless. In addition, field technicians can get held up by traffic or an accident on the freeway, or even by a customer issue that was more complicated than what was initially scoped. And sometimes, customers need to cancel or reschedule service—even when a technician is already on the way. To help with this, Visionet enhanced Field Service RSO so service managers can use the Intra Day feature to help optimize work order schedules on the fly. With this feature, service managers can dynamically adjust a day’s schedule in response to various situations such as cancellations or rescheduling, incoming high-priority trouble tickets, unexpected gaps in technicians’ schedules, delays in ongoing assignments, or fluctuations in resource availability. This level of agility in scheduling ensures that service disruptions are handled with maximum efficiency.

Take, for instance, a scenario where a customer faces an unexpected broadband outage during the day, and the problem can’t be fixed remotely. In that case, a service manager may dispatch a field technician to the location to resolve the issue quickly and limit service interruption. Reviewing the Field Service RSO board, the manager can find an available technician with the expertise that’s best suited to address the customer’s issue promptly. The manager then assigns the new work order and reorganizes the day’s schedule to accommodate this change.

A field employee walking outside by solar panels, holding a tablet

Dynamics 365 Field Service

Interact with Copilot using new capabilities in the Field Service web app.

Stepping up field service with next-generation AI

We’re excited to be sharing all the ways you can use Copilot Studio with Copilot in Dynamics 365 Field Service to extend AI capabilities that can help make your field service organization more efficient, productive, and responsive to customers.

We invite you to visit the Microsoft booth (216), along with our partners, at Field Service Palm Springs to discover how Copilot in Dynamics 365 Field Service works alongside frontline teams to streamline work order management and increase technician productivity. Learn more about AI-powered experiences for your frontline on Monday, May 6, by attending:

  • Chair Opening Remarks by Héctor Garcia Tellado, General Manager, Microsoft Dynamics 365 Frontline Applications
  • The Customer Journey Panel: Revaluating and Remapping Service Workflows to Optimize Automation Tool Adoption and Enhance CX

The post Enabling fast, flexible, cost-effective service with Microsoft Copilot in Dynamics 365 Field Service appeared first on Microsoft Dynamics 365 Blog.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.