Enforcing Default Retention Labels in Office 365

%3CLINGO-SUB%20id%3D%22lingo-sub-138280%22%20slang%3D%22en-US%22%3EEnforcing%20Default%20Retention%20Labels%20in%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138280%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Label%20feature%20in%20Security%20and%20Compliance%20Center%20works%20great%20to%20apply%20consistent%20policies%20across%20O365%20capabilities.%20However%2C%20there%20does%20not%20appear%20to%20be%20a%20way%20to%20enforce%20a%20default%20selection%20in%20SharePoint%20(OneDrive%2C%20Groups%20or%20Sites)%20at%20a%20high%20level%20through%20the%20Security%20and%20Compliance%20or%20site%20Collection%20settings.%20At%20this%20time%20I%20have%20not%20been%20able%20to%20find%20an%20exposed%20property%20that%20will%20allow%20validation%20and%20setting%20the%20value%20using%20PowerShell%20either.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIs%20there%20a%20way%2C%20now%20or%20on%20the%20roadmap%2C%20to%20allow%20an%20administrator%20to%20verify%20that%20a%20default%20Label%26nbsp%3Bhas%20been%20set%3F%26nbsp%3BAlso%2C%20as%20part%20of%20provisioning%20(either%20during%20or%20after)%20can%20a%20default%20value%20for%20a%20SharePoint%20library%20be%20set%26nbsp%3Bwithout%20modifying%20the%20settings%20through%20the%20UI%20for%20each%20library%20in%20a%20site.%20Also%20to%20enforce%20a%20selection%20when%20a%20new%20library%20is%20created%20on%20an%20existing%20site%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIdeally%2C%20it%20would%20be%20helpful%20to%20allow%20setting%20a%20tenant%20wide%20policy%20for%20each%20platform%20(Mail%2C%20OneDrive%2C%20Groups%20and%20SharePoint)%2C%20similar%20to%20how%20Exchange%20does%20tags%2C%20that%20are%20applied%20when%20a%20new%20library%20is%20created.%20The%20owner%20of%20the%20library%20can%20modify%20it%20afterwards%20if%20needed%2C%20along%20with%20document%20level%20updates.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-138280%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%20Groups%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174613%22%20slang%3D%22en-US%22%3ERe%3A%20Enforcing%20Default%20Retention%20Labels%20in%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174613%22%20slang%3D%22en-US%22%3E%3CP%3EFully%20support%20this.%20We%20have%20a%203%20tier%20classification%20schema%20in%20our%20ISMS.%20We'd%20like%20any%20documents%20that%20are%20brought%20into%20our%20SharePoint%20to%20have%20the%20lowest%20form%20of%20Classification%20automatically%20set.%20As%20opposed%20to%20trying%20to%20create%20a%20workaround%20that%20'tricks'%20SharePoint%20(365)%20into%20flagging%20it.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-166729%22%20slang%3D%22en-US%22%3ERe%3A%20Enforcing%20Default%20Retention%20Labels%20in%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-166729%22%20slang%3D%22en-US%22%3E%3CP%3EI%26nbsp%3B%20should%20probably%20add%2C%20that%20we%20can%20define%20a%20default%20deletion%2Fretention%20policy%20to%20OneDrive..%20but%20this%20is%20not%20visible%20to%20users%20in%20the%20same%20way%20that%20labels%20are.%20If%20I%20apply%20a%202%20year%20deletion%20policy%2C%20there%20is%20nothing%20to%20tell%20the%20user%20that%20their%20content%20will%20be%20deleted%202%20years%20after%20creation.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20it%20instead%20had%20a%20default%20label%20applied%20called%20%22Content%20Deletion%20-%202%20years%20from%20creation%22%20then%20this%20would%20be%20much%20more%20visible%20and%20consumable%20by%20the%20user.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-161268%22%20slang%3D%22en-US%22%3ERe%3A%20Enforcing%20Default%20Retention%20Labels%20in%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-161268%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20addition%20of%20a%20default%20label%20would%20be%20a%20major%20improvement%20to%20the%20current%20system%2C%20especially%20when%20combined%20with%20targeted%20policies%20based%20on%20URL.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'd%20also%20like%20to%20see%20the%20ability%20to%20define%20default%20labels%20on%20OneDrive%20that%20doesn't%20require%20the%20use%20of%20dynamic%20labelling%20(E5%20only).%20This%20would%20allow%20organisations%20to%20have%20the%20ability%20to%20place%20some%20form%20of%20governance%20on%20OneDrive%20that%20doesn't%20require%20the%20users%20to%20self%20label%20content%2C%20instead%20a%20default%20retention%20period%20could%20be%20applied%20and%20labels%20provided%20to%20allow%20users%20to%20change%20the%20retention%20themselves.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPaul.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

The Label feature in Security and Compliance Center works great to apply consistent policies across O365 capabilities. However, there does not appear to be a way to enforce a default selection in SharePoint (OneDrive, Groups or Sites) at a high level through the Security and Compliance or site Collection settings. At this time I have not been able to find an exposed property that will allow validation and setting the value using PowerShell either.

 

Is there a way, now or on the roadmap, to allow an administrator to verify that a default Label has been set? Also, as part of provisioning (either during or after) can a default value for a SharePoint library be set without modifying the settings through the UI for each library in a site. Also to enforce a selection when a new library is created on an existing site?

 

Ideally, it would be helpful to allow setting a tenant wide policy for each platform (Mail, OneDrive, Groups and SharePoint), similar to how Exchange does tags, that are applied when a new library is created. The owner of the library can modify it afterwards if needed, along with document level updates.

3 Replies
Highlighted

The addition of a default label would be a major improvement to the current system, especially when combined with targeted policies based on URL.

 

I'd also like to see the ability to define default labels on OneDrive that doesn't require the use of dynamic labelling (E5 only). This would allow organisations to have the ability to place some form of governance on OneDrive that doesn't require the users to self label content, instead a default retention period could be applied and labels provided to allow users to change the retention themselves.

 

Paul.

Highlighted

I  should probably add, that we can define a default deletion/retention policy to OneDrive.. but this is not visible to users in the same way that labels are. If I apply a 2 year deletion policy, there is nothing to tell the user that their content will be deleted 2 years after creation.

 

If it instead had a default label applied called "Content Deletion - 2 years from creation" then this would be much more visible and consumable by the user.

Highlighted

Fully support this. We have a 3 tier classification schema in our ISMS. We'd like any documents that are brought into our SharePoint to have the lowest form of Classification automatically set. As opposed to trying to create a workaround that 'tricks' SharePoint (365) into flagging it.