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

Processing and Data Availability

Learn about the different types of processing and data availability Orchestry provides.

    Platform Features

    Workspace Provisioning

    Provisioning requests are queued against the Orchestry engine (API) in your respective Azure Region (e.g., North America). Our engine limits each tenant to three (3) sequential provisioning jobs at any given time, with a queue dynamically handling overflow to ensure Microsoft Graph throttling is avoided. The processing of individual provisioning jobs depends heavily on the complexity of the template being provisioned. 

    Workspace Directory  

    Any objects provisioned via Orchestry will automatically update the Workspace Directory in real-time. Items that have an Orchestry archival policy executed as part of the daily ETL (see below) will ensure the Directory is updated in tandem. Objects provisioned, archived or deleted via a native experience (e.g., Teams, SharePoint, etc.) get crawled as part of the daily ETL and are added to the Directory after the fact.  

     

    EXCEPTIONS: An exception to the delay associated with the daily ETL to pick up any non-Orchestry changes (changes via native M365 experience) occurs when an ad Hoc Import is forced using the ‘Import and Update’ button under Directory Configuration.

    This process can take quite a bit of time depending on the amount of sites and teams in your tenant. This is typically only triggered once, during installation.  

    Workspace Dashboard and Insights 

    Updated data for the Workspace Dashboard and associated Insights is collected, processed and updated as part of the daily ETL process and therefore should not be communicated as real time.

    Archival Policy Execution

    Archival policies associated with a workspace and set to trigger are executed as part of the daily ETL processing, after the dashboard data has been updated (see below for sequence).  

     

    EXCEPTIONS: Archival Policies can be executed in near real time (up to 5 minutes) when the policy is ‘forced’ to fire using the Force Archive function.

    Underlying Processes

    API

    Requests made directly to the Orchestry API follow the same general rules included above for provisioning and archiving. In addition, calls to the API are limited to protect Orchestry infrastructure.

    Daily ETL

    Our Extract, Transform and Load (ETL) process runs daily to collect new data, identify delta in existing data and execute policies. The ETL is programmed to execute activities in the following sequence:  

    1. Lifecycle Data Updated

    2. Directory Updated

    3. Execute Archival Policies

    When Archival policies archive or delete a workspace, the ELT will automatically clean up that particular workspace from the Directory using the following logic:  

    • Archive in Place: Retained in the Directory but Visibility = False
    • Copy and Delete / Delete: Removed from the Directory