In my previous post you were able to learn how to authenticate user in Power Virtual Agent. This post is about getting and using context of the authenticated user.
Today Microsoft already released some of the features, which were planned to be released on 2nd of December 2019, in their “new” product: Power Virtual Agent. One of them is “Authentication”. In this post I will help you to set up Azure Active Directory as an oAuth2.0 authentication endpoint.
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”).
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.