Set up compliance boundaries for eDiscovery investigations in Office 365
Compliance boundaries create logical boundaries within an Office 365 organization that control the user content locations (such as mailboxes, SharePoint sites, and OneDrive accounts) that eDiscovery managers can search. Also, compliance boundaries control who can access eDiscovery cases used to manage the legal, human resources, or other investigations within your organization. The need for compliance boundaries is often necessary for multi-national corporations that have to respect geographical boarders and regulations and for governments, which are often divided into different agencies. In Office 365, compliance boundaries help you meet these requirements when performing content searches and managing investigations with eDiscovery cases.
We use the example in the following illustration to explain how compliance boundaries work.
In this example, Contoso LTD is an Office 365 organization that consists of two subsidiaries, Fourth Coffee and Coho Winery. The business requires that eDiscovery mangers and investigators can only search the Exchange mailboxes, OneDrive accounts, and SharePoint sites in their agency. Also, eDiscovery managers and investigators can only see eDiscovery cases in their agency, and they can only access the cases that they're a member of. Here's how compliance boundaries meet these requirements.
The search permissions filtering functionality in Content Search controls the content locations that eDiscovery managers and investigators can search. This means eDiscovery managers and investigators in the Fourth Coffee agency can only search content locations in the Fourth Coffee subsidiary. The same restriction applies to the Coho Winery subsidiary.
Role groups control who can see the eDiscovery cases in the Security & Compliance Center. This means that eDiscovery managers and investigators can only see the eDiscovery cases in their agency.
Role groups also control who can assign members to an eDiscovery case. This means eDiscovery managers and investigators can only assign members to cases that they themselves are a member of.
Here's the process for setting up compliance boundaries:
Step 1: Identify a user attribute to define your agencies
The first step is to choose an Azure Active Directory attribute to use that will define your agencies. This attribute will be used to create the search permissions filter that limits an eDiscovery manager to search only the content locations of users who are assigned a specific value for this attribute. For example, let's say Contoso decides to use the Department attribute. The value for this attribute for users in the Fourth Coffee subsidiary would be
FourthCoffee and the value for users in Coho Winery subsidiary would be
CohoWinery. In Step 4, you use this
attribute:value pair (for example, Department:FourthCoffee) to limit the user content locations that eDiscovery managers can search.
Here's a list of Azure Active Directory user attributes that you can use for compliance boundaries:
CustomAttribute1 — CustomAttribute15
C (Two letter Country Code)
Although more user attributes are available, particularly for Exchange mailboxes, the attributes listed above are the only ones currently supported by OneDrive.
Step 2: File a request with Microsoft Support to synchronize the user attribute to OneDrive accounts
The next step is to file a request with Microsoft Support to synchronize the Azure Active Directory attribute that you chose in Step 1 to all OneDrive accounts in your organization. After this synchronization occurs, the attribute (and its value) that you chose in Step 1 will be mapped to a hidden managed property in SharePoint named
ComplianceAttribute. You use this attribute to create the search permissions filter for OneDrive in Step 4.
Include the following information when you submit the request to Microsoft support:
The default domain name of your Office 365 organization
The name of the Azure Active Directory attribute (from Step 1)
The following title or description of the purpose of the support request: "Enable OneDrive for Business Synchronization with Azure Active Directory for Compliance Security Filters". This helps route the request to the Office 365 eDiscovery engineering team who will implement the request.
After the engineering change is made and the attribute is synchronized to OneDrive, Microsoft Support will send you the build number that the change was made in and an estimated deployment date. The deployment process usually takes 4–6 weeks after you submit the support request.
Important: You can complete Step 3 through Step 5 before the change is deployed. But running content searches won't return documents from OneDrive sites specified in the search permissions filter until after the change is deployed.
Step 3: Create a role group for each agency
The next step is to create the role groups in the Security & Compliance Center that will align with your agencies. We recommend that you create a role group by copying the built-in eDiscovery Managers group, adding the appropriate members, and removing roles that may not be applicable to your needs. For more information about eDiscovery-related roles, see Assign eDiscovery permissions in the Office 365 Security & Compliance Center.
To create the role groups, go to the Permissions page in the Security & Compliance Center and create a role group for each team in each agency that will use compliance boundaries and eDiscovery cases to manage investigations.
Using the Contoso compliance boundaries scenario, four role groups need to be created and the appropriate members added to each one.
Fourth Coffee eDiscovery Managers
Fourth Coffee Investigators
Coho Winery eDiscovery Managers
Coho Winery Investigators
Step 4: Create a search permissions filter to enforce the compliance boundary
After you've created role groups for each agency, the next step is to create the search permissions filters that associate each role group to its specific agency and defines the compliance boundary itself. You need to create one search permissions filter for each agency. For more information about creating security permissions filters, see Configure permissions filtering for Content Search.
Here's the syntax that's used to create a search permissions filter used for compliance boundaries.
New-ComplianceSecurityFilter -FilterName <name of filter> -Users <role groups> -Filters "Mailbox_<ComplianceAttribute> -eq '<AttributeVale> '", "Site_<ComplianceAttribute> -eq '<AttributeValue>' -or Site_Path -like '<SharePointURL>*'" -Action <Action >
Here's a description of each parameter in the command:
FilterName: Specifies the name of the filter. Use a name that describes or identifies the agency that the filter is used in.
Users: Specifies the users or groups who get this filter applied to the Content Search actions they perform. For compliance boundaries, this parameter specifies the role groups (that you created in Step 3) in the agency that you're creating the filter for. Note this is a multi-value parameter so you can include one or more role groups, separated by commas.
Filters: Specifies the search criteria for the filter. For the compliance boundaries, you define the following filters. Each one applies to a content location.
Mailbox: Specifies the mailboxes that the role groups defined in the
Usersparameter can search. For compliance boundaries, ComplianceAttribute is the same attribute that you identified in Step 1 and AttributeValue specifies the agency. This filter allows members of the role group to search only the mailboxes in a specific agency; for example,
"Mailbox_Department -eq 'FourthCoffee'".
Site: Specifies the OneDrive accounts that the role groups defined in the
Usersparameter can search. For the OneDrive filter, use the actual string
ComplianceAttribute. This maps to the same attribute that you identified in Step 1 and that's synchronized to OneDrive accounts as a result of the support request that you submitted in Step 2; AttributeValue specifies the agency. This filter allows members of the role group to search only the OneDrive accounts in a specific agency; for example,
"Site_ComplianceAttribute -eq 'FourthCoffee'".
Site_Path: Specifies the SharePoint sites that the role groups defined in the
Usersparameter can search. The SharePointURL specifies the sites in the agency that members of the role group can search; for example,
"Site_Path -like 'https://contoso.sharepoint.com/sites/FourthCoffee*'"Notice the
Site_Pathfilters are connected by an -or operator.
The syntax for the
Filtersparameter includes a filters list. A filters list is a filter that includes a mailbox filter and a site filter separated by a comma. In the previous example, notice that a comma separates Mailbox_ComplianceAttribute and Site_ComplianceAttribute:
-Filters "Mailbox_<ComplianceAttribute> -eq '<AttributeVale> '", "Site_ComplianceAttribute -eq '<AttributeValue>' -or Site_Path -like '<SharePointURL>*'". When this filter is processed during the running of a content search, two search permissions filters are created from the filters list: one mailbox filter and one site filter. An alternative to using a filters list would be to create two separate search permissions filters for each agency: one search permissions filter for the mailbox attribute and one filter for the site attributes. In either case, the results will be the same. Using a filters list or creating separate search permissions filters is a matter of preference.
Action: Specifies the type of Compliance Search action that the filter is applied to. For example,
-Action Searchwould only apply the filter when members of the role group defined in the
Usersparameter run a content search. In this case, the filter wouldn't be applied when exporting search results. For compliance boundaries, use
-Action Allso the filter applies to all search actions.
For a list of the Content Search actions, see the "New-ComplianceSecurityFilter" section in Configure permissions filtering for Content Search.
Here are examples of the two search permissions filters that would be created to support the Contoso compliance boundaries scenario. Both of these examples include a comma-separated filters list, in which the mailbox and site filters are included in the same search permissions filter and are separated by a comma.
New-ComplianceSecurityFilter -FilterName "Fourth Coffee Security Filter" -Users "Fourth Coffee eDiscovery Managers", "Fourth Coffee Investigators" -Filters "Mailbox_Department -eq 'FourthCoffee'", "Site_ComplianceAttribute -eq 'FourthCoffee' -or Site_Path -like 'https://contoso.sharepoint.com/sites/FourthCoffee*'" -Action ALL
New-ComplianceSecurityFilter -FilterName "Coho Winery Security Filter" -Users "Coho Winery eDiscovery Managers", "Coho Winery Investigators" -Filters "Mailbox_Department -eq 'CohoWinery'", "Site_ComplianceAttribute -eq 'CohoWinery' -or Site_Path -like 'https://contoso.sharepoint.com/sites/CohoWinery*'" -Action ALL
Step 5: Create an eDiscovery case for intra-agency investigations
The final step is to create a eDiscovery case in the Security & Compliance Center and then add the role group that you created in Step 3 as a member of the case. This results in two important characteristics of using compliance boundaries:
Only members of the role group added to the case will be able to see and access the case in the Security & Compliance Center. For example, if the Fourth Coffee Investigators role group is the only member of a case, then members of the Fourth Coffee eDiscovery Managers role group (or members of any other role group) won't be able to see or access the case.
When a member of the role group assigned to a case runs a search associated with the case, they will only be able to search the content locations within their agency (which is defined by the search permissions filter that you created in Step 4.)
To create a case and assign members:
Go to the eDiscovery page in the Security & Compliance Center and create a case.
In the list of eDiscovery cases, click the name of the case you created.
In the Manage this case flyout page, under Manage role groups, click Add.
In the list of role groups, select one of the role groups that you created in Step 3, and click Add.
Click Save on the Manage this case flyout to save the change.
Compliance boundary limitations
Keep the following limitations in mind when managing eDiscovery cases and investigations that use of compliance boundaries.
When creating and running a Content Search, you can select content locations that are outside of your agency. However, because of the search permissions filter, content from those locations won't be included in the search results.
Compliance boundaries don't apply to holds in eDiscovery cases. That means an eDiscovery manager in one agency can place a user in a different agency on hold. However, the compliance boundary will be enforced if the eDiscovery manager searches the content locations of the user who was placed on hold. That means the eDiscovery manager won't be able search the user's content locations, even though they were able to place the user on hold.
Also, hold statistics will only apply to content locations in the agency.
Search permissions filters aren't applied to Exchange public folders.
Searching and exporting content in Multi-Geo environments
Search permissions filters also let you control where content is routed for export and which datacenter can be searched when searching content locations in a SharePoint Multi-Geo environment.
Export search results: You can export the search results from Exchange mailboxes, SharePoint sites, and OneDrive accounts from a specific datacenter. This means that you can specify the datacenter location that search results will be exported from.
Use the Region parameter for New-ComplianceSecurityFilter or Set-ComplianceSecurityFilter cmdlets to create or change which datacenter the export will be routed through.
Parameter value Datacenter location NAM North American (datacenters are in the US) EUR Europe APC Asia Pacific CAN Canada
Route content searches: You can route the content searches of SharePoint sites and OneDrive accounts to a satellite data center. This means you can specify the datacenter location where searches will be run.
Use the following values for the Region parameter values to control which datacenter that Content Searches will run in when searching SharePoint sites and OneDrive locations.
Parameter value Datacenter routing locations for SharePoint NAM US EUR Europe APC Asia Pacific CAN US AUS Asia Pacific KOR The organization's default datacenter GBR Europe JPN Asia Pacific IND Asia Pacific LAM US
If you don't specify the Region parameter for a search permissions filter, the organization's default SharePoint region will be searched, then search results are exported to the closest datacenter.
To simplify the concept, the Region parameter controls the datacenter that is used to search for content in SharePoint and OneDrive. This doesn't apply to searching for content in Exchange because Exchange content searches aren't bound by the geographic location of datacenters. Also, the same Region parameter value may also dictate the datacenter that exports are routed through. This is often necessary to control the movement of data across geographic boarders.
If you're using Advanced eDiscovery, searching for content in SharePoint and OneDrive isn't bound by the geographic location of datacenters. For more information about Advanced eDiscovery, see Overview of the Advanced eDiscovery solution in Microsoft 365.
Here are examples of using the Region parameter when creating search permission filters for compliance boundaries. This assumes that the Fourth Coffee subsidiary is located in North America and that Coho Winery is in Europe.
New-ComplianceSecurityFilter -FilterName "Fourth Coffee Security Filter" -Users "Fourth Coffee eDiscovery Managers", "Fourth Coffee Investigators" -Filters "Mailbox_Department -eq 'FourthCoffee'", "Site_Department -eq 'FourthCoffee' -or Site_Path -like 'https://contoso.sharepoint.com/sites/FourthCoffee*'" -Action ALL -Region NAM
New-ComplianceSecurityFilter -FilterName "Coho Winery Security Filter" -Users "Coho Winery eDiscovery Managers", "Coho Winery Investigators" -Filters "Mailbox_Department -eq 'CohoWinery'", "Site_Department -eq 'CohoWinery' -or Site_Path -like 'https://contoso.sharepoint.com/sites/CohoWinery*'" -Action ALL -Region EUR
Keep the following things in mind when searching and exporting content in multi-geo environments.
The Region parameter doesn't control searches of Exchange mailboxes. All data centers will be searched when you search mailboxes. To limit the scope of which Exchange mailboxes can be searched, use the Filters parameter when creating or changing a search permissions filter.
If it's necessary for an eDiscovery Manager to search across multiple SharePoint regions, you need to create a different user account for that eDiscovery manager that can be used in the search permissions filter to specify the alternate region where the SharePoint sites or OneDrive accounts are located.
When searching for content in SharePoint and OneDrive, the Region parameter directs searches to either the main or satellite location where the eDiscovery manager will conduct eDiscovery investigations. If an eDiscovery manager searches SharePoint and OneDrive sites outside of the region that's specified in the search permissions filter, no search results will be returned.
When exporting search results, content from all content locations (including Exchange, Skype for Business, SharePoint, OneDrive, and other Office 365 services that you can search by using the Content Search tool) will be uploaded to the Azure Storage location in the datacenter that's specified by the Region parameter. This helps organizations stay within compliance by not allowing content to be exported across controlled borders. If no region is specified in the search permissions filter, content is uploaded to the organization's default region.
You can edit an existing search permissions filter to add or change the region by running the following command:
Set-ComplianceSecurityFilter -FilterName <Filter name> -Region <Region>
Frequently asked questions
Who can create and manage search permissions filters (using New-ComplianceSecurityFilter and Set-ComplianceSecurityFilter cmdlets)?
To create, view, and modify search permissions filters, you have to be a member of the Organization Management role group in the Security & Compliance Center.
If an eDiscovery manager is assigned to more than one role group that spans multiple agencies, how do they search for content in one agency or the other?
The eDiscovery manager can add parameters to their search query that will restrict the search to a specific agency. For example, if an organization has specified the CustomAttribute10 property to differentiate agencies, they can append the following to their search query to search mailboxes and OneDrive accounts in a specific agency:
CustomAttribute10:<value> AND Site_ComplianceAttribute:<value>.
What happens if the value of the attribute that's used as the compliance attribute in a search permissions filter is changed?
It takes up to three days for a search permissions filter to enforce the compliance boundary if the value of the attribute that's used in the filter is changed. For example, in the Contoso scenario let's say that a user in the Fourth Coffee agency is transferred to the Coho Winery agency. As a result, the value of the Department attribute on the user object is changed from FourthCoffee to CohoWinery. In this situation, Fourth Coffee eDiscovery and investors will get search results for that user for up three days after the attribute is changed. Similarly, it takes up to three days before Coho Winery eDiscovery managers and investigators get search results for the user.
Can an eDiscovery manager see content from two separate compliance boundaries?
Yes. This can be done by adding the user to role groups that have visibility to both agencies.
Do search permissions filters work for eDiscovery case holds, Office 365 retention policies, or DLP?
No, not at this time.
If I specify a region to control where content is exported, but I don't have a SharePoint organization in that region, can I still search SharePoint?
If the region specified in the search permissions filter doesn't exist in your organization, the default region will be searched.
What is the maximum number of search permissions filters that can be created in an organization?
There is no limit to the number of search permissions filters that can be created in an organization. However, search performance will be impacted when there are more than 100 search permissions filters. To keep the number of search permissions filters in your organization as small as possible, create filters that combine rules for Exchange, SharePoint, and OneDrive into a single search permissions filter whenever possible.