SOLVED

Why has the ability to create a disposition label based on Last Modified disappeared in the UI?

%3CLINGO-SUB%20id%3D%22lingo-sub-1866847%22%20slang%3D%22en-US%22%3EWhy%20has%20the%20ability%20to%20create%20a%20disposition%20label%20based%20on%20Last%20Modified%20disappeared%20in%20the%20UI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1866847%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20setting%20up%20default%20disposition%20labels%20in%20Office%20365...%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Old%20Security%20and%20Compliance%20Centre%20allowed%20me%20to%20do%20this..%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Seasto_0-1604929116150.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F232318i7ECF587CEA170D9A%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Seasto_0-1604929116150.png%22%20alt%3D%22Seasto_0-1604929116150.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20the%20new%20Office%20365%20Compliance%20Centre%20only%20allows%20this%20based%20on%20Created%20Date...%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Seasto_1-1604925977235.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F232316iB4F4D306E18DD5BE%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Seasto_1-1604925977235.png%22%20alt%3D%22Seasto_1-1604925977235.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EI%20have%20been%20working%20in%20setting%20up%20Information%20Governance%20for%20over%2015%20years%20now%20and%20can%20easily%20state%20that%20the%20use%20case%20for%20Last%20Modified%20is%20way%20more%20common%20than%20the%20use%20case%20for%20Created%20(especially%20in%20current%20cloud%20migration%20scenarios)%2C%20so%20why%20has%20the%20UI%20feature%20disappeared%20when%20it%20is%20available%20in%20the%20old%20interface%20and%20the%20Exchange%20Online%20PowerShell%20API's%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20Regards.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1866847%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECompliance%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1867589%22%20slang%3D%22en-US%22%3ERe%3A%20Why%20has%20the%20ability%20to%20create%20a%20disposition%20label%20based%20on%20Last%20Modified%20disappeared%20in%20the%20UI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1867589%22%20slang%3D%22en-US%22%3E%3CP%3EUse%20the%20first%20option%20here%2C%20%22Retain%20items%20for%20specific%20period%22%2C%20then%20select%20the%20period%20and%20when%20to%20trigger%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1870572%22%20slang%3D%22en-US%22%3ERe%3A%20Why%20has%20the%20ability%20to%20create%20a%20disposition%20label%20based%20on%20Last%20Modified%20disappeared%20in%20the%20UI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1870572%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3E%26nbsp%3BI%20specifically%20stated%20Disposition%20e.g.%20Delete%20Only%2C%20I%20do%20not%20want%20the%20documents%20Retained%20%3F%3C%2FP%3E%3CP%3ETo%20further%20clarify%2C%20if%20I%20set%20to%20Retain%20this%20will%20have%20an%20undesirable%20effect%20on%20the%20ability%20to%20edit%20documents%20in%20a%20modern%20SharePoint%20Document%20Library.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHence%20the%20business%20or%20use%20case%20in%20this%20scenario%20aligns%20to%20the%20DELETE%20and%20not%20the%20KEEPANDDELETE%20(PowerShell%20Triggers)%20REF%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fnew-compliancetag%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fnew-compliancetag%3Fview%3Dexchange-ps%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20aware%20it%20can%20be%20done%20in%20PowerShell%20and%20in%20the%20old%20interface%20I%20am%20just%20wondering%20why%20such%20a%20critical%20piece%20of%20end%20user%20functionality%20has%20been%20omitted%20from%20the%20new%20Compliance%20Centre%2C%20e.g.%20for%20Information%20Governance%20end%20users%20that%20are%20not%20aware%20of%20the%20PowerShell%20options.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20did%20try%20using%20the%20Retain%20option%20to%20set%20the%20trigger%20and%20then%20moved%20the%20main%20option%20to%20DELETE%20but%20it%20defaults%20the%20trigger%20back%20to%20being%20based%20on%20the%20Created%20Date%2C%20which%20again%20is%20not%20the%20use%20case.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20Regards%2C%3C%2FP%3E%3CP%3ESeasto%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I am setting up default disposition labels in Office 365... 

The Old Security and Compliance Centre allowed me to do this..

Seasto_0-1604929116150.png

 

However the new Office 365 Compliance Centre only allows this based on Created Date...

Seasto_1-1604925977235.png

I have been working in setting up Information Governance for over 15 years now and can easily state that the use case for Last Modified is way more common than the use case for Created (especially in current cloud migration scenarios), so why has the UI feature disappeared when it is available in the old interface and the Exchange Online PowerShell API's?

 

Kind Regards.

3 Replies

Use the first option here, "Retain items for specific period", then select the period and when to trigger it.

@Vasil Michev I specifically stated Disposition e.g. Delete Only, I do not want the documents Retained ?

To further clarify, if I set to Retain this will have an undesirable effect on the ability to edit documents in a modern SharePoint Document Library.

 

Hence the business or use case in this scenario aligns to the DELETE and not the KEEPANDDELETE (PowerShell Triggers) REF: https://docs.microsoft.com/en-us/powershell/module/exchange/new-compliancetag?view=exchange-ps

 

I am aware it can be done in PowerShell and in the old interface I am just wondering why such a critical piece of end user functionality has been omitted from the new Compliance Centre, e.g. for Information Governance end users that are not aware of the PowerShell options.

 

I did try using the Retain option to set the trigger and then moved the main option to DELETE but it defaults the trigger back to being based on the Created Date, which again is not the use case.

 

Kind Regards,

Seasto 

best response confirmed by Seasto (New Contributor)
Solution

Sorry for anyone who comes across this the actual option is available but not obvious.

If you select the Custom Option from the Drop-Down the necessary fields will dynamically appear.

 

Regards,

Seasto