User Profile
tgraham-legalops
Brass Contributor
Joined Jan 13, 2022
User Widgets
Recent Discussions
Cannot update Case number in Microsoft Purview eDiscovery
I can no longer update the Case number under case settings in the new eDiscovery UI. I used to be able to update it via the externalId Graph endpoint but that appears to be deprecated. The error simply reads "update failed" - there is no additional information. Is anyone else having this problem?Solved224Views0likes2CommentsRe: Legal Hold Communication Acknowledgment links broken by Welcome pop-up
Nevermind, I figured out how to bypass the annoying Welcome pop-up. To create acknowledgment links that bypass the Welcome pop-up: Click the Acknowledgment Link button Select the link text and click the Remove hyperlink button Select the link text again, click the Insert Hyperlink button, paste https://compliance.microsoft.com/{{AckLink}} and click OK Now, when you send legal hold communications, your acknowledgment links will bypass the welcome message and display "acknowledgment recorded" message, causing less confusion to the users. ALSO, if you want to send links to review sets and other tabs in the eDiscovery Premium UI that bypass the Welcome pop-up, you can do so by changing the path and appending the &autoRedirect=false parameter to the URL. For example, this URL will take you to the new UI (still in Preview mode) and display the Welcome pop-up: https://purview.microsoft.com/ediscovery/advancedediscovery/cases/v2/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx?tid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx&casename=____________&casesworkbench=Overview Whereas this URL will take you to old UI and bypass the Welcome pop-up: https://compliance.microsoft.com/advancedediscovery/cases/v2/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx?tid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx&casename=____________&casesworkbench=Overview&autoRedirect=false Just change "https://purview.microsoft.com/ediscovery/advancedediscovery" to "https://compliance.microsoft.com/advancedediscovery" and append "&autoRedirect=false" to the end of the URL and you'll bypass the new UI and the Welcome pop-up.11Views0likes1CommentLegal Hold Communication Acknowledgment links broken by Welcome pop-up
https://learn.microsoft.com/en-us/purview/ediscovery-acknowledge-hold-notification generated by Microsoft in a legal hold communication typically takes users to a Purview page with the message "Thank you! Your acknowledgment has been recorded." But now, the ever-present "Welcome to the new Microsoft Purview portal!" pop-up displays, regardless of the user's permissions, and there's no way to close it or bypass it to reach that "Thank you" page. The "Thank you" page loads in the background, but it's partially obscured by the "Welcome" message. Can we please do something to either get rid of this welcome message or disassociate it from these legal hold acknowledgment links?Solved341Views0likes2CommentsGraph Security Legal hold Communication endpoint
Why is there no legal hold communication endpoint for the https://learn.microsoft.com/en-us/graph/api/resources/security-ediscoverycase?view=graph-rest-1.0? We need to be able to list, create and update legal hold communications for various eDiscovery cases with Graph.106Views0likes0CommentsRe: DLP rule - Document Property is: 'ComplianceTag:\0'
It's sending incident reports to an administrator. So far, nothing received, so it's not working. Other DLP policies which include a policy tip are working as expected but the conditions for those policies are not trying to match the "document property is" condition with a null value. So, I think the problem is either 1) I have the wrong syntax for matching null values or 2) null values are not supported.1.4KViews0likes0CommentsDLP rule - Document Property is: 'ComplianceTag:\0'
Is an expression like the one below supported by the "Document Property Is" condition when setting a DLP Policy in Purview? I'm trying to set a rule that applies a DLP alert to files in SharePoint that do not have a retention label applied to them. Would using the null character regex work for this? Document Property is: 'ComplianceTag:\0' Alternatively, is it possible to set a rule when a document property does NOT contain something?Re: Name & alias mismatch in eDiscovery Premium
Ok, this has come up again. And again the results are limited to calendar invites, specifically exchange items where "message kind" = "meetings". The other commonality with the previous instance of this email alias/display name mismatch problem is that the one of the custodians in question shared their calendar with the other custodian at some point (I found proof of this through a content search on emails in their accounts that were sent to each other with the subject = "You're invited to share this calendar"). I think what's happening is when Ren Hoek <rhoek@companydotcom> shares his calendar with "view all items" permissions with Stimpy J. Cat <sjcat@companydotcom>, copies of all calendar items created by Ren appear in Stimpy's Exchange calendar folder as if Stimpy created them. In eDiscovery these are the items that appear as if the sender is this: "Stimpy J. Cat <rhoek@companydotcom>." I think that's what's happening. Can someone from Microsoft please confirm?641Views0likes0CommentsRe: Examples of "subject matches patterns" regular expression when auto-applying sensitivity label
miller34mike Thank you! Have you had any luck using the "Header matches patterns" condition? No matter what I try, I can't get that one to work. Any tips would be greatly appreciated.1.5KViews0likes1CommentExamples of "subject matches patterns" regular expression when auto-applying sensitivity label
Hello, I'm trying to auto-apply a sensitivity label to Exchange content (a specific user mailbox) where the rule is defined by a "subject matches patterns" condition. Microsoft requires a regular expression here. The emails I'm trying to apply the label to all have the words "Litigation Hold" in the subject line. I've tried to capture these using the following regular expressions but none have worked: (?:Litigation Hold), \bLitigation Hold\b, \sLitigation Hold\s, ^(?:Litigation Hold)$, Litigation Hold. What syntax is Microsoft looking for here? Any help or examples would be appreciated, thank you.SolvedIs there a method to select recipients and send a new communication in an eDiscovery case?
The clunky UI makes it difficult to select recipients for a legal hold communication when working with large custodian lists; while you can search on name or email, you can't sort by name or email. Also, I've noticed that some communications fail to send if more than 100 custodians are selected for a single communication. So I have to break it up into separate communications, making it hard to track which ones have been selected and which haven't. This brings me to Graph, which could potentially enable imports of data from a list or csv, but I don't see a method for accessing and writing to the Legal Hold Communication feature in Purview in the documentation. Does such a method exist? If not, is it on the roadmap?458Views0likes0CommentsAdd "communication summary" column to eDiscovery (Premium) cases page
When viewing all cases, it would be great to see the communication summary displayed as an additional column. As eDiscovery administrator I just want to see the number of notices sent and the number acknowledged displayed for each case without having to click into each one. Just a simple "4/7" to show 4 acknowledged out of 7 sent would be great to see alongside the case number, case name, description columns, etc.274Views0likes0CommentsPossible to change test on Purview comm acknowledgment page?
We'd like to change the text on the page that users see when they acknowledge a communication sent via the Purview eDiscovery communication tool. Is it possible to change? Right now it says "eDiscovery (Premium)" and "Thank you!". Is it possible to change the wording here? Or maybe redirect the users to a different acknowledgment page while still recording the acknowledgment?
Recent Blog Articles
No content to show