Home

Deleted O365 / AzureAD users still showing up in Yammer search box

%3CLINGO-SUB%20id%3D%22lingo-sub-172008%22%20slang%3D%22en-US%22%3EDeleted%20O365%20%2F%20AzureAD%20users%20still%20showing%20up%20in%20Yammer%20search%20box%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172008%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20was%20wondering%20if%20anyone%20knows%20why%26nbsp%3Busers%20that%20were%20deleted%20in%20Office%20365%20%2F%20AzureAD%20still%20show%20up%20in%20the%20Yammer%20search%20box.%20What%20I%20be%20done%20about%20that%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20help.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-172008%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eprofile%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178727%22%20slang%3D%22en-US%22%3ERe%3A%20Deleted%20O365%20%2F%20AzureAD%20users%20still%20showing%20up%20in%20Yammer%20search%20box%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178727%22%20slang%3D%22en-US%22%3E%3CP%3EVery%20strange.%20The%20only%20thing%20I%20can%20think%20of%20is%20using%20the%20API%20to%20delete%20them%2C%20but%20that%20will%20probably%26nbsp%3Bgive%20you%20the%20same%20error.%20Error%20message%20could%20be%20more%20specific%2C%20but%20it%20won't%20help%20find%20a%20solution%20as%20you%20have%20already%20tried%20everything.%20Having%20the%20O365%20identities%20enforced%20at%20least%20assures%20you%20that%20they%20can't%20access%20Yammer%20as%20they%20have%20to%20use%20their%20O365%20credentials%20to%20log%20in.%20Would%20suggest%20creating%20a%20ticket%20with%20Microsoft%20support%20and%20asking%20them%20to%26nbsp%3Bdo%20this%20for%20you.%20Would%20be%20interesting%20to%20learn%20what%20has%20caused%20this.%20My%20guess%20is%20that%20you%20are%20dealing%20with%20a%20bug.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174123%22%20slang%3D%22en-US%22%3ERe%3A%20Deleted%20O365%20%2F%20AzureAD%20users%20still%20showing%20up%20in%20Yammer%20search%20box%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174123%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20tip.%20I've%20not%20been%20a%20Yammer%20admin%20in%20our%20tenant%20from%20the%20get%20go%20so%20when%20I%20was%20looking%20into%20enforcing%20O365%20identities%20I%20was%20suprised%20to%20learn%20that%20this%20setting%20was%20already%20enabled.%3C%2FP%3E%0A%3CP%3ESo%20this%20is%20not%20the%20solution%2C%20unfortunately.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%20I%20went%20back%20to%20the%20%22Remove%20users%22%20menu.%20One%20of%20the%20users%20not%20in%20our%20O365%20tenant%20anymore%20still%20showed%20up%20in%20the%20search%20box%20there.%20So%20I%20tried%20to%20permanently%20remove%20this%20user%20like%20so%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20753px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F30690iF8223591E4469D75%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22yammer_unableToDelete2.png%22%20title%3D%22yammer_unableToDelete2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20my%20surprise%20it's%20not%20possible%20to%20remove%20this%20user%2C%20see%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20646px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F30689iB1BD0F77BEF81146%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22yammer_unableToDelete.png%22%20title%3D%22yammer_unableToDelete.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStrangely%20enough%2C%20this%20user%20has%20a%20join%20date%20of%201970.%20There're%20a%20bunge%20of%20users%20that%20have%20this%20join%20date%20when%20I%20look%20at%20the%20users%20report%20I%20can%20create%20in%20yammer.%20On%20the%20other%20hand%2C%20not%20all%20of%20thus%20users%20can%20be%20found%20via%20the%20search%20box.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20could%20understand%20if%20you%20have%20no%20further%20ideas%2C%20your%20help%20is%20still%20appreciated.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174064%22%20slang%3D%22en-US%22%3ERe%3A%20Deleted%20O365%20%2F%20AzureAD%20users%20still%20showing%20up%20in%20Yammer%20search%20box%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174064%22%20slang%3D%22en-US%22%3E%3CP%3EHere's%20a%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fenforce-office-365-identity-for-yammer-users-008f940b-6bec-47fc-bcc6-9c6133467562%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Elink%3C%2FA%3E%26nbsp%3Bto%20a%20page%20with%20more%20info.%26nbsp%3B%20Office%20365%20identities%20are%20not%20enforced%20in%20Yammer%20by%20default.%20This%20means%20that%20users%20are%20making%20use%20of%20Yammer%20identities.%20This%20is%20the%20case%20because%20of%20the%20freemium%20version%20of%20Yammer.%20Anyone%20with%20an%20email%20address%20from%20a%20specific%20domain%20can%20create%20an%20account%20on%20Yammer%20and%20will%20be%20added%20to%20a%20network%20with%20colleagues%20with%20an%20email%20address%20from%20that%20same%20domain.%20This%20is%20why%20you%20end%20up%20having%20multiple%20networks%20if%20you%20have%20subdomains.%20Enforcing%20the%20O365%20identities%20means%20that%20the%20users%20from%20now%20on%20will%20make%20use%20of%20their%20O365%20account%20as%20they%20will%20get%20a%20redirect%20to%20the%20O365%20login%20page%20when%20they%20enter%20their%20email%20address.%20Enabling%20this%20feature%20also%20allows%20you%20to%20block%20access%20for%20users%20without%20a%20Yammer%20license%2C%20just%20as%20you%20currently%20manage%20access%20to%20other%20O365%20applications.%20The%20issue%20of%20the%20users%20showing%20up%20in%20search%20even%20though%20they%20have%20been%20deleted%20should%20be%20solved%20when%20O365%20identities%20are%20enforced.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174053%22%20slang%3D%22en-US%22%3ERe%3A%20Deleted%20O365%20%2F%20AzureAD%20users%20still%20showing%20up%20in%20Yammer%20search%20box%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174053%22%20slang%3D%22en-US%22%3EHi%2C%20what%20do%20you%20mean%20by%20%22enforced%20O365%20identities%22%3F%20Our%20users%20come%20from%20local%20AD%20synced%20to%20AzureAD.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-173520%22%20slang%3D%22en-US%22%3ERe%3A%20Deleted%20O365%20%2F%20AzureAD%20users%20still%20showing%20up%20in%20Yammer%20search%20box%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-173520%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20deleted%20a%20user%20in%20O365%20in%20my%20test%20environment%20to%20see%20what%20happens.%20The%20account%20is%20not%20listed%20anymore%20in%20the%20people%20directory%20in%20Yammer%20and%20also%20doesn't%20show%20up%20via%20search.%20This%20took%20just%20a%20couple%20of%20seconds.%20Have%20you%20enforced%20O365%20identities%3F%20Would%20be%20happy%20to%20test%20when%20that%20is%20disabled%2C%20but%20it's%20not%20something%20I%20can%20change%20without%20creating%20a%20ticket%20with%20MSFT%20support.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-173507%22%20slang%3D%22en-US%22%3ERe%3A%20Deleted%20O365%20%2F%20AzureAD%20users%20still%20showing%20up%20in%20Yammer%20search%20box%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-173507%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20suggestion.%20I%20tried%20this%20but%20the%20user%20still%20shows%20up%20in%20the%20Yammer%20searchbox.%3CBR%20%2F%3EAre%20you%20able%20to%20reproduce%20this%20behaviour%20at%20all%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172652%22%20slang%3D%22en-US%22%3ERe%3A%20Deleted%20O365%20%2F%20AzureAD%20users%20still%20showing%20up%20in%20Yammer%20search%20box%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172652%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20you%20tried%20blocking%20the%20users%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172589%22%20slang%3D%22en-US%22%3ERe%3A%20Deleted%20O365%20%2F%20AzureAD%20users%20still%20showing%20up%20in%20Yammer%20search%20box%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172589%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20reply.%3CBR%20%2F%3EI%20found%20that%20all%20users%20deleted%20in%20O365%2FAAD%20will%20get%20the%20%22soft%20delete%22%20state.%3CBR%20%2F%3EUnder%20%22Remove%20Users%22%20they%20don't%20show%20up%20in%20the%20list%20of%20deactivated%20users%2C%20though%20they%20can%20be%20found%20via%20the%20search%20box%20above.%20%3CBR%20%2F%3EMoreover%2C%20more%20recently%20removed%20O365%2FAAD%20users%20to%20appear%20in%20that%20list%20of%20deactivated%20users%20but%20cannot%20be%20found%20through%20the%20search%20box.%3CBR%20%2F%3EI%20guess%20at%20some%20point%20something%20must%20have%20changed%20in%20the%20way%20Yammer%20handles%20those%20users%20deleted%20in%20O365%2FAAD.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172041%22%20slang%3D%22en-US%22%3ERe%3A%20Deleted%20O365%20%2F%20AzureAD%20users%20still%20showing%20up%20in%20Yammer%20search%20box%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172041%22%20slang%3D%22en-US%22%3E%3CP%3ETheir%20posts%2Fcomments%2Ffiles%20could%20still%20be%20of%20value%20and%20being%20able%20to%20find%20them%20via%20search%20gives%20you%20an%20easy%20way%20to%20access%20that.%20Users%20deleted%20from%20O365%2FAAD%20will%20get%20the%20%22deactivated%22%20status%20in%20Yammer.%20You%20can%20go%20to%20the%20%3CSTRONG%3Eadmin%20setting%20%26gt%3B%20remove%20users%3C%2FSTRONG%3Eand%20delete%20the%20accounts%20there.%20It's%20been%20a%20while%20since%20I%20did%20this%2C%20but%20if%20I%20remember%20correctly%2C%20they%20shouldn't%20show%20up%20anymore%20via%20search.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Florian Hein
Regular Contributor

