Compliance admins should be able to delete labels marked as record
Under Classifications, a label created and marked as Record cannot be later changed or, more importantly, deleted by any administrator. As an admin can remove a document from bearing the status of record, they should therefore be able to delete a label with Record status. The combination of Record and Delete after 'x' years is very dangerous - not to mention a department may update their requirements in time.
It is surprising that Microsoft has not addressed this yet!! I have 6-7 labels sitting around because of this that are not even used or published and I cannot delete them. As shown here, their approach is hit and miss. Very disappointing Microsoft! Please fix this!
I've spoken to two different MS Support techs and neither seem willing or able to help remove labels. I'm curious how those of you who have commented and have had success through MS Support found resolution.
I'm following the recommended instructions in this article:
But, the response I'm getting looks like this:
"We are not allowed to access and manage the information in customer's organization.
For example: we have backend to check how many items in user mailbox, ok we can know it is 19GB/100GB. But we cannot see, copy or delete anything in it, that will against our compliance policy. Also that feature is by design, please keep monitor in uservoice and I will help to collect vote for you!
Thanks for your understanding."
This is definitely a must have! Currently I can't even set a sensitivity label with the correct name as I now can't rename or delete this Record Label. It wouldn't be too bad if I could rename it but it's not even possible to do that!
I've got two open support tickets for removing labels with the record classification. Very frustrating process :-( Would be great if we could do this ourselves.
100% agree - it is bizarre that Record Type labels that are not in use (or were test labels) cannot be deleted... And no warnings are given whilst defining the label - sloppy MS
Pranav Kothare commented
Anything that end users create in their tenants, they should be able to control/manage/delete as needed. Labels and records management is no exception to that rule.
Global admins should be able to control all the information under their tenancy.
Agreed - if the label is unused, it should be removable. I had to get Microsoft to delete several labels from our tenancy through the back end which I had created while troubleshooting another bug with their retention area. It makes no sense NOT to allow label deletion for labels which have not been used.
Martin Allard commented
Same for me, if no files ever got a retention label marked as a record, there is no reason to prevent deletion of this label. Further more, the information tip related to the "Is Record" option is misleading as it only mentions that files can no longer be deleted, not the label it self.
Makes it very difficult to roll out records management using O365 if we can't update labels. Deleting/updating labels either for POC purposes, requirement change or errors in creation is absolutely necessary.
yes very much needed. as we can not keep forever in tenant.
Same for me. I've created some test label with 'Use label to classify content as a "Record"' checked, but never used it. I'm not able to delete these labels anymore. From UX perspective, it's quite frustrating that you can create items, but not edit or remove them anymore, even if you're an admin. Please fix this Microsoft.
Joanne Klein commented
Note: this also happens if a retention label is defined "based on an event". As soon as you save the label, you can no longer delete it.
I agree, this is extremely frustrating in cases where labels are created as a proof of concept. Ideally there should be a way to delete them, especially where they are not being used at all. It would have been nice that this behaviour was highlighted on label creation so you could make an informed choice whether to proceed or not.
Hazem Zureiqat commented
Has anyone been able to delete a label marked as Record by contacting support or using PowerShell?
Helene Kaltak commented
This is very misleading, I made the mistake of marking a label as a record which proliferated as a column across all content types. At least a global admin should have the ability to delete a label. In the records management world organizations merge, business activities change and therefore flexibility is required to update/delete labels to reflect a records file plan or classification structure.
John Matsunaga commented
Jan Egil Andreassen commented
We are currently implemented Labels as the mechanism for handling records in our tenant, but the possibility to not change or delete a label that is marked as Record hinder us to set this into production. As minimum global admin should be able to change and delete a Label that is marked as Record. Consideration/support is needed for what shall be done on existing content that is tagged with that label, should it be changed for existing content? Same goes for when deleting a Label.
Syed Mujtaba Hassan commented
We were looking for different options to implement Our Information Managmenet policies and created a Label as a proof-of-concept. Now we are unable even to rename it. This is too awfull for a Product like this.
I understand the purpose of records markers in retention policies is to protect official company records. There is, however, a sizeable gap in the functionality to be able to administer such labels even before they are published for use. i.e., even an unpublished (and therefore completely unused) retention label with a company record marker cannot be edited or deleted in any way. Guidance on https://docs.microsoft.com/en-us/office365/securitycompliance/labels#using-retention-labels-for-records-management does NOT alert anyone to this fact as it notes "WHEN AN ITEM IS LABELLED AS A RECORD, four things happen: 1. The item can't be permanently deleted; 2. The item can't be edited; 3. The label can't be changed; 4. The label can't be removed."
Actually, the situation is IF A LABEL IS CREATED (AND EVEN NOT PUBLISHED) WHICH APPLIES A RECORD MARKER those four things happen. This is going to quickly result in companies having a plethora of useless and unused retention labels cluttering up their admin consoles and worst still (if published) confusion for their users.
I suggest that Powershell functionality should be introduced to allow admins to manage retention labels which have record markers.
James Shuriff commented
"If content is classified as a record, users won't be able to edit or delete the content or change or remove the label. However, they'll still be able to edit the content's metadata."
Very misleading. It does not even imply that Administrators can't delete or even edit the label. I agree with this completely and I think it's awful that this has been floating around for over a year.