NOTE: This is a sample application to help you understand how Semantic Kernel and AI can work in Web Applications. This sample is NOT FOR PRODUCTION deployments.

Chat Copilot Sample Application

This sample allows you to build your own integrated large language model (LLM) chat copilot. The sample is built on Microsoft Semantic Kernel and has three components:

1. A frontend application React web app
2. A backend REST API .NET web API service
3. A .NET worker service for processing semantic memory.

These quick-start instructions run the sample locally. They can also be found on the official Chat Copilot Microsoft Learn documentation page for getting started.

To deploy the sample to Azure, please view Deploying Chat Copilot after meeting the requirements described below.

IMPORTANT: This sample is for educational purposes only and is not recommended for production deployments.

IMPORTANT: Each chat interaction will call Azure OpenAI/OpenAI which will use tokens that you may be billed for.

Requirements

You will need the following items to run the sample:

• .NET 7.0 SDK (via Setup install.* script)
• Node.js (via Setup install.* script)
• Yarn (via Setup install.* script)
• AI Service

Instructions

Windows

1. Open PowerShell as an administrator.

   NOTE: Ensure that you have PowerShell Core 6+ installed. This is different from the default PowerShell installed on Windows.

2. Setup your environment.

   cd <path to chat-copilot>\scripts\
   .\Install.ps1
   

   NOTE: This script will install Chocolatey, dotnet-7.0-sdk, nodejs, and yarn.

   NOTE: If you receive an error that the script is not digitally signed or cannot execute on the system, you may need to change the execution policy (see list of policies and scopes) or unblock the script.

