Removed users

[Diane Kennedy]

Does anyone know how to get a searchable list of recently deactivated users or view them all on one page? It's really a pain to verify if a user has been deactivated using the Yammer UI.

[#2]

If you're network admin the data export can show you that information.

[#3]

I have network admins that handle deactivations. I don't care to give them that kind of access, and I don't want to have to look these up for them. I was hoping I could code something for them. 

It's unfortunate that this info isn't provided on one screen and isn't searchable. 

Since I have your attention, Angus, I'm trying to test and prove that now that we are using Office 365 identity management, once we disable the AD account, former employees can no longer access Yammer. My assumption is that all sessions would terminate at that point. However, so far in our testing, it appears they can still access the network via the mobile app. Any thoughts or suggestions on this? 

[#4]

Only verified admins can get the export though, right?

[#5]

You can't trigger an export yourself via powershell/API and also send the email with the attached file via the shell as well? Is there any concern about sending the users file?

In excel, or specifically PowerQuery in excel, you can set the deactivated date or suspended date to be within X amount of days... or just simply sort by date at that point.

You could also just run the export api and export it to a shared drive and have it refresh daily.

[#6]

With the parameters you described, Diane, I would recommend something like what Victor is laying out.  You could craft a PowerShell script to run the export API, dump the results to a result set or flat file, and then do your logic based on that result set.  After it runs you can have something emailed to the folks who have to process it, update a SharePoint list, whatever.  

I've seen what you're talking about, how when an account is disabled its token can still be active for a little while.  I've found that blocking those accounts kills the active token.  Also, through the UI you can force a session to end, though I'm sure you don't want to do that manually.  I'm guessing that there are undocumented APIs you can use to force all the sessions to end, which you can add to your script.  

[#7]

Yes, we can do this through the UI, but I'm trying to eliminate that extra step. We are in a "reinvention" at the moment with hundreds of people being laid off. I'm trying to automate and simplify as much as possible.

It seems like it *should* be pretty straightforward that when the user's AD account is disabled their Yammer account is disabled and all their sessions are terminated.

[#8]

For clarification, the users who are being deactivated in AD are showing up as suspended in Yammer, but still have access? Or is their deactivation in AD not triggering anything.

I'm trying to gain insight. Have you read this article? https://blogs.technet.microsoft.com/askyammer/2016/11/01/when-does-a-user-getting-logged-out-of-yamm...

[#9]

I'm looking at the article now. Thanks for sharing.

In our testing thus far, the user is able to continue accessing Yammer after AD is disabled so long as they don't close their browser or mobile app. We're still testing on this, however.

[#10]

In your testing, see if there's a timeout.  It SHOULD invalidate the authentication token after a little while, especially if you're using O365 Identity Enforced.  

[#11]

We're going to check that out tomorrow. I'm hoping it's 30 minutes or less.