---
sourceDocument: Yokohama Conversational Interfaces
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/conversational-interfaces

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Setting up the Self-configured bot for using Microsoft Copilot

# Setting up the Self-configured bot for using Microsoft Copilot {#ariaid-title1}

Release version: Yokohama  
Updated January 21, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Using your Self-configured bot with Microsoft Copilot for Now Assist conversations requires you to complete a few additional setup actions.  
Note:  
Custom Engine Agent (CEA) is replacing Declarative Agent (DA), the prior Microsoft Copilot integration. The CEA enables Virtual Agent to be discoverable by Microsoft Copilot, with full functional access to Now Assist in Virtual Agent and multi-turn conversations.

You must have version 10.1.1 or higher of the Microsoft Teams plugin to have CEA support. In version 10.2 of the Microsoft Teams plugin, streaming is inactive by default and CEA is active by default.

You can install the default Now Assist
Virtual Agent bot from the Microsoft Teams app store. This bot deploys automatically, but you cannot customize its prompts or manifest description. You must still install the ServiceNow
Microsoft Teams plugin from the ServiceNow app store.

For more information on Microsoft Teams and Now Assist in Virtual Agent installation and settings, see [.](https://servicenow-prod.fluidtopics.net/iN2MtmVnzW_UkA~M5QL0NQ "Integrate your Now Assist Virtual Agent with Microsoft Copilot using Conversational Integration with Microsoft Teams to leverage the generative AI conversational experience.")

As of October 2025, streaming is active by default for both Teams and Copilot. Configurations are shared by Teams and Copilot, and both apps are linked to the assistant.

You can use the self-configured bot or the default version to install Microsoft Copilot integration. The default bot automatically deploys in Copilot. If you want to use a self-configured bot for Microsoft Copilot, complete the following additional setup:  
* Provide the Self-configured bot a name while creating it. Providing a name for the bot improves the reliability of the bot responses within Copilot conversations.
* Activate your assistant in the Conversational Interfaces configuration page. For more information, see [Configuring assistants overview](https://servicenow-prod.fluidtopics.net/Iq8pGh6Fvy4~YMEuJyerJQ "Use Assistant Designer to build and optimize large language model (LLM) assistants for your conversational needs. Assistant Designer is a centralized assistant administrator experience that allows you to create and manage both chat and voice assistants.").
* Enable Copilot integration with Now Assist in Virtual Agent. For more information, see [Enable Now Assist experience in Virtual Agent API](https://servicenow-prod.fluidtopics.net/CB8hy9UeprQWJvheHHEN0Q "Enable Now Assist experience in Virtual Agent API to support generative AI skills across multiple provider channels.").
* Migrate any relevant topics to the Now LLM Service for Now Assist large language model (LLM) conversations with Copilot. To migrate your topics to LLM, you must enable LLM. For more information, see [Migrate NLU topics to LLM topics](https://servicenow-prod.fluidtopics.net/IO5mySqmb8AowcSuXjIKkQ "Migrate one or more of your existing Natural Language Understanding (NLU) or keyword topics into new large language model (LLM) topics while maintaining your original NLU/keyword topics. After migration is complete, choose whether to publish your new LLM topics.").  
  Note:  
  After enabling LLM, you don't need to do anything specific for the Copilot as it pertains to LLM topics. As long as the Self-configured bot is discoverable by the LLM, it's also discoverable by the Copilot and verifies that the plugin or bot responds when it's used.
* Enable AI Search on your ServiceNow Now Assist instance to use Now Assist with Microsoft Copilot. For more information about enabling AI Search, see .
* Update the following fields within the manifest file that is downloaded from Admin experience to configure the Self-configured bot and use it for the Copilot integration.  
  Note:  
  Update the semantic description field if you have any custom skills and make the Copilot LLM and orchestrator have the ability to discover a custom skill.
  Figure 1. manifest.json changes for Copilot integration
  * Full Description:
    * Update the bot name in the full description to your Self-configured bot name.  
      Note:  
      Update the bot name in all the instances in the full description. Updating the bot name helps Copilot to identify the bot that the request must be routed to.
    * Update the generic description that ServiceNow provides with a specific use case that you may have in your topics.

      For example, if you have unique LLM skills that accomplish scenarios unique to your environment,
      such as reserving a hotel desk or ordering food for a meeting, be sure to add that to your description so that Copilot will be able to recognize the skill and be able to process it.
    {#setup-self-bot-copilot__ul_qf4_1fb_mcc}
  * View Prompts: Add the prompts with your bot name.  
    Note:  
    The JSON prompts aren't available in the manifest file by default. You must add them yourself and update the bot name with your Self-configured bot name.  

        {
        "Sana What is our laptop replacement policy?"
        },

    Note:  
    Updating the bot name on the prompt helps the utterance work with Copilot.Figure 2. View Prompts

  {#setup-self-bot-copilot__ul_wzk_ycb_mcc}

  For more information, refer to [App manifest scheme](https://learn.microsoft.com/en-us/microsoftteams/platform/resources/schema/manifest-schema) in the Microsoft Teams Developer documentation.
* Enable Message Extension for the Self-configured bot, generate the new manifest file, and upload it to Microsoft Teams.  

  Message Extension in Microsoft Copilot Integration
  :   The Microsoft Copilot integration is built on top of the existing Message Extension feature. For more information about enabling Message Extension for your bot on your ServiceNow instance, see [Auto-generate the manifest file for uploading on Microsoft Teams](https://servicenow-prod.fluidtopics.net/BDugBwl_qJj1hfKQoETXuw "Auto-generate the manifest file and customize the branding of your Microsoft Teams app so that you can make Virtual Agent available in your organization.").

      When the message extension is enabled, you see the list of message extension-enabled apps when you select the Plugins icon (![Plugins icon.]()). You can select the app of your choice from the list of plugins.  
  Figure 3. Message Extension in Copilot  
  Note:  
  Users can update the manifest file to enhance the Copilot's Orchestration.
* Edit, customize, and enhance the bot behavior to meet your needs. For more information, see [Guidelines to create or upgrade Copilot extensions](https://learn.microsoft.com/en-us/microsoftteams/platform/messaging-extensions/high-quality-message-extension?tabs=tasks).
{#setup-self-bot-copilot__ul_ogl_p3h_2cc}