When building bot’s for Microsoft Teams you have to keep in mind that Microsoft Teams acts differently when sending emojis. When testing out a bot I was building I always got an error when sending 😊. When testing out the bot in the emulator it always worked. Why is this?

When quickly creating a bot channels registration in Azure (I usually do this for testing something) You can select to create your own Microsoft App ID and Secret. If you do this then you can copy/paste them because you need them later on. But when you select “Auto create App ID and Secret” they don’t show you the secret in your bot settings.

With releasing the SPAdminBot almost a week ago, I got some great response. But I also forgot to mention some items in my previous blog post. The steps to take on how to install this in your own Azure environment and use your own bot ID’s. In this post, I will go through the detailed steps on how to get the SPAdminBot up and running.

I’ve started a new open source project called the SharePoint Admin Bot or SPAdminBot for short. Why you ask? Because I got tired of doing and seeing people do the same tasks over and over again on SharePoint Online and Office 365. For something simple like creating a site collection you would always have to go into the admin portal and click through multiple pages to get the job done. These kinds of simple tasks can be easily done by a bot.