Adaptive scopes in now in preview and will be soon released to general availability.

With adaptive scopes you can define a attribute based filtering for content. Really nice addition to filtering locations easily.

How to create Adaptive scopes?

Go to Information governance and choose Adaptive scopes then create scope

Choose what kind of scope you want, in my example I choose Groups.

Define a query for the group with and and or definitions.

And you can also create advanced query with OPATH filters.

What are OPATH filters?

When creating your own custom OPath filters, consider the following items:

• Use the following syntax to identify the types of values that you’re searching for:
  • Text values: Enclose the text in single quotation marks (for example, 'Value' or 'Value with spaces'). Or, you can enclose a text value in double quotation marks, but that limits the characters you can use to enclose the whole OPath filter.
  • Variables: Enclose variables that need to be expanded in single quotation marks (for example, '$User'). If the variable value itself contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of '$User', use '$($User -Replace "'","''")'.
  • Integer values: You don’t need to enclose integers (for example, 500). You can often enclose integers in single quotation marks or double quotation marks, but that limits the characters you can use to enclose the whole OPath filter.
  • System values: Don’t enclose system values (for example, $true, $false, or $null). To enclose the whole OPath filter in double quotation marks, you need to escape the dollar sign in system value (for example, $true).

You need to enclose the whole OPath filter in double quotation marks " or " single quotation marks ' '. Although any OPath filter object is technically a string and not a script block, you can still use braces { }, but only if the filter doesn't contain variables that require expansion. The characters that you can use to enclose the whole OPath filter depend on types of values that you're searching for and the characters you used (or didn't use) to enclose those values:

• Text values: Depends on how you enclosed the text to search for:
  • Text enclosed in single quotation marks: Enclose the whole OPath filter in double quotation marks or braces.
  • Text enclosed in double quotation marks: Enclose the whole OPath filter in braces.
• Variables: Enclose the whole OPath filter in double quotation marks (for example, "Name -eq '$User'").
• Integer values: Depends on how you enclosed (or didn't enclose) the integer to search for:
  • Integer not enclosed: Enclose the whole OPath filter in double quotation marks, single quotation marks, or braces (for example "CountryCode -eq 840").
  • Integer enclosed in single quotation marks: Enclose the whole OPath filter in double quotation marks or braces "CountryCode -eq '840'".
  • Integer enclosed in double quotation marks: Enclose the whole OPath filter in braces (for example {CountryCode -eq "840"}).
• System values: Enclose the whole OPath filter in single quotation marks or braces (for example 'HiddenFromAddressListsEnabled -eq $true'). If you escape the dollar sign system value, you can also enclose the whole OPath filter in double quotation marks (for example, "HiddenFromAddressListsEnabled -eq $true").

• nclude the hyphen before all logical or comparison operators. The most common operators include:
  • -and
  • -or
  • -not
  • -eq (equals)
  • -ne (not equal)
  • -lt (less than)
  • -gt (greater than)
  • -like (string comparison)
  • -notlike (string comparison)
• Many filterable properties accept wildcard characters. If you use a wildcard character, use the -like operator instead of the -eq operator. Use the -like operator to find pattern matches in rich types (for example, strings). Use the -eq operator to find an exact match.When you use the -like operator in Exchange Online PowerShell, the wildcard character is supported only as a suffix. For example, "Department -like 'sales*'" is allowed; "Department -like '*sales'" is not allowed.

Choosing retention label

Go to labels and choose you label to publish.

Choose Adaptive

Add a scope and choose the scope you created in previous steps.

And it will filter out location that the scope doesn’t apply to.

Review your settings and done.

Note that it will take up to 1 day for labels to appear to your users. Labels will appear in Outlook and Outlook web app only for mailboxes that have at least 10 MB of data.

Policy lookup

Then we also get Policy look that is also in preview. Nice feature to look for policies applied to a user, a site or to a group.

Over and out,