Remove deleted sites from sharepoint frequent sites view
remove deleted site from frequent sites
I have tried "Unfollow", I have remove the groups from Azure, I have used PowerShell to delete those 3 old sites, nothing works. I been in a battle with those 3 tiles for 6 days now. Any real solution out there?
Also, what happened what Tobias wrote "TobiasAT commented · April 11, 2018 12:48". "Just to mention, this is a bug. In February I opened a support case for the issue. MS will implement a global fix at the end of April, or in May.". Again, Any real solution out there?
IT Bear commented
I have been following this for almost 2 year but I think I found a potential solution:
First: frequent site is somehow tied to Office Graph and Delve. So you need to disable Office graph in SharePoint admin center -> Setting, select "Don't allow access to Office Graph."
Then open your Delve, go to setting -> Feature setting, disable document tracking.
Finally, go to SharePoint main page (where the frequent site is listed), go to Site settings -> Search -> Search and offline availability. click "Reindex site" to trigger a site crawl.
Log out and wait for 1 hour, log back in, and Voila!! frequent site is empty.
I have tried on my account and it works.
Wait, it looks like this might be fixed. I was having the same issue, and then I noticed that not only was my removed site still being listed, but this removed site was also listed under Following. So I "unfollowed" (click the little star) the removed site and it was no longer listed under Following. Some time later (couple of hours I think), the site was actually gone from my Frequent Sites list. I checked my users and their Frequent Sites lists are not listing the removed site either.
I realize my situation is not significant (I'm working with only 1 site) but maybe unfollowing sites eventually removes the sites from the Frequent Sites list?
It is end of September 2018 and this is still an issue....at least it is for me.
This is an issue for me too
Just to mention, this is a bug. In February I opened a support case for the issue. MS will implement a global fix at the end of April, or in May.