07-12-2017 02:37 AM
07-12-2017 05:15 AM
07-12-2017 07:23 AM - edited 07-12-2017 07:24 AM
Worth checking your Office 365 Global admins who are automatically assigned Yammer Verified Admin rights and also check any Network admins that look out of place -
Go to Settings > Network Admin and then choose Admins.
"Yammer offers two levels of network‐wide admin privileges: Network Admin and Verified Admin. Both can configure settings that standard users cannot."
Only Network admins or Verified admins can Remove or block any user. See the Yammer admin guide for more details. Also, check out the Manage Yammer users across their life cycle from Office 365 guide.
If all of this is as expected, logging a Service Request is excellent advice.
07-12-2017 11:46 AMSolution
07-13-2017 12:16 AM
I want to share the question with you from Microsoft support:
We had from past where we had few customer had similar question and design change request but it got rejected by engineering team and primary justification around having that functionality in yammer: Some IT admins have theorized about "bad users", but for Yammer, the users are people trying to be productive at their jobs. They're not going to risk getting in trouble just to temporarily suspend someone as a prank. The reality of this issue is that it's not an issue. Its very few inappropriate suspensions actually happen, and the consequences of those suspensions are very minimal because the suspended user can easily reactivate their account.
07-13-2017 01:06 AM
Thanks for feeding this back, it may help others that also come across this behaviour. So as has been said, it's by design and arguably a quirk of the system but one unlikely to have much impact.
07-13-2017 07:26 AM - edited 07-13-2017 07:27 AM
I would also add to Sebastian's response that if you navigate in to the "Remove users" section in the admin console, you are able to see who has deactivated particular users. If, in the worst case scenario, someone were to erroneously or maliciously deactivate someone, it can be rectified quickly (and you are able to also reactivate the user this way, too).
I manage a very large network and we have not encountered any instances of folks misusing this feature.