Hello,

 

I was wondering if anyone knows why users that were deleted in Office 365 / AzureAD still show up in the Yammer search box. What I be done about that?

 

Thanks for your help.

9 Replies
Highlighted

Their posts/comments/files could still be of value and being able to find them via search gives you an easy way to access that. Users deleted from O365/AAD will get the "deactivated" status in Yammer. You can go to the admin setting > remove users and delete the accounts there. It's been a while since I did this, but if I remember correctly, they shouldn't show up anymore via search. 

Highlighted

Thanks for your reply.
I found that all users deleted in O365/AAD will get the "soft delete" state.
Under "Remove Users" they don't show up in the list of deactivated users, though they can be found via the search box above.
Moreover, more recently removed O365/AAD users to appear in that list of deactivated users but cannot be found through the search box.
I guess at some point something must have changed in the way Yammer handles those users deleted in O365/AAD.

Highlighted

Have you tried blocking the users? 

Highlighted
Thanks for the suggestion. I tried this but the user still shows up in the Yammer searchbox.
Are you able to reproduce this behaviour at all?
Highlighted

I just deleted a user in O365 in my test environment to see what happens. The account is not listed anymore in the people directory in Yammer and also doesn't show up via search. This took just a couple of seconds. Have you enforced O365 identities? Would be happy to test when that is disabled, but it's not something I can change without creating a ticket with MSFT support. 

Highlighted
Hi, what do you mean by "enforced O365 identities"? Our users come from local AD synced to AzureAD.
Highlighted

Here's a link to a page with more info.  Office 365 identities are not enforced in Yammer by default. This means that users are making use of Yammer identities. This is the case because of the freemium version of Yammer. Anyone with an email address from a specific domain can create an account on Yammer and will be added to a network with colleagues with an email address from that same domain. This is why you end up having multiple networks if you have subdomains. Enforcing the O365 identities means that the users from now on will make use of their O365 account as they will get a redirect to the O365 login page when they enter their email address. Enabling this feature also allows you to block access for users without a Yammer license, just as you currently manage access to other O365 applications. The issue of the users showing up in search even though they have been deleted should be solved when O365 identities are enforced. 

Highlighted

Thanks for the tip. I've not been a Yammer admin in our tenant from the get go so when I was looking into enforcing O365 identities I was suprised to learn that this setting was already enabled.

So this is not the solution, unfortunately.

 

So I went back to the "Remove users" menu. One of the users not in our O365 tenant anymore still showed up in the search box there. So I tried to permanently remove this user like so:

 

yammer_unableToDelete2.png

 

To my surprise it's not possible to remove this user, see:

 

yammer_unableToDelete.png

 

Strangely enough, this user has a join date of 1970. There're a bunge of users that have this join date when I look at the users report I can create in yammer. On the other hand, not all of thus users can be found via the search box.

 

I could understand if you have no further ideas, your help is still appreciated.

 

Thanks.

Highlighted

Very strange. The only thing I can think of is using the API to delete them, but that will probably give you the same error. Error message could be more specific, but it won't help find a solution as you have already tried everything. Having the O365 identities enforced at least assures you that they can't access Yammer as they have to use their O365 credentials to log in. Would suggest creating a ticket with Microsoft support and asking them to do this for you. Would be interesting to learn what has caused this. My guess is that you are dealing with a bug. 

Related Conversations