AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Microsoft word support chat1/7/2024 ![]() ![]() If you DID remove a hold at some point that was responsible for the PHL, there is a ridiculous grace period similar to DelayHold on Mailboxes. One, run this diagnostic on the site if you already haven't: But hopefully this can help you push through best of luck. That’s the fight that I had to go through, and I know it sucks. This report is what finally got them to admit that there were faulty orphaned policies against our sites, and then it was additional fighting to get the product group to purge said orphans from our sites. Push and fight to get your case to have the technician perform a scan/report of all applied retention policies against a provided list of sites, and provide what retention policies (if any) should be applied to those sites, by retention policy ID. Open a Sev A about orphaned retention policies, and explain to them that the inability to remove these orphaned holds places your organization into potential legal peril as you are culpable for data that is being retained outside of and against your retention policies. Second step is the not fun one, but it’s the only option. It will then disassociate the orphaned policy from the site, and you can remove content or the site itself. ![]() Once in a blue moon, it will find and admit that the site has a bad retention policy applied, and it will ask if you want to fix it. ![]() Search something like “diag SharePoint retention policy” and one of the results should lead you to a scanning process that will check a provided SP site for an error/orphaned retention policy. What you have are orphaned retention policies still locked to the sites in the backend, and nothing we can see or do can fix it in most cases.įirst step that you can try solo: go to where you open an MS case and have their stupid search bar. Ok, I’ve been through your same pain, but thankfully I picked enough fights and our CSAM supported us enough to get things going. the content on the site is 100% blown away except for the damn preservation libraries. Policy checks on each site shows "No Policies". No ediscovery cases /holds have been created or active in over 6 months, and all retention labels have specifically excluded certain sites, over 4 months ago, all the sites impacted went through the orphan retention check and show no issue. Some people have mentioned some things, just to clarify. To the extent that I may no longer advocate for its use within our organization.Įdit: Good to see I am not alone in these stressors, glad to see some people are getting some good experiences!. I must admit that my experience has left me disappointed and disconnected from this product. ![]() It has been challenging to find anyone, particularly within this specific ticket, who possesses the necessary expertise in this product. These included manual deletion within the preservation library and unrelated troubleshooting approaches, such as Wireshark tracking. What concerns me most is that the support personnel consistently recommended actions that deviated from the intended design of the Microsoft 365 environment or imply its a settings issue our end. Despite our efforts, which included screen-sharing to demonstrate errors when manipulating the files or the site, we remained unable to delete them due to an orphaned active eDiscovery hold. Their suggested remedies included instructions to "just delete it" or "remove the label from the files in the preservation hold library." They also directed us to third-party websites with PowerShell commands for deleting files in preservation libraries. Unfortunately, we have not received effective support from either the SharePoint or compliance teams. Spent many hours searching the webs for similar situations, trying differing solutions.įinally, I bit the bullet and submitted a support ticket for a solution, I have submitted 3 tickets for this situation alone, almost 4 months it has been discussed. We thoroughly checked our compliance center and found no active eDiscovery cases or holds, and all retention labels had explicitly excluded these sites. Upon further investigation, we discovered that preservation hold libraries were enabled. There were no apparent obstacles preventing their removal. Recently, while cleaning up old assets/sites in our tenant, we encountered an issue where certain old classic sites could not be deleted. I mention this to convey my proficiency in various administrative areas, including PowerShell. My specialization lies in content and record management. I hold an active certification as a Microsoft 365 Administrator Expert and have been using Microsoft 365 for nearly eight years. I am a Global Administrator for a small to mid-sized organization and have been working in the compliance domain for several years. just a rant a word of wise for anyone who wants to use 365. ![]()
0 Comments
Read More
Leave a Reply. |