Setting up the Self-configured bot for using Microsoft Copilot

  • Release version: Yokohama
  • Updated January 21, 2026
  • 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 .

    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.
    • Enable Copilot integration with Now Assist in Virtual Agent. For more information, see Enable Now Assist experience in Virtual Agent API.
    • 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.
      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 Enable AI Search for Next Experience.
    • 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
      Update the description, semantic description, and sample prompts on the manifest.json file to reflect your Self-configured bot name.
      • 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.

      • 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
        Prompts are displayed while you connect with the Copilot using your plugin or bot name.

      For more information, refer to App manifest scheme 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.

      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
      Microsoft Copilot displaying the Message Extension-enabled apps.
      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.