The Baretta

This is a nice simple Flow that I love!  If you work with a lot of different software and want to keep up to date on the latest changes without having to save all those pesky favourites to various RSS feeds/blogs, this is for you. The great thing about this is, when you start posting it to Teams, now everyone can see when there is an update!  It's only 3 steps, here's how: Create a Blank Flow Add the Trigger ' RSS - When a feed item is published ' Add the ' Data Operations - Compose ' action to create a nicely formatted message to send to teams Add the ' Teams - Post a Message ' action, select your team & channel, and put the Compose Output into the Message box I use this flow to keep up to date on all the latest Microsoft PowerApps news, see the screenshot below for my flow setup.

What Nintex Workflow for O365 has an action to create a site automatically in SharePoint, but it's functionality is quite limited.  You can't create groups and you can't add staff to those groups.  This tutorial shows you how to create a Nintex workflow to automate the whole process using SharePoint Web Services. Even better, we are going to create the ability to automate Site Creation across multiple Site Collections. If you're looking for a tutorial on how to do this in Nintex Workflow 2010/2013, I've written an article here:  SharePoint 2010 - Automate Site & Group Creation with Nintex Workflow 2010 Why As most SharePoint administrators are aware, it's ALWAYS a bad idea to give staff the ability to create SharePoint sites.  They will end up creating them for the wrong purposes, will not maintain them, no retention policies will get assigned to them, etc. However, you don't want to restrict your users creative freedom.  You want to govern it...

What Nintex Workflow has an action to create a site automatically in SharePoint, but it's functionality is quite limited.  You can't create groups and you can't add staff to those groups.  This tutorial shows you how to create a Nintex workflow to automate the whole process using SharePoint Web Services. Why As most SharePoint administrators are aware, it's ALWAYS a bad idea to give staff the ability to create SharePoint sites.  They will end up creating them for the wrong purposes, will not maintain them, no retention policies will get assigned to them, etc. However, you don't want to restrict your users creative freedom.  You want to govern it in a manageable way. In order to keep track of all your SharePoint sites, we need to ensure that when we allow staff to create sites/content, it is being properly tagged with the right information.  As long as you are logging & tagging sites with extra data, you can easily govern and manage those sites far i...