We don’t need to deal with the “Messaging bot” or “Calling bot” options at the moment. This will allows us to either connect an existing Microsoft bot we’ve already created, or create a brand new one. Go to the Bots step and click the Set up button. For our purposes, we only need to worry about the Bot. We can add a Tab, Bot, Connector, or Message Extension. After that page is filled out, we should go to the Capabilities step. The “Branding” will need to have 2 icons, one that’s 192px by 192px, and another that’s 32×32. The various website URLs can be anything while we test. “Package Name” is basically like a web url, but in reverse, so mine is something like “”… “Version” should be 1.0.0 to start and should align with semantic versioning. For “App ID”, I just click the “Generate” button and it fills in a UUID for us. The App details are fairly self-explanatory, and you only need to worry about the ones with the star. After that, you’ll be greeted with a lot of options you’ll need to make your app. The easiest way to do that is through the Microsoft App Studio app.Īfter adding that, go into the App Studio, make sure you’re in the “Manifest editor” tab, and choose “Create a new app”.
The first step we need to take is creating an app for us to use. My goal is to write a few posts that simplifies the ways to integrate with Teams and use the Graph API. One thing I noticed is that their documentation is extensive, but can be overwhelming if you just need to do something simple. In my role at Mio, I’ve had the opportunity to work fairly extensively with Microsoft Teams and the Microsoft Graph API.
0 kommentar(er)
