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

Orchestry Updates for June 2025 | Part 1

These improvements were deployed on June 5, 2025

New Feature: Guest Request Auto-Approval

Guest Request Auto-Approval introduces a centralized Safe List of domains to Orchestry’s guest governance engine, allowing organizations to bypass redundant guest approval workflows for fully trusted partner domains.

Administrators can maintain full approval controls for unknown guests while streamlining onboarding for pre-vetted collaborators.

In Guest Management Settings, you can define a list of approved domains (for example: "partner.com"). Any guest request from one of these domains will be approved automatically, even if manual approval is normally required.

Why We Built It

1. Guest Friction Slows Collaboration: Sometimes speed is essential, getting external collaborators into the system immediately can be valuable.

2. Microsoft Has Limited Controls: Orchestry's robust Guest Request automation continues to offer many advantages over the native Microsoft solutions.

3. Eliminate Needless Manual Approvals: Frequent guest domains repeatedly pass vetting — approvals become redundant.

4. Maintain Security with Targeted Relaxation: Only trusted domains bypass approvals while all other requests follow full Orchestry policies.

KB-GM-GuestSettings2

This feature is especially useful for organizations that:

  • Work regularly with specific external vendors or partners
  • Want to simplify the guest onboarding process
  • Need to maintain efficiency while keeping control
  • Want continued oversight for any new domains, but less stringency for established partners

Want to learn how to add domains to your safe list?  Check out the article: Guest Settings available in Orchestry

Bug Fixes

User Sync on Communication Sites

Fixed an issue where Orchestry couldn’t load users for some SharePoint Communication Sites. This affected rare site setups and has now been resolved.

Metadata Validation in API Requests

Fixed an issue where some provisioning requests made through the API were incorrectly blocked, even though they worked fine in the UI. Validation now behaves consistently across both.