How to create your first Teams bot and deploy it to Azure
Creating a Teams bot is not a complex process, but figuring out all the different things that are required for the first time can seem like a challenging feat to accomplish.
Application development, architecture design, and security in Microsoft cloud
Creating a Teams bot is not a complex process, but figuring out all the different things that are required for the first time can seem like a challenging feat to accomplish.
The reason why we aren’t seeing more Teams app development for real customer scenarios today is that people don’t know enough about it.
As the number of things we can include in our Teams provisioning solutions has grown, it has become harder to remember to ask all the important questions.
Organizations have a lot of processes that include an approval step. Let’s dig into all the available Teams-based approval implementation options, what problems we might face, and how to counter them.
This blog post is about showing you how we can have as effortless Teams provisioning approvals as possible right where they matter the most.
Using the Wiki tab in Teams can easily lead to a permanent loss of information. Let me show you how to delete the tab during your provisioning process.
Wouldn’t it be great if we didn’t have to leave Microsoft Teams whenever we want to use a custom team provisioning solution? Good news: we can!
This blog post aims to clarify the meaning and benefits of workspace provisioning solutions to those who are not yet that familiar with the topic, and explain why there is no one-size-fits-all solution to the problem.
The long awaited continuation to my Shifts blog post mini-series is finally here! This time we dig deep into how you can customize Shifts, what kind of business processes you can automate (with a real-life customer use case), and what pitfalls you need to be aware of.
Even though Shifts has been a part of Teams for a while now, not that many have actually used it or know much about it. In this first part of the series, I’ll tell you the things you need to know about Shifts as a developer to be able to implement meaningful customizations for your customers.
Implementing workspace provisioning solutions results to your dev tenant looking like a massive mess. Let’s clean it up!
Our blog post series is closing to the end. In this final blog post of the series, I will show you how you can automatically configure two SharePoint related tabs: the SharePoint tab itself and the Files tab.
We’ve already come quite far in this blog post series! We’ve got our team cloned and have already started configuring the tabs. The Planner tab is probably the easiest one to configure out of the tabs I’m covering in this blog post series. Still, there are some small things you should keep in mind and be aware of to get the most out of this process.
People can have different opinions on how Teams tabs should be configured and that is most likely the reason why they aren’t automatically configured when you clone a team. The configuration can be automated, but each different kind of tab needs to be set up in a slightly different way. In this blog post, I’ll show you how you can configure the OneNote tab.
At this point, we have our brand new team set up with its cloned tabs. However, none of those tabs are yet configured to show any content. All of the tab types are a bit different from one another, but what I am about to show to you in this blog post is so fundamental that it should be very useful to you no matter which tabs you eventually decide to configure.
In the prelude, I told you a little bit about the reasons why configuring tabs automatically is important. In this one, I will show you a couple of ways on how you can clone a team programmatically via Microsoft Graph. I also talk a little bit about what quirks the whole clone team process contains, and what we can expect from Teams templates in the future.
With the clone team operation, you can clone the team settings, channels, apps, tabs, and even members. What doesn’t automatically happen with cloning though is the configuration of tabs. Searching for the right resource to display can be difficult at times, so I’m happy to tell you that it is possible for us to automate the configuration of the cloned tabs via Microsoft Graph. And that is the bread and butter of this blog post series.
Soon you will be able to create a team for an Office 365 group via its modern team site. There will be a button that allows you to create a Team with a single click. But could things be made even easier? In this blog post, I’ll show you how you can have an option to create a team automatically when creating a new modern, Office 365 group connected team site.
Microsoft Graph Teams operations can be used for all kinds of cool stuff related to Teams. Because I’ve had so much fun playing around with those, I figured I’d show you a couple of examples of how you can utilize those operations in a SPFx web part, and provision a Team for an existing Office 365 Group.