Home

Exchange Online to Remove In-Place Hold and eDiscovery Tool

%3CLINGO-SUB%20id%3D%22lingo-sub-1093956%22%20slang%3D%22en-US%22%3EExchange%20Online%20to%20Remove%20In-Place%20Hold%20and%20eDiscovery%20Tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1093956%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20announced%20the%20retirement%20of%20two%20legacy%20eDiscovery%20tools%20from%20Office%20365.%20The%20first%20is%20V1%20of%20Advanced%20eDiscovery%3B%20the%20second%20is%20Exchange%20Online%20in-place%20hold%20and%20search.Both%20tools%20will%20be%20removed%20from%20Office%20365%20in%20mid-2020.%20The%20big%20question%20is%20how%20Office%20365%20tenants%20who%20are%20currently%20using%20the%20old%20tools%20can%20move%20work%20in%20progress%20to%20the%20new%20tools.%20Stay%20tuned%20for%20more%20information!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Foffice365itpros.com%2F2020%2F01%2F07%2Fmicrosoft-retires-legacy-ediscovery-tools%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foffice365itpros.com%2F2020%2F01%2F07%2Fmicrosoft-retires-legacy-ediscovery-tools%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1093956%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1095522%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20to%20Remove%20In-Place%20Hold%20and%20eDiscovery%20Tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1095522%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'd%20be%20very%20interested%20as%20well%20as%20to%20what%20we%20are%20to%20do%20with%20the%20existing%20Holds%20we%20have%20in%20the%20old%20tools.%20We've%20been%20using%20them%20for%20holding%20ex-employee%20mailboxes.%20I%20did%20start%20in%202017%20to%20put%20those%20holds%20in%20the%20new%20tools%2C%20but%20we%20have%20multi-100s%20of%20mailboxes%20that%20we%20must%20maintain%20going%20forward%20for%20legal%2Fcompliance%20purposes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1095569%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20to%20Remove%20In-Place%20Hold%20and%20eDiscovery%20Tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1095569%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2707%22%20target%3D%22_blank%22%3E%40Cary%20Siemers%3C%2FA%3E%26nbsp%3BThat's%20one%20of%20the%20questions%20I%20have%20with%20the%20Exchange%20product%20group.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1096862%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20to%20Remove%20In-Place%20Hold%20and%20eDiscovery%20Tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1096862%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2707%22%20target%3D%22_blank%22%3E%40Cary%20Siemers%3C%2FA%3E%26nbsp%3B%3CSPAN%3EMicrosoft%20has%20updated%20their%20note%20about%20retiring%20legacy%20eDiscovery%20tools%20and%20the%20Search-Mailbox%20cmdlet.%20Some%20guidance%20is%20now%20available%20for%20how%20to%20use%20PowerShell%20to%20move%20old%20Exchange%20Online%20in-place%20holds%20to%20holds%20in%20Office%20365%20eDiscovery%20cases.%20See%20the%20updated%20text%20at%20%3CA%20href%3D%22https%3A%2F%2Foffice365itpros.com%2F2020%2F01%2F08%2Fposting-microsoft-365-roadmap-items-teams%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foffice365itpros.com%2F2020%2F01%2F08%2Fposting-microsoft-365-roadmap-items-teams%2F%3C%2FA%3E%20for%20more%20information.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1096867%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20to%20Remove%20In-Place%20Hold%20and%20eDiscovery%20Tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1096867%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECool%20and%20thanks!%20I'll%20take%20a%20look.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1096920%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20to%20Remove%20In-Place%20Hold%20and%20eDiscovery%20Tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1096920%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGot%20to%20Step%205%20and%20got%20%22Only%20mailboxes%20are%20supported.%20The%20recipient%20name%40contoso.com%20is%20of%20type%20MailContact%22%20error%20and%20I%20can't%20proceed.%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20look%20at%20the%20values%20in%20%24search.SourceMailboxes%20they%20are%20all%20mailboxes%20and%20the%20MailContact%20in%20the%20error%20response%20isn't%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooks%20like%20Microsoft%20still%20need%20to%20work%20on%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1096973%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20to%20Remove%20In-Place%20Hold%20and%20eDiscovery%20Tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1096973%22%20slang%3D%22en-US%22%3E%3CP%3EOk%2C%20thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1096968%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20to%20Remove%20In-Place%20Hold%20and%20eDiscovery%20Tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1096968%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2707%22%20target%3D%22_blank%22%3E%40Cary%20Siemers%3C%2FA%3E%26nbsp%3BYou%20expected%20the%20PowerShell%20to%20work%20without%20some%20massaging%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETry%3A%3C%2FP%3E%0A%3CP%3E1.%20Create%20the%20policy%3A%3C%2FP%3E%0A%3CP%3E%24policy%20%3D%20New-CaseHoldPolicy%20-Name%20%24search.Name%20-Case%20%24case.Identity%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2.%20Add%20the%20mailboxes%20from%20the%20old%20EXO%20search%3A%3C%2FP%3E%0A%3CP%3Eforeach%20(%24mbx%20in%20%24Search.SourceMailboxes)%20%7B%3CBR%20%2F%3ESet-CaseHoldPolicy%20-Identity%20%24Policy.Name%20-AddExchangeLocation%20(Get-Mailbox%20-Identity%20%24Mbx).PrimarySmtpAddress%20%7D%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E3.%20Check%20that%20all%20the%20mailboxes%20are%20present%3A%3C%2FP%3E%0A%3CP%3Eget-caseholdpolicy%20-Identity%20%24Policy.Name%20%7C%20Ft%20ExchangeLocation%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20also%20found%20that%20the%20code%20didn't%20deal%20with%20inactive%20mailboxes%20too%20well.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBTW%2C%20the%20PowerShell%20cmdlets%20to%20deal%20with%20Office%20365%20eDiscovery%20cases%20is%20covered%20in%20Chapter%2020%20of%20the%20%3CA%20href%3D%22https%3A%2F%2Fgum.co%2FO365IT%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20365%20for%20IT%20Pros%3C%2FA%3E%20eBook.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Tony Redmond
MVP

Microsoft announced the retirement of two legacy eDiscovery tools from Office 365. The first is V1 of Advanced eDiscovery; the second is Exchange Online in-place hold and search.Both tools will be removed from Office 365 in mid-2020. The big question is how Office 365 tenants who are currently using the old tools can move work in progress to the new tools. Stay tuned for more information!

 

https://office365itpros.com/2020/01/07/microsoft-retires-legacy-ediscovery-tools/

7 Replies

@Tony Redmond 

I'd be very interested as well as to what we are to do with the existing Holds we have in the old tools. We've been using them for holding ex-employee mailboxes. I did start in 2017 to put those holds in the new tools, but we have multi-100s of mailboxes that we must maintain going forward for legal/compliance purposes.

@Cary Siemers That's one of the questions I have with the Exchange product group.

@Cary Siemers Microsoft has updated their note about retiring legacy eDiscovery tools and the Search-Mailbox cmdlet. Some guidance is now available for how to use PowerShell to move old Exchange Online in-place holds to holds in Office 365 eDiscovery cases. See the updated text at https://office365itpros.com/2020/01/08/posting-microsoft-365-roadmap-items-teams/ for more information.

@Tony Redmond 

Cool and thanks! I'll take a look.

@Tony Redmond 

Got to Step 5 and got "Only mailboxes are supported. The recipient name@contoso.com is of type MailContact" error and I can't proceed. 

When I look at the values in $search.SourceMailboxes they are all mailboxes and the MailContact in the error response isn't there.

 

Looks like Microsoft still need to work on this.

@Cary Siemers You expected the PowerShell to work without some massaging?

 

Try:

1. Create the policy:

$policy = New-CaseHoldPolicy -Name $search.Name -Case $case.Identity

 

2. Add the mailboxes from the old EXO search:

foreach ($mbx in $Search.SourceMailboxes) {
Set-CaseHoldPolicy -Identity $Policy.Name -AddExchangeLocation (Get-Mailbox -Identity $Mbx).PrimarySmtpAddress }

 

3. Check that all the mailboxes are present:

get-caseholdpolicy -Identity $Policy.Name | Ft ExchangeLocation

 

I also found that the code didn't deal with inactive mailboxes too well.

 

BTW, the PowerShell cmdlets to deal with Office 365 eDiscovery cases is covered in Chapter 20 of the Office 365 for IT Pros eBook.

Related Conversations