3. Configure Chat Copilot.

   .\Configure.ps1 -AIService {AI_SERVICE} -APIKey {API_KEY} -Endpoint {AZURE_OPENAI_ENDPOINT}
   

   • AI_SERVICE: AzureOpenAI or OpenAI.

   • API_KEY: The API key for Azure OpenAI or for OpenAI.

   • AZURE_OPENAI_ENDPOINT: The Azure OpenAI resource Endpoint address. Omit -Endpoint if using OpenAI.

   • IMPORTANT: For AzureOpenAI, if you deployed models gpt-35-turbo and text-embedding-ada-002 with custom names (instead of each own's given name), also use the parameters:

     -CompletionModel {DEPLOYMENT_NAME} -EmbeddingModel {DEPLOYMENT_NAME} -PlannerModel {DEPLOYMENT_NAME}
     

4. Run Chat Copilot locally. This step starts both the backend API and frontend application.

   .\Start.ps1
   

   It may take a few minutes for Yarn packages to install on the first run.

   NOTE: Confirm pop-ups are not blocked and you are logged in with the same account used to register the application.

   • (Optional) To start ONLY the backend:

     .\Start-Backend.ps1
     

Linux/macOS

1. Open Bash as an administrator.

2. Configure environment.

   cd <path to chat-copilot>/scripts/
   

   Ubuntu/Debian Linux

   ./install-apt.sh
   

   NOTE: This script uses apt to install dotnet-sdk-7.0, nodejs, and yarn.

   macOS

   ./install-brew.sh
   

   NOTE: This script uses homebrew to install dotnet-sdk, nodejs, and yarn.

3. Configure Chat Copilot.

   1. For OpenAI

      ./configure.sh --aiservice OpenAI --apikey {API_KEY}
      

      • API_KEY: The API key for OpenAI.

   2. For Azure OpenAI

      ./configure.sh --aiservice AzureOpenAI \
                     --endpoint {AZURE_OPENAI_ENDPOINT} \
                     --apikey   {API_KEY}
      

      • AZURE_OPENAI_ENDPOINT: The Azure OpenAI resource Endpoint address.
      • API_KEY: The API key for Azure OpenAI.

      IMPORTANT: If you deployed models gpt-35-turbo and text-embedding-ada-002 with custom names (instead of each own's given name), you need to specify the deployment names with three additional parameters:

      ./configure.sh --aiservice AzureOpenAI \
                     --endpoint        {AZURE_OPENAI_ENDPOINT} \
                     --apikey          {API_KEY} \
                     --completionmodel {DEPLOYMENT_NAME} \
                     --plannermodel    {DEPLOYMENT_NAME} \
                     --embeddingmodel  {DEPLOYMENT_NAME}
      

4. Run Chat Copilot locally. This step starts both the backend API and frontend application.

   ./start.sh
   

   It may take a few minutes for Yarn packages to install on the first run.

   NOTE: Confirm pop-ups are not blocked and you are logged in with the same account used to register the application.

   • (Optional) To start ONLY the backend:

     ./start-backend.sh
     

(Optional) Run the memory pipeline

By default, the webapi is configured to work without the memory pipeline for synchronous processing documents. To enable asynchronous document processing, you need to configure the webapi and the memory pipeline. Please refer to the webapi README and the memory pipeline README for more information.

(Optional) Enable backend authentication via Azure AD

By default, Chat Copilot runs locally without authentication, using a guest user profile. If you want to enable authentication with Azure Active Directory, follow the steps below.

Requirements

• Azure account
• Azure AD Tenant

Instructions

1. Create an application registration for the frontend web app, using the values below

   • Supported account types: "Accounts in this organizational directory only ({YOUR TENANT} only - Single tenant)"
   • Redirect URI (optional): Single-page application (SPA) and use http://localhost:3000.

2. Create a second application registration for the backend web api, using the values below:

   • Supported account types: "Accounts in this organizational directory only ({YOUR TENANT} only - Single tenant)"
   • Do not configure a Redirect URI (optional)

NOTE: Other account types can be used to allow multitenant and personal Microsoft accounts to use your application if you desire. Doing so may result in more users and therefore higher costs.

Take note of the Application (client) ID for both app registrations as you will need them in future steps.

3. Expose an API within the second app registration

   1. Select Expose an API from the menu

   2. Add an Application ID URI

      1. This will generate an api:// URI

      2. Click Save to store the generated URI

   3. Add a scope for access_as_user

      1. Click Add scope

      2. Set Scope name to access_as_user

      3. Set Who can consent to Admins and users

      4. Set Admin consent display name and User consent display name to Access copilot chat as a user

      5. Set Admin consent description and User consent description to Allows the accesses to the Copilot chat web API as a user

   4. Add the web app frontend as an authorized client application

      1. Click Add a client application

      2. For Client ID, enter the frontend's application (client) ID

      3. Check the checkbox under Authorized scopes

      4. Click Add application

4. Add permissions to web app frontend to access web api as user

   1. Open app registration for web app frontend

   2. Go to API Permissions

   3. Click Add a permission

   4. Select the tab APIs my organization uses

   5. Choose the app registration representing the web api backend

   6. Select permissions access_as_user

   7. Click Add permissions

5. Run the Configure script with additional parameters to set up authentication.

   Powershell

   .\Configure.ps1 -AiService {AI_SERVICE} -APIKey {API_KEY} -Endpoint {AZURE_OPENAI_ENDPOINT} -FrontendClientId {FRONTEND_APPLICATION_ID} -BackendClientId {BACKEND_APPLICATION_ID} -TenantId {TENANT_ID} -Instance {AZURE_AD_INSTANCE}
   

   Bash

   ./configure.sh --aiservice {AI_SERVICE} --apikey {API_KEY} --endpoint {AZURE_OPENAI_ENDPOINT} --frontend-clientid {FRONTEND_APPLICATION_ID} --backend-clientid {BACKEND_APPLICATION_ID} --tenantid {TENANT_ID} --instance {AZURE_AD_INSTANCE}
   

   • AI_SERVICE: AzureOpenAI or OpenAI.
   • API_KEY: The API key for Azure OpenAI or for OpenAI.
   • AZURE_OPENAI_ENDPOINT: The Azure OpenAI resource Endpoint address. Omit -Endpoint if using OpenAI.
   • FRONTEND_APPLICATION_ID: The Application (client) ID associated with the application registration for the frontend.
   • BACKEND_APPLICATION_ID: The Application (client) ID associated with the application registration for the backend.
   • TENANT_ID : Your Azure AD tenant ID
   • AZURE_AD_INSTANCE (optional): The Azure AD cloud instance for the authenticating users. Defaults to https://login.microsoftonline.com.

6. Run Chat Copilot locally. This step starts both the backend API and frontend application.

   Powershell

   .\Start.ps1
   

   Bash

   ./start.sh
   

Troubleshooting

1. Issue: Unable to load chats.

   Details: interactionin_progress: Interaction is currently in progress.

   Explanation: The WebApp can display this error when the application is configured for a different AAD tenant from the browser, (e.g., personal/MSA account vs work/school account).

   Solution: Either use a private/incognito browser tab or clear your browser credentials/cookies. Confirm you are logged in with the same account used to register the application.

2. Issue:: Challenges using text completion models, such as text-davinci-003

   Solution: For OpenAI, see model endpoint compatibility for the complete list of current models supporting chat completions. For Azure OpenAI, see model summary table and region availability.

3. Issue: Localhost SSL certificate errors / CORS errors

   

   Explanation: Your browser may be blocking the frontend access to the backend while waiting for your permission to connect.

   Solution:

   1. Confirm the backend service is running. Open a web browser and navigate to https://localhost:40443/healthz
      • You should see a confirmation message: Healthy
      • If your browser asks you to acknowledge the risks of visiting an insecure website, you must acknowledge this before the frontend can connect to the backend server.
   2. Navigate to http://localhost:3000 or refresh the page to use the Chat Copilot application.

4. Issue: Yarn is not working.

   Explanation: You may have the wrong Yarn version installed such as v2.x+.

   Solution: Use the classic version.

   npm install -g yarn
   yarn set version classic
   

5. Issue: Missing /usr/share/dotnet/host/fxr folder.

   Details: "A fatal error occurred. The folder [/usr/share/dotnet/host/fxr] does not exist" when running dotnet commands on Linux.

   Explanation: When .NET (Core) was first released for Linux, it was not yet available in the official Ubuntu repo. So instead, many of us added the Microsoft APT repo in order to install it. Now, the packages are part of the Ubuntu repo, and they are conflicting with the Microsoft packages. This error is a result of mixed packages. (Source: StackOverflow)

   Solution:

   # Remove all existing packages to get to a clean state:
   sudo apt remove --assume-yes dotnet*;
   sudo apt remove --assume-yes aspnetcore*;
   sudo apt remove --assume-yes netstandard*;
   
   # Set the Microsoft package provider priority
   echo -e "Package: *\nPin: origin \"packages.microsoft.com\"\nPin-Priority: 1001" | sudo tee /etc/apt/preferences.d/99microsoft-dotnet.pref;
   
   # Update and install dotnet
   sudo apt update;
   sudo apt install --assume-yes dotnet-sdk-7.0;
   

Check out our other repos!

If you would like to learn more about Semantic Kernel and AI, you may also be interested in other repos the Semantic Kernel team supports:

Join the community

We welcome your contributions and suggestions to the Chat Copilot Sample App! One of the easiest ways to participate is to engage in discussions in the GitHub repository. Bug reports and fixes are welcome!

To learn more and get started:

• Read the documentation
• Join the Discord community
• Contribute to the project
• Follow the team on our blog

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

License

Copyright (c) Microsoft Corporation. All rights reserved.

Licensed under the MIT license.