Is Orchestry down?

We're aware that some people are experiencing failures when deploying SPFx packages to the SharePoint tenant app catalog using app-only (certificate/application) authentication. Affected requests return the following error, even when the app registration has Sites.FullControl.All granted with admin consent: "Must have Manage Web Site permissions in order to add apps to site collection app catalog" This issue is currently preventing automatic updates to the web part package for Orchestry users. We have reported this to Microsoft and are tracking it closely. This appears to be a Microsoft-side issue, not something within Orchestry's control. It has been reported to Microsoft and is being tracked publicly: PnP PowerShell GitHub issue #5406 [https://github.com/pnp/powershell/issues/5406] SharePoint dev docs GitHub issue #10955 — confirmed as a bug by Microsoft [https://github.com/SharePoint/sp-dev-docs/issues/10955] We are monitoring both threads closely and will post updates here as we learn more. If you're impacted, please reach out to our Customer Success team at support.orchestry.com for a manual workaround.

Microsoft has confirmed that a mitigation has been put in place to resolve the issue affecting SPFx package uploads to the SharePoint tenant app catalog via app-only (certificate/application) authentication. Multiple customers have confirmed the fix in Microsoft's public tracking thread, and our own internal testing confirms the issue no longer reproduces. If you were previously impacted and continue to see this error, please reach out to our Customer Success team at support.orchestry.com. Thanks for your patience while we tracked this down alongside Microsoft.

**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.

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.

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.

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.

**Resolved – Workspace Provisioning Issue** The issue affecting workspace provisioning, template application, and related operations has been fully resolved. Our investigation determined that the underlying issue was caused by a regression affecting Microsoft SharePoint APIs when accessed through the PnP framework. This regression caused header and footer configuration operations to fail during provisioning, resulting in unsuccessful workspace creation and template deployment. As an immediate mitigation, we previously deployed a hotfix that bypassed workspace header and footer configuration, allowing provisioning and related operations to complete successfully while relying on default SharePoint settings. We have now released a permanent fix that restores workspace header and footer configuration while avoiding the affected Microsoft API behavior. The solution leverages an alternative implementation path that preserves provisioning reliability while ensuring workspace branding and navigation settings are applied correctly. We have verified the fix across affected provisioning scenarios, and all impacted functionality is operating normally.