Jun 15 2020 12:07 AM
Jun 15 2020 12:07 AM
Hi all. Hope everyone is well. I have been noticing something strange with Teams for a while now. There are actions linked to the owners of a Team, but they did not carry out these actions. Example if a global administrator removes a user from an Office 365 Group the system message says that an owner of the team has removed them when that is not the case. Any ideas?
Jun 15 2020 12:17 AM - edited Jun 15 2020 12:18 AM
@Navishkar Sadheo Hello! Teams has some background workflows that perform actions on behalf of existing owners when syncing changes from Groups to Teams. This has now been fixed though!
"System messages, e.g., who has been added or removed from a team, will no longer be posted to the Channel pane. This will not affect compliance logs."
Jun 17 2020 02:21 AM
Hi there. Thanks for the reply. I heard about system messages being moved from the general channel to a separate info pane. That is not my issue. My issue is the inaccuracy when it comes to system messages. For example if a global admin who is not a member of a specific team removes a user from an Office 365 Group using the Azure Active Directory Admin center for example, the system message in the general channel says that one of the owners removed the member. This is not correct. Even in the audit, it shows that one of the owners of a team removed the member.
Jun 17 2020 02:28 AM
@Navishkar Sadheo Hello! That's my point with the previous reply.
"Teams has some background workflows that perform actions on behalf of existing owners when syncing changes from Groups to Teams."
As you're not doing it with an existing owner a random owner is chosen for this message. It will be fixed I'm sure.
Jun 17 2020 06:44 AM
Thanks for the info. Hopefully it will be fixed soon. There was many questions going in certain Teams in my organization witch owners questioning each other at to why they added terminated staff back into the Teams etc.
The fact that the audit log doesn't accurately log these events is also alarming but hopefully, it will be fixed soon.