Bot Deployment | Microsoft Teams Bot Creation | Part 06

Summary

This video tutorial guides viewers through deploying a bot on Microsoft Teams with three deployment options: individual, organizational, and public. The speaker opts for organizational deployment, explaining the process of preparing and submitting a bot with essential files like icons and a manifest file. The manifest details bot information, permissions, and app ID. After creating a zip file, the bot is uploaded and published via App Studio, pending admin approval. The video also highlights the importance of the admin dashboard for app management and the final activation of the bot for organizational use.

Takeaways

• 🤖 **Deployment Types**: There are three deployment types for a bot: Individual, Organization level, and Public.
• 🔒 **Individual Deployment**: The bot is only available to the user who deploys it, making it the easiest to set up.
• 👥 **Organizational Deployment**: The bot is accessible to everyone in the organization, requiring approval from the organization's admin.
• 🌐 **Public Deployment**: The most complex, as it requires passing numerous tests before the bot can be published for anyone to use.
• 📄 **Required Files**: For deployment, three files are needed: an icon color file, an icon outline file, and a manifest file.
• 🖼️ **Bot Icons**: The icon color and icon outline files determine how the bot's icon is displayed in different contexts.
• 📝 **Manifest File**: Contains crucial information about the bot, including its name, permissions, app ID, and other configurations.
• 📑 **Copying Existing Info**: The speaker suggests copying and pasting existing app information into the manifest file for ease.
• 🔄 **Zipping Files**: The manifest and icon files need to be compressed into a zip file for submission to Microsoft Teams.
• 🛠️ **App Studio in Teams**: To upload a bot or app, use the App Studio feature within Microsoft Teams, where you can import and publish the app.
• 🔍 **Admin Approval Process**: The admin dashboard is where the admin can manage and approve apps, making them available for the organization.
• 🔄 **Publishing the App**: After publishing, the app must be approved by the admin before it becomes accessible to the organization's users.

Q & A

What are the three types of bot deployment mentioned in the video?

The three types of bot deployment are Individual, Organization level, and Public.

What is the main difference between Individual and Organization level deployment?

Individual deployment makes the bot available only to you, while Organization level deployment allows everyone in your organization to access and talk to the bot.

Why is Public deployment considered more difficult than the other types?

Public deployment is more difficult because it requires passing numerous tests before the bot can be published and made available to any organization or individual.

What is the purpose of the 'manifest' file in the deployment process?

The 'manifest' file contains important information about the bot such as the bot's name, permissions, app ID, and other configuration values necessary for deployment.

What are the two icon files used for in the bot deployment?

The two icon files, 'icon color' and 'icon outline', are used to display the bot's icon in different places within the Microsoft Teams platform.

How does the video guide the user to prepare for the deployment process?

The video instructs the user to provide certain information to Microsoft Teams, including selecting Python, choosing a Team Conversation Bot, and using the three files (icon color, icon outline, and manifest) to submit the app for approval.

What is the role of the 'App Studio' in deploying a bot to Microsoft Teams?

The 'App Studio' in Microsoft Teams is used to import an existing app, set up the bot details from the manifest file, and publish the app for organization-level access pending admin approval.

What is the significance of the admin's approval in the deployment process?

The admin's approval is crucial as it allows the published bot to be accessible to users within the organization after it has been published by the developer.

How can users find and activate the deployed bot within Microsoft Teams?

Users can find the deployed bot in the 'Apps' section of Microsoft Teams, where they can see the list of available apps and activate the organization's app.

What documentation does Microsoft provide to help users understand the manifest file and deployment process?

Microsoft provides a comprehensive documentation page that offers a detailed description and guidance on the manifest file and the deployment process, which can be accessed through the provided URL in the video.

What is the final step for making the bot available to the organization after publishing?

The final step is for the admin to go to the admin center, select the app, and change its status to 'publish', making it available for use within the organization.

Outlines

00:00

🤖 Introduction to Bot Deployment Types

This paragraph introduces the video's focus on deploying a bot and outlines three deployment types: Individual, Organization, and Public. It explains that the complexity of deployment varies with the intended audience, being easiest for individual use and most complex for public access, which requires passing numerous tests. The speaker opts for an Organization level deployment and briefly describes the required files: icon color, icon outline, and the manifest file, which contains essential bot information such as name, permissions, and app ID. The paragraph also mentions the need to submit these files to Microsoft Teams for approval.

05:01

📁 Steps for Organization Level Bot Deployment

The second paragraph delves into the process of deploying a bot at the organizational level. It describes the steps of loading app details from a manifest file using the App Studio in Microsoft Teams, including version number, description, names, and icons. The paragraph explains the need for an admin's approval after publishing the bot within the organization. It also guides through the process of making the app available for use by navigating to the apps section and activating it. The speaker provides a brief on how the admin will see and approve the app through the admin dashboard. The paragraph concludes with a summary of the steps involved in creating a manifest file, zipping it, importing it into App Studio, publishing, and getting admin approval.

Keywords

💡Deployment

Deployment in the context of the video refers to the process of making a bot available for use. It is a key concept as it outlines the different levels at which a bot can be made accessible: individual, organization, and public. The script discusses the varying degrees of difficulty associated with each type of deployment, emphasizing that public deployment is the most challenging due to the need to pass numerous tests before publication.

💡Individual Deployment

Individual deployment is one of the three types of deployment mentioned in the script. It is defined as making a bot available exclusively to the person who created it. This type is described as the easiest form of deployment, as it does not require approval from others or compliance with additional standards.

💡Organization Level Deployment

Organization level deployment is another deployment type where the bot is made accessible to everyone within an organization. The script explains that this is more complex than individual deployment because it involves publishing the bot and requires approval from the organization's admin, indicating a higher level of scrutiny and coordination.

💡Public Deployment

Public deployment is the most challenging of the three deployment types discussed in the video script. It involves making a bot available to any organization or individual, which requires passing a significant number of tests before the bot can be published. This level of deployment is characterized by the highest level of difficulty and the broadest potential audience.

💡Microsoft Teams

Microsoft Teams is the platform on which the deployment of the bot is being discussed. It is a key part of the script's narrative as it is the environment where the bot will operate and be made available to users. The script details the process of submitting information to Microsoft Teams and the subsequent steps involved in deploying a bot on this platform.

💡Manifest File

The manifest file is a crucial component in the deployment process described in the script. It contains essential information about the bot, such as its name, permissions, and app ID. The script explains that this file, along with icon files, is submitted to Microsoft Teams for review and approval during the deployment process.

💡App Studio

App Studio is a feature within Microsoft Teams that is used to manage and publish apps, including bots. The script describes using App Studio to import an existing program, set up the bot's details from the manifest file, and publish the bot for organization-level deployment.

💡Admin Approval

Admin approval is a necessary step in the deployment process, particularly for organization-level and public deployments. The script mentions that once a bot is published, the organization's admin must approve it before it can be used by the organization's members. This step ensures that only approved and compliant bots are made available within the organization.

💡Bot Icons

Bot icons are visual representations of the bot that appear within Microsoft Teams. The script discusses two types of icons: icon color and icon outline. These icons are part of the bot's identity and are included in the manifest file, which is submitted as part of the deployment process.

💡Publish

Publishing, in the context of the video, refers to the act of making the bot available within Microsoft Teams for a certain level of audience (individual, organization, or public). The script explains that after the bot is published, it must go through an approval process before it can be activated and used by the intended audience.

💡Admin Dashboard

The admin dashboard is the interface within Microsoft Teams where administrators manage settings and apps for the organization. The script describes using the admin dashboard to search for and approve apps, including the bot being discussed, ensuring that only authorized and compliant applications are accessible to organization members.

Highlights

Introduction to deploying a bot with three types of deployment: Individual, Organization level, and Public.

Individual deployment makes the bot available only to the user.

Organization level deployment allows everyone in the organization to access the bot.

Public deployment enables any organization or individual to use the bot, with the highest level of difficulty.

Explanation of the process for organization level deployment.

Requirement of providing information to Microsoft Teams for deployment.

Description of the three files needed for app submission: icon color, icon outline, and manifest.

The manifest file contains crucial information such as bot name, permissions, and app ID.

Instructions on copying and pasting existing app information into the echo bot's manifest file.

Details on the use of icons in the manifest file for bot display.

Microsoft Teams provides a URL for further documentation on the manifest file.

Steps to compress the manifest and related files into a zip file for submission.

Using App Studio in Microsoft Teams to upload and manage the bot.

Importing an existing program into the App Studio instead of creating a bot from scratch.

Process of publishing the bot within the organization and requiring admin approval.

Accessing the admin dashboard to manage and approve apps.

Final summary of the steps involved in deploying a bot in Microsoft Teams.

Anticipation of the actual video demonstration in the next video.

Transcripts

Hey, guys. In this video, we're gonna deploy our bot.

There are 3 types of deployment.

Individual , when you do this kind of deployment, Bot will be only available to you.

Organization level deployment

so that everyone in your organisation can access your bot and talk to it.

and the Public, any organisation or anyone can use your bot.

and each deployment comes with its own level of difficulties

and the level of difficulty will be proportional to the number of people that gonna use your bot.

For individual, it's very easy.

For organisation its little complex than easy.

You will be publishing the bot and your organisation admin needs to approve it.

And Public is very hard I felt.

Because we need to pass many number of tests we need pass before you publish your bot.

We gonna do the organisation level deployment.

So let's see how to do what to do.

So in order for the deployment, we need to provide some information.

We need to give some information to the Microsoft teams.

So let me... show you the sample they have used,

select python.

And just picking this Team Conversation Bot.

And here if you see we have these fields in manifest.

We use these three files to submit our app and then our organisation admin gonna approve or decline it.

So what are these three files for? I icon color, icon outline an main file.

These two are our bot icons, like, whatever icon you want to display for your bot that you can put it.

And manifest will contain the information Like,

what is the bot name? What is the permission that it has, and the app ID, all those information.

So what I'm gonna do since I already have this information, I'm just gonna copy paste of my existing app.

In our echo bot I'm gonna paste that.

This is manifest file.

Let's open in an editor.

Let's see what are the files we have.

Icon color and Icon outline and manifest file.

So these two icons are accordingly used by the place they're displayed.

So let's quickly see this manifest file.

So here, we have given developer information.

here we have icons information, and the name of our bot,

description, some color and the bot Id with the same app Id and the scopes and..

This command I'm gonna tell you later. But for now just ignore it.

That's it. But for... to give you more information.

Let me just open it. this is the url for that manifest file. There is a very good documentation provided by Microsoft.

you can go through them go through this page to understand more about it.

For everything they have given nice neat description. Okay.

So what we need to do now is...

go to our manifest file.

And we need to zip them.

Compress. and create the zip file.

We have created the zip file.

Now we need to submit this to my Microsoft teams.

So let me open Microsoft teams.

Seems my system ran out of memory. I may run out of memory. I don't know.

Two hours later.

In order for you to upload a app or bot

what you need, You need app studio.

here you can see that is something called App Studio.

You click on it,

these are the drafts which I previously created. So

So what we are we are not creating the bot from the scratch, because I already have the code.

Import an existing program. So we are on the right folder, so this manifest zip file we have created.

Let's set up that.

Once you select, it's gonna read from other manifest file and load all the details.

So app details loaded, version number description, names, icons.Okay.

And the bot information, all that.

here you can see. There is this... video section, capability sections finish.

In the test and distribute, there is an option called publish.

once you publish... What it's gonna happen is, its gonna be published to your organisation level, but your admin needs to approve it once.

Once you approve, then you can go to this apps section.

And here, you'll see list apps that are available.

Your are organisation App will be shown in the top built for your organization, you can click and activate it.

But I'll also show you how it will look for the admin to approve it.

Let me open the link. So this is the admin dashboard link.

Come on open up. Yeah.

Here you can see there are list of settings, what we are interested in the teams app, click on manage apps

Here it's Gonna show list of apps for us. Search our app by its name. So here it is. Click on it.

And now here this status is already published because I've already did. If it it's not, you just need to do it, you just need to publish.

Once you publish it, the users in your organisation will be able to use your app.

So I think let me just re summarize it again. So... What we have.

So we have a manifest file, in this we're gonna define list of configuration values

like names, icons, permissions & all those stuff.

And we're gonna create a zip file and manifest zip file and in the Microsoft teams,

we need to go to the app studio.

In the apps studio,

we are gonna do import an existing app and we gonna select our zip file and then you're gonna just publish it.

Once we publish it we go to our admin centre select the app and change the status to publish. That's it.

The actual video we have seen in the beginning will be coming up in the next video.