Teams Real Simple with Pictures: The new Viva Goals RBAC role, and distinguishing it from the Organisation Admin role

I spoke recently at a Viva Goals AMA with fellow MVP's Karoliina Kettukari and Kevin McDonnell. And in addition to it being a lot of fun I got to tell a little bit about my story and how I got into Viva. This was via Viva Goals. I class myself as what I would call a second wave advocate of Viva. Why? Because the first wave with the initial four apps such as connections and topics seemed to just pass me by. I was too deep into Teams at the time. I was always, for some reason or other getting around to it. Indeed, it was the acquisition of Ally.io and phasing into the portfolio of Goals which which kicked things off for me, because in my mind Goals looked useful from a business perspective. To me, it looked useful in the same way Power BI is useful. It gave purpose, and direction, and evidence of making an impact. So I got hands on in the preview. I liked it. And then I did a bit of testing for Microsoft - particularly around its integration with Teams, I also attended the programs where I fed back a lot of asks on things like integrations, and one of those asks was to have a defined RBAC role for Goals. This is because there wasn't one in the same way there are other RBAC roles for Viva Apps such as Knowledge Manager, whilst at the same time all the admin controls were accessible to the person who set up the org. Whether it is for principle of least privilege, or decentralised administration there is a case for RBAC. But all is not as it seems and there may be some surprises for those into their Azure AD.