Site provisioning repeatedly failing for some customers at the site-header step

Resolved – Workspace Provisioning Issue

The issue affecting workspace provisioning, template application, and related operations has been resolved.

We have deployed a mitigation that bypasses workspace header and footer configuration during provisioning, allowing affected operations to complete successfully while relying on the default SharePoint header and footer configuration. We have verified that provisioning and related workflows are functioning normally following this change.

Our investigation determined that the underlying issue is related to a regression affecting Microsoft SharePoint APIs when accessed through the PnP framework. While the immediate customer impact has been resolved, we continue to work on a permanent fix that will restore full workspace header and footer configuration functionality.

We expect to deliver this enhancement as part of our normal release cadence, with the current target being our next scheduled release on June 18, 2026, pending successful validation and testing.

Thank you for your patience and understanding throughout this incident.

Monitoring – Hotfix Successfully Deployed

We have successfully deployed a hotfix and have verified that workspace provisioning, template application, and related operations are functioning as expected.

The hotfix mitigates the immediate impact of the issue by temporarily bypassing workspace header and footer configuration, which was triggering failures due to an underlying regression affecting Microsoft SharePoint APIs when accessed through the PnP framework.

We are actively monitoring the platform to confirm continued stability and successful operation of affected workflows.

Our investigation into the underlying issue remains ongoing. We are working toward a long-term solution that restores full workspace header and footer configuration functionality without requiring this temporary bypass.

We will continue to provide updates as more information becomes available.

Hotfix Deployment in Progress

We have identified the root cause of the issue impacting workspace provisioning, template application, and related operations.

Our investigation indicates that a recent regression in a Microsoft SharePoint API is causing failures when Orchestry interacts with the API through the PnP framework. This issue affects functionality that configures workspace header and footer settings during provisioning and template deployment.

To restore service as quickly as possible, we are deploying a hotfix that temporarily bypasses workspace header and footer configuration. This mitigation addresses the most critical customer impact by allowing workspace provisioning and related operations to complete successfully.

While this hotfix restores affected functionality, our team continues to investigate a long-term solution for the underlying Microsoft API regression and will provide further updates as they become available.

We appreciate your patience and understanding as we work through this issue.

**Investigating – Workspace Provisioning and Template Application Failures**

We are currently investigating an issue affecting workspace provisioning, template application, and certain installation/update operations for some customers in Orchestry.

Our investigation has identified that the issue is being caused by a recent regression in a Microsoft SharePoint API that Orchestry relies on during site provisioning and template deployment. As a result, customers may experience failures when:

* Creating new workspaces
* Creating Microsoft Teams workspaces
* Applying templates to new or existing sites
* Running Orchestry installations or updates
* Performing archive operations that create destination sites

Our team has identified a mitigation and is actively working to deploy a hotfix that bypasses the affected Microsoft API call. We are continuing to monitor the situation and will provide additional updates as more information becomes available.

We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.