> ## Documentation Index
> Fetch the complete documentation index at: https://kb.mspprocess.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploying the MSP Process Teams Bot Into a Microsoft Teams Environment

> IntroductionWhen an end-user calls into your helpdesk, one of the options you can use to verify their identity is to send them an end-user verification code…

### Introduction

When an end-user calls into your helpdesk, one of the options you can use to verify their identity is to send them an end-user verification code or link through Microsoft Teams.

In order to send the verification code or link through Microsoft Teams, you must first customize the MSP Process Teams bot, and then deploy it to your client's Microsoft Teams environment.

### **Setting up for Verication+ only services**

Log into your MSP Process tenant

Go to Settings> Account Settings> Teams Bot Configuration

![](https://mintcdn.com/triggr/dXDzJtUmPBaHtkPV/images/msp-process-kb/ef0f6825b42e.webp?fit=max\&auto=format\&n=dXDzJtUmPBaHtkPV\&q=85\&s=9c5af740dccde5a958af782643e3a687)

Create a Teams Bot by selecting an Icon for both the Color Icon and Outline icon (if you add the same file to both, the outline image will be blurred)

Fill out the remaining sections of the page and click Update. Then Get Zip File

![](https://mintcdn.com/triggr/-njaXAnAb5AWpJCy/images/msp-process-kb/5f408d4ad056.webp?fit=max\&auto=format\&n=-njaXAnAb5AWpJCy\&q=85\&s=7b020e24b74ef7fcfac237839e4f9beb)

You can then import the teams Bot into your Teams Admin portal. 

You can additionally set the app to autoload on your clients sidebar by default. 

Your clients should then be able to use this as a way to get end user Authentication codes. 

### Customizing the MSP Process Teams Bot for Full Service Tenants

1. Login to the MSP Process UI ([https://app.mspprocess.com](https://app.mspprocess.com))
2. Navigate to the **AI Service Desk ->** **Client Portal -> Teams Bot Configuration** page
3. Configure the Bot so that it has your logo, is named appropriately (so that you your customers will understand who the messages are coming from), and has an appropriate description:

* **NOTE:** For optimal readability, the logo you upload should be 192 x 192 pixels 
*

1. The following fields are required by Microsoft; here's how we recommend to configure them:
2. **Description (Short):** If you've got a snazzy marketing slogan for your MSP ("Our MSP is the place to be!") put it here.
3. **Description (Long):** Enter text that'll tell your end-users what they should use the app for: "Use this app to interact with the Blue Wolf IT Team on your Support requests."
4. **Website URL:** Enter your website URL; it must start with https\://
5. **Privacy Policy:** Enter the URL to your privacy policy. If you don't have a privacy policy, just enter the URL of your website. It must start with https\://
6. **Terms of Service:** Enter the URL to your Terms and Conditions. If you don't have a Terms and Conditions web page, just enter the URL of your website. It must start with https\://
7. When everything has been configured, click the **Get Zip File** button

### Deploying the Bot for Testing Purposes, to One User

You may wish to test out how the MSP Process Teams bot looks by first making it available in your own MS Teams environment. This can be done for a single user, allowing you (the user) to test things out before deploying it to your customers.

Source: These instructions come from a Microsoft KB article ([here](https://learn.microsoft.com/en-us/microsoftteams/platform/sbs-teams-conversation-bot?tabs=dev\&tutorial-step=5))

#### **To upload the app to Teams**

1. In the Teams client, select the **Apps** icon.

2. Select **Manage your apps**.

3. Select **Upload an app**.

4. Look for the option to **Upload a custom app**. If the option is visible, custom app upload is enabled.

5. ![](https://mintcdn.com/triggr/qgn0c5cLkGKqcauq/images/msp-process-kb/92024e307b34.png?fit=max\&auto=format\&n=qgn0c5cLkGKqcauq\&q=85\&s=af996ee08cd8b8ae89ac5b7c67481a4a)

6.  Note: Contact your Teams administrator, if you don't find the option to upload a custom app.

7. Select **Open** to upload the .zip file that you created earlier.

8.

9. Click **Add**.

10.

11. Select **Open** to use the app in personal scope.

12. Alternatively, you can either search and select the required scope or select a channel or chat from the list, and move through the dialog to select **Go**.

13.

14. **Congratulations!** You have now deployed your MS Teams bot into your MS Teams environment, and you've made it available for testing purposes.

### Deploying the MSP Process Teams Bot to a Client's Microsoft Teams Environment

1. Login to the Microsoft Teams Admin Center, and navigate to **Teams Apps -> Manage Apps** (Direct Link: [https://admin.teams.microsoft.com/policies/manage-apps](https://admin.teams.microsoft.com/policies/manage-apps))

* Click on **Actions -> Upload new app**

1. Click the **Upload** button to upload the .zip file that you created earlier.

*

1. Once the app has been uploaded, navigate to **Teams Apps -> Setup Policies**
2. Click the **Add** button to create a new policy
3. Give this app policy an appropriate Name and Description

*

1. In the **Installed Apps** section, click the **Add apps** button, and choose your MSP Process Teams bot

*

1. Click **Save**
2. Click on the **Group policy assignment** tab

*

1. Click the **Add** button, and assign your app policy to the appropriate list of end-users (in this example, I'm assigning the app to *everyone*)

*

That's it! You've now deployed your customized version of the MSP Process Teams bot to your client's Microsoft Teams environment.

### Sending End-user Verification Codes/Links through Microsoft Teams

Now that you've deployed your customized version of the MSP Process Teams bot to your client's Microsoft Teams environment, you can start sending them end-user verification codes or links. For ConnectWise, HaloPSA, SuperOps.ai, Syncro or Zendesk partners, you'll click on the red shield beside the user's e-mail address:

You'll then be able to send that end-user either a code or a link through Microsoft Teams by clicking the appropriate button:

For our Autotask partners, you'll see the two new Teams-related options (**Teams Code** and **Teams Link**) in the Verification feature, in the drop-down menu:


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.