Earlier this summer we released support for something called Adaptive Scopes in Microsoft Compliance Center, which essentially allows your organization to utilize the custom metadata you’ve configured in Orchestry to automate the application of compliance policies such as retention to your SharePoint Sites. But did you know there’s other benefits to this new functionality?
Earlier this summer we released support for something called Adaptive Scopes in Microsoft Compliance Center, which essentially allows your organization to utilize the custom metadata you’ve configured in Orchestry to automate the application of compliance policies such as retention to your SharePoint Sites. With this new feature, we can deploy retention policies and labels to SharePoint sites dynamically using attributes and properties to determine inclusion or exclusion from the policies. While many organizations find the application of sensitivity labels and retention labels crucial to their information management strategy, many will agree that this strategy breaks down quickly when it relies on users to manually apply policies to their workspaces.
Beyond the incredible value of being able to ensure the right policies are being applied dynamically and silently to your workspaces, Orchestry’s application of custom property bags provides significant value in other areas like Search!
What are Property Bags
If you’re wondering what a Property Bag, let us help explain! As described by the great folks over at the PnP Modern Search community project, a property bag “could be useful to store information about a SharePoint site or other element that can’t be tagged with a taxonomy value directly.” Put simply, it’s a method used in web development to apply metadata to something like a SharePoint site, and there are many ways we can then leverage these properties to help us identify sites correctly.
Adaptive Scopes are a new piece of functionality within Microsoft Compliance that can help you more easily manage targeting data within your changing environment. Rather than static scopes, Adaptive Scopes will dynamically read attributes and properties for objects to determine whether compliance policies should be applied. In some ways, this is similar to the idea of a Dynamic Security Group in Azure AD, vs a static group.
Orchestry now supports writing the Workspace Template ID as well as any applied metadata into property bags stored on the attached SharePoint Site. These properties are also automatically enabled for indexing, meaning they automatically get crawled by search and can then be easily mapped to Managed Properties in the Search Schema. This not only facilitates the use of KQL queries in the Compliance Center to create Adaptive Scopes, it also means that these properties can be used in custom search-based solutions.
The Orchestry Directory already provides a rich and flexible search experience for filtering and searching through your entire catalogue of workspaces, including any custom metadata such as Location, Department Owner, Customer, and anything else that may be valuable to classify your workspaces.
There are times when there are benefits to building your own search experience within SharePoint. Because the property bags are set to be indexed by Microsoft Search, we can use these metadata values as a means to create powerful search and refinement-based experiences, such as the example below.
While the provisioning of custom property bags is indeed a powerful feature, it is merely the tip of the iceberg when it comes to the host of features built-in to the Orchestry platform when it comes to designing and provisioning feature-rich workspaces at the click of a button. These templates can be both intuitive to end users, but flexible and powerful enough to accommodate some of the most advanced scenarios in the industry.
If you’re interested in finding out how Orchestry can help your organization? Reach out to us today using the Get My Demo button and find out.