Deleting Items from Preservation hold library
Hello, I have a client who needs to free up spaces taken mostly by retention. Since he's already backing up and archiving his data, the retention policy in place for the groups 365 is not needed anymore. He modified his retention policy (in the compliance center) to not take the 365 groups anymore and desactivated the functionnality of retention in the administration of his main SharePoint site. However, when deleting items in the retention library of each SharePoint site (linked to Teams), this error message still appears : "This library contains items that have been modified or deleted but must remain available due to eDiscovery holds. Items cannot be modified or removed." The thing is that we didn't find any eDiscovery strategies in place in the compliance center. Do you have any idea from where this can be from and how we could resolve this issue ? Thank you for your answers !
Deleting a SharePoint site collection when Office 365 retention is On for SharePoint sites
We have retention policies configured in Office 365 security and compliance center for all SharePoint sites. My question is would that prevent an admin from deleting a site collection. We want to delete an empty unused site collection but get an error saying that "A compliance policy is currently blocking this site deletion". How can we delete this site collection without modifying the retention policy.
Preservation Hold library not appearing when both retention labels and policies are applied
It is already known that retention labels published as retention policies 'trump' retention policies created directly in the Information Governance section of the Compliance admin centre. When retention labels are published to all SharePoint sites, they are visible ('explicit') as an option when you choose to 'Apply label to this library' in the document library or list settings. When they are published to specific SharePoint sites, they are only visible in that site, in addition to the 'global' labels. When retention policies are created in the Info Governance section and applied to individual SharePoint sites, they normally create a Preservation Hold library that is visible (via /_layouts/15/viewlsts.aspx?view=14) only to Site Collection Admins, SP Admins and Global Admins. As these policies are invisible to end users they are sometimes described as 'implicit'. They don't include the option to review disposition before deletion. There is nothing to stop you having a combination of explicit retention labels/policies and implicit retention policies on a single site. However, when you do this it appears to hide the Preservation Hold library BUT still deletes content in line with the implicit policy - the deleted content (deleted by 'System account') is in the Recycle Bin. Does anyone have any suggestions how to view the (apparently) hidden preservation hold library on a site that includes explicit retention labels/policies? And no, you can't try '/PreservationHoldLibrary/Forms/AllItems.aspx'. It says 404 not found.
Failed to create Retention Policy in Sharepoint 365
I am using SharePoint 365 E3 Trial Subscription to test our application. In one of tests we need to create a Retention Policy for preserving content from SharePoint sites. When I'm trying to create a policy, I'm getting the following error: We failed to communicate with SharePoint because of: 'The request was aborted: The request was canceled.'. Request: /api/RetentionCompliance Status code: 500 Exception: Microsoft.Exchange.PswsClient.PswsException Diagnostic information: {Version:16.00.2265.005,Environment:WEUPROD,DeploymentId:7deb614ab723416aa8242d781f6fc114,InstanceId:WebRole_IN_2,SID:993e89b2-3df5-40c5-b5af-09ee3cf93f38,CID:65dac505-cf25-43ff-86c7-371c8566c9cc} Time: 2018-04-16T13:03:39.6303371Z ----------------------------- How can I resolve this issue or does anyone know any workaround for it?
Version history and Retention Policies - Why do I have so many versions?
We are using (I believe) the global default of 500 versions for document libraries in SharePoint Online and now we are discovering that the version history is accumulating more than 500 major versions on items in libraries. We have retention policies set for SharePoint sites (do not delete for X years). Is that overriding the version history settings? We have libraries in supporting MSTeams and Communication sites where files are well over the 500 major version limit. 6800+, 7900+ It's kind of insane... I'm not finding the documentation to answer my question very easily. It's also throwing a wrench into backup software that we are trying to run since it doesn't have a setting where it allows us to backup a maximum amount of versions.
