Oct 24 2017 05:54 AM
Oct 24 2017 05:54 AM
I created a few test labels. I am able to delete all labels except label that has been marked as a record. Following powershell code gives an error: "You cannot remove the compliance label because the tag is record label."
How can I delete my label?
Set-ExecutionPolicy RemoteSigned $UserCredential = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection Import-PSSession $Session IRemove-ComplianceTag -Identity "mytestlabel" Remove-PSSession $Session
Oct 24 2017 11:07 AM
As noted in the documentation, record labels cannot be removed or edited: https://support.office.com/en-us/article/Overview-of-labels-af398293-c69d-465e-a249-d74561552d30#rec...
Oct 24 2017 11:36 AM
Oh! And here I was thinking "A record can’t be modified or deleted" would not apply since I am not actually published my label. No warning whatsoever. Microsoft will have many happy customers using their production tenant as a test-bed for labels. It's a good thing I used a test tenant.
Aug 07 2018 07:55 AM - edited Aug 07 2018 07:56 AM
Microsoft really needs to change the way they describe them in the actual settings as well. You generally think that "users" are by default not inclusive to the Administrators in terms of permissions. The assumption (I know &$$ out of you and me) was that I would apply this label to an item and it would prevent a user from deleting the content accidentally. Not that the label itself would be prevented from deletion by the administrator.
Aug 17 2018 11:31 AM
So nice! So I made a typo and now we'll have to live with it on the tenant for ever. Clever, very clever!
Mar 21 2019 09:16 AM
@Eric Beaudry There is nothing in Microsoft's actual documentation (link provided above) that suggests the label cannot be deleted. It talks specifically about items that have been declared as a record. So the label should be able to be deleted. MS needs to fix this ASAP.