Conclusion
As always we continue to update, iterate and create amazing value for our customers. If you are interested in taking a closer look at Orchestry then please get in touch. We would love to hear from you 🙂
We are always working on new features and improvements to the Orchestry platform to make sure that our customers are getting more and more value from Orchestry. This month we want to share some new amazing features, great improvements, and a bunch of pesky bugs that we have squashed!
Orchestry now has additional capabilities for customers that are running into issues with long workspace names. As we discussed in our Microsoft Teams Naming Best Practices insight, the Teams navigation experience will truncate Team names after 34-36 characters (anything over 36 characters will further truncate the name to 34 characters to fit the ellipsis), which can make it difficult to identify a team.
This is a common governance and adoption challenge for many organizations.
In our latest update, you can now specify your desired character limit for each individual naming policy (e.g., 36 characters), and this limit will correctly check both the Workspace Name and URL to ensure it falls under the desired threshold, even accounting for any prefixes or suffixes that are dynamically added to a name.
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.
Orchestry now supports Groups as part of an Approval Workflow. Previously you could only use individual users but now you can use M365 users for an approval step.
Any person in the Group will need to approve the request in order for it to be provisioned.
In order to help guide your users better through selecting the correct Workspace, we have now added additional options, which include
To use this new feature, simply edit any existing Workspace Template, and enable the following options:
As always we continue to update, iterate and create amazing value for our customers. If you are interested in taking a closer look at Orchestry then please get in touch. We would love to hear from you 🙂