Orchestry incident
Advisory: Archival Policies with Group Configuration Options
Orchestry experienced a minor incident on January 8, 2026 affecting Lifecycle, lasting 11d 23h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Jan 08, 2026, 03:54 PM UTC
We are currently monitoring an issue affecting workspace archivals that include certain group configuration options. Archival policies may fail when either of the following options is enabled: * Remove from Global Address List (GAL) * Remove from Exchange Client This issue is caused by a recent change in Microsoft’s Microsoft Graph service and is external to Orchestry. As a result, affected archival jobs may appear to succeed but do not complete all archival actions. Impact * Some archival jobs may not complete as expected. * No data loss has occurred. Workaround As a temporary measure, we recommend disabling the above group configuration options in archival policies until Microsoft resolves the underlying issue. Our engineering team has identified the root cause and is actively monitoring Microsoft’s progress on a fix. We will provide updates as more information becomes available.
- monitoring Jan 09, 2026, 03:45 PM UTC
This problem persists. We have opened a support ticket with Microsoft and they are aware of the issue but appear to be still investigating. We will continue to monitor and add updates here as we find out more details.
- monitoring Jan 13, 2026, 06:14 PM UTC
This issue remains open. Microsoft is aware of the issue and has escalated it to their engineering team. We continue to work with their support to help investigate the issue and we will provide an update as soon as possible. In the interim, since workspace archivals may fail or complete without applying archival steps when Archival Policies include Microsoft 365 group visibility options (Remove from GAL / Remove from Exchange Client), as a workaround, temporarily disable these options and retry; no data loss has occurred.
- monitoring Jan 14, 2026, 11:45 PM UTC
Microsoft has confirmed this is a known, global issue affecting Microsoft Graph group updates and has begun deploying a fix. The fix is currently rolling out worldwide and is expected to be fully propagated within 2–3 business days; intermittent issues may continue during this period. As a workaround, disabling group visibility options (Remove from GAL / Remove from Exchange Client) remains recommended until the rollout is complete.
- resolved Jan 20, 2026, 03:44 PM UTC
On Thursday, January 15th we released a workaround in code to disable group visibility options (Remove from GAL / Remove from Exchange Client) on all calls to the Graph API. We have since tested this workaround and rolled it all to customers mitigating the impact of the issue. Microsoft continues to tell us that the issue has been patched by their Engineering team and that they have a fix being deployed, but they have given no timeline regarding when we can expect general resolution. We can confirm that the issue persists without the workaround mentioned above. Once we have confirmed that Microsoft has resolved the issue and that the group visibility options are again supported without error, we will reenable them. For the time being, we consider this incident resolved on our side.
- postmortem Jan 29, 2026, 04:04 PM UTC
## Workspace Archival Failures \(Group Visibility Options\) ### Summary A Microsoft Graph service regression caused some workspace archivals to fail when Archival Policies included group visibility options \(**Remove from GAL** / **Remove from Exchange Client**\). In some cases, archivals appeared to succeed but did not apply any archival actions. ### Impact Only customers using the affected group visibility options were impacted. **No data loss occurred**, but impacted workspaces were not archived as expected until the issue was mitigated and archivals were re-run. ### Root Cause Microsoft Graph began returning errors when updating Microsoft 365 group visibility properties required by these archival options. This behavior changed unexpectedly and was external to Orchestry. ### Mitigation & Resolution Orchestry deployed a temporary workaround on **January 15** to disable the affected group visibility updates, which mitigated the issue for customers. On **Monday**, we confirmed Microsoft had fully resolved the underlying issue and removed the workaround. The archival options are now confirmed working normally.