This may seem trivial, but if you want to create a Flow, that is parameterized, where a name of a group and list of members is passed as the request parameters then it turns out it is not that straightforward.
In Microsoft Flow there is a set of actions, that allow to work with Office 365 Groups. There is also one dedicated to adding new members (only “Members”. There is no way currently to add “Owners”).
The post continues the previous one, where I was trying to compare Groups with Teams. Despite the comparison was possible, Office 365 Group is not, what I underlined then, a standalone application, but a security object. Remember also, that Office 365 Groups were first introduced somewhere in 2014. Over the years it was being extended to work with other Office 365 based applications as well to be used in hybrid scenarios with on-premise Exchange.
Since it’s very beginning the narration that Microsoft was building around the concept was, that it is a tool dedicated for groups of employees, that delivers tools assisting and helping in their ongoing work, collaboration and communication.
Office 365 Groups are a quite old concept. They were first introduced somewhere in 2014, but since then the concept developed, from a simple Shared Mailbox, into a tool dedicated for collaboration between employees. Then, in November 2016 Microsoft Teams went public what… brought a lot of confusion on users’ faces. I guess this confusion is still present.
I this post I am not trying to explain when to use what, but to compare those two products to show you their capabilities and… to help you answer on your own, which tool to use when.