Skip to content
English
  • There are no suggestions because the search field is empty.

Orchestry Updates for February 2024

These features were deployed on March 1st, 2024

This update does not require your intervention and does not involve any downtime.

New Features

New Crawling Engine

After massive efforts from the engineering team, an entirely new and improved crawling engine has been released to all customers. This greatly expands the breadth of data being captured - necessitating a new SQL Database - and underpins a whole series of new features and functionalities planned for the coming year. Stay tuned for some great things

Improvements

  • Updated logic for the Team Information Tab and the Workspace Details pages to use consistent logic in displaying whether or not Guests are enabled in the workspace. Going forward, the Team Information Tab will display "Guests Enabled" or "Guests Disabled". In the Admin-only Workspace Details experience, the label will be more descriptive and include either:
    • Guests Enabled
    • Guests Enabled via Orchestry (when using a Guest Request policy)
    • Guests Disabled

1YioaykWW1euzbugi_pbU_315YHTk3xuQA

  • Moved the addition of Group Members closer to the end of the Provisioning job to ensure they are added as late as possible and are less likely to receive notifications about the group before it is completely provisioned.
  • Added size of workspace to logging output for Archival jobs

    khzg_OKM5R4-w6QrjGZ3oPMot5j3cSQMzg

 

  • Fixed an issue where the Guest Inactivity calculation had become out of sync with the Last Login Date.
  • Fixed an issue where the SharePoint Site and associated Group was not being renamed correctly during an Archival policy.
  • Fixed an issue where Communication Sites are being incorrectly identified as Microsoft Teams
  • Added a check for PIM-based elevation, allowing users to refresh their credentials from Microsoft365 and perform GA-only actions like an Orchestry update.
  • Fixed an issue where the New Teams experience could sometimes cause workspace links from the Directory Tab to not correctly connect to the correct Team and Channel.
  • Fixed an issue where the webhook added to the Second Step of an Archival policy was overriding the webhook saved to the First Step.
  • Fixed issue where Localizations would occasionally not render in the Request Screen when using the Web App.
  • Added a number of missing localizations found within end-user facing experiences.

What's Coming Soon?

Stay tuned for the release of the new Recommendations Engine (see Orchestry Announces New  Recommendations Feature) next week, brand new Orchestry Web Parts and Workspace Directory improvements all targeted for March!