This blog will cover an example of a MS Teams provisioning process that was originally delivered for M365 California Jan ’21. The sessions were 30 minutes which covered enough time to discuss the entire process. This blog will contain a four videos which dive deeper on the steps during that sessions.

Setting up the SharePoint List

Setting up the Power Automate Flow

Extending the Flow with MS Graph & Azure Active Directory

Setting up the Power App custom list form and the SharePoint user interaction

This is just an example of one way to provision MS Teams sites and the steps involved in that process, it’s certainly not the only way. Feel free to leave a comment and let me know.

Comments
  • Mota
    Posted at 10:29 am January 27, 2021
    Mota
    Reply
    Author

    Hi Tom, really cool walkthrough and very informative. Please can you provide some scenarios where this would process could prove effective? Thanks in advance.

    • Tom Daly
      Posted at 2:59 pm February 10, 2021
      Tom Daly
      Reply
      Author

      Thanks for the feedback. I’ve done 2 more complicated implementations of this in a similar way but there are also products that do the same thing.

      The 2 bigger projects wanted to control how the teams are provisioning so they could be approved by an admin. I used Power Automate in 1 and built a custom SPFx webpart to do the provisioning in another to compare and at the time there were no Preview Flow controls for Teams. Ultimately they wanted to templatize the teams creation process, creating “Project” teams. After provisioning adding members, activating SharePoint features, joining sites to a hub, setting up teams. While most of this would be done in the Power Automate, many steps are done in an Azure Function that can do more. The Power Automate last step is to call the Azure Function to perform some of the site/teams manipulation.

  • Leave a Reply to Mota
    Cancel Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.