Account was added as owner to a group by Viva Engage?

Question

We were alerted to a change being done on the Entra user database for the breakglass accounts we created dated the 10th of December, which had those breakglass accounts added as an owner to a group. The group seems to apparently be the Viva Engage (yammer) group of what I've found, tho the audit log only lists the group ID, and leaves the displayname and user principal name completely empty.

Said group is not listed in EntraID that I could see, so unsure what it actually is. If I track the Object ID as a group, I end up with a group 'All Company'...which is also one I see popping up in Viva Engage if I actually look at that for management at https://engage.cloud.microsoft/.

Looking at the owners for the group, I find basically all high-level admins existing in EntraID have been added as owner to that group.

Looking at the audit logs, it's shown the actor initiating this change is listed as 'Viva Engage', which is listed as an 'application'.

We're not actively doing anything to implement Viva Engage, nor have we actually done anything with it.

While the membership as an owner isn't really a bad thing for the users, we're puzzled as to where this change came from and who (or what) initiated it and why.

At this point we're thinking it's a change Microsoft has done to provide for further changes made to their Viva Engage thing which may require that right in the future, but we're lookin to get some confirmation of that change actually originating at Microsoft.

Is anyone willing to hazard a guess here, or point me at portions I might look at for more information?

Answer 1

IIRC, all global admins are added as owners to the "All Company" group, which is done by an automated background process. I can confirm the same behavior is some of my test tenants, so it's nothing to worry about.