Teams Real Simple with Pictures: Using List Rules and Exchange to keep the Team up to date on changes

It feels good to be back on a somewhat even keel. Winter has been absolutely crazy - and after the Microsoft Teams Winter Tour and Ignite I had to take a short break to play what I call the containment game. You know the one. Batting everything out whilst simultaneously closing everything down. It's stopping that accumulation of work from getting out of control. I am happy to say that's now done. I won. It's back to business as usual. So what should we talk about first? There is a lot of things given that Ignite is now over - and if I were others maybe I would go for the latest and greatest, yet having wanted to discuss it since it's recent release and having had no bandwidth to do so I have settled on List Rules and how we can notify the Team of changes to the list. Something straightforward and doesn't take long to write home about. So Rules. Rules are defined by Microsoft as having the purpose of 'automate [ing] tasks such as sending someone a notification when data changes in the list'. In other words, they are very likely replacements for Alerts which have been around a long time and are legacy functionality stretching back to classic SPO and SPO Lists. Now, this blog won't cover every possible scenario for a rule. There's no point - it's super simple and as you go through this blog you'll see how easy it is to implement rules. What I am more interested in is notifying the team of changes rather than individuals: either in Teams or via email. What's that? This can be done by Power Automate and we could create a flow and do it that way. Absolutely. Yet this would suggest whoever is implementing it knew how to do that and had the time and inclination to do that. For me, a lot of what I hear is people want to just do things there, on the List. So Rules for simplicity, Power Automate for anything more