The new SharePoint webpart version (1.1.2.0) is now available and resolves the issue.
The webpart has been refactored to use the SPFx "externals" pattern, which automatically registers admin.aidesk-pro.com in the tenant's Trusted Script Sources at .sppkg install time. This satisfies SharePoint Online's Content Security Policy, which Microsoft started enforcing on March 1, 2026, and restores webchat loading on SharePoint pages.
Action required from SharePoint administrators: - Download the latest aideskpro-webchat.sppkg from your AI Desk PRO admin portal : https://admin.aidesk-pro.com/webchat/aideskpro-webchat.sppkg. - Upload it to your SharePoint App Catalog (overwriting the previous version). - No per-tenant CSP allowlist change is required — installation registers the domain automatically.
The webchat continues to operate normally on web and other channels; only the SharePoint webpart was affected.
Root cause identified. Microsoft started enforcing Content Security Policy (CSP) on SharePoint Online pages from March 1, 2026, which blocks by default the loading of scripts from non-Microsoft domains. Our SharePoint webpart uses a dynamic script loading mechanism that does not auto-register the admin.aidesk-pro.com domain in the tenant's "Trusted Script Sources" — which is what causes the blocking we observed.
Next steps: - We are refactoring the webpart to use the SPFx "externals" pattern, which automatically registers the domain in Trusted Script Sources at install time. A new version of the .sppkg package will be released shortly.
We will update this incident as soon as the new webpart version is published.
Posted Apr 28, 2026 - 14:51 CEST
Update
We are continuing to investigate this issue.
Posted Apr 28, 2026 - 10:18 CEST
Investigating
We are currently experiencing an issue where the webchat is no longer displayed on SharePoint pages.
The webchat is working correctly on web and other sites, and the issue appears to be specific to SharePoint.
This is likely due to a recent change on the SharePoint side. Our team is actively investigating and working on a fix.
We will keep you updated as soon as more information is available.