November 2, 2026
Current status: Optimization work completed - Monitoring in progress
In October 2026, our teams carried out various platform optimization activities. Display errors affecting the components (blue error message) should therefore no longer occur.
What should you do?
- If your components are displayed correctly, no action is required
- ⚠️ If the error still appears, apply the workaround described in the instructions from the July 8, 2026 update, further down in this article, with the help of your SharePoint and/or network administrator
- If the issue persists after applying this workaround, send us your network (.HAR) and console logs by following the network log extraction procedure, through our contact form, specifying “Jint components incident”
Next steps
We will continue to monitor the situation. The article will be updated with the status Resolved once the situation is fully stabilized.
Thank you for your patience and cooperation.
The Jint Support Team
July 8, 2026
Current status: Cause identified – Instructions updated
We would like to inform you that the incident affecting component display may still occur in some environments. The cause remains related to a change on Microsoft's side in the SharePoint environment.
To ensure the best possible compatibility, please follow the updated instructions below.
Instructions
1. Add the Jint domains to SharePoint Trusted Script Sources
⚠️ This operation must be performed by a SharePoint administrator.
- Go to the SharePoint admin center.
- In the left-hand menu, click Advanced.
- Go to the Trusted Script Sources section.
- Add the following addresses:
https://sp-cdn.jint.iohttps://cdn.jint.io-
https://cdn.mozzaik365.net/⚠️ The final "/" is required.
- Save the changes.
2. Allow the Jint domains in your network infrastructure
⚠️ This step only applies to organizations using a VPN, firewall, or proxy.
Please ask your network administrator to add the following addresses to the list of allowed domains:
https://sp-cdn.jint.iohttps://cdn.jint.io-
https://cdn.mozzaik365.net/⚠️ The final "/" is required.
If the issue persists
If these actions do not restore component display, you can send us your network and console logs to help us investigate further.
👉 See the network log extraction procedure to learn how to retrieve them, then send us the .HAR file and a console capture through our contact form, specifying “Jint components incident”.
Next steps
Our teams continue to monitor the situation. We will update this article as soon as new information becomes available.
What should you do?
- If possible, apply both workaround steps above with the help of your SharePoint and/or network administrator
- There is no need to open a ticket if the workaround resolves your issue
- If the issue persists after these actions, send us your network and console logs by following the procedure indicated above
Thank you for your patience and cooperation.
The Jint Support Team
April 24, 2026
Current status: Cause identified – Workaround available
We have an important update to share with you: the cause of the incident has been identified. It is related to a recent change introduced by Microsoft in the SharePoint environment.
More technical details are available in our GitHub ticket opened with the Microsoft teams: 👉 https://github.com/SharePoint/sp-dev-docs/issues/10784
Workaround available
While waiting for a permanent fix from Microsoft, a workaround is already available.
It consists of adding our CDN to the authorized script sources in your SharePoint tenant. This operation must be performed by your SharePoint administrator.
🔹 Instructions
- Go to the SharePoint admin center > Advanced > Script sources
- Click Add a source
- Copy and paste the following URL:
https://cdn.mozzaik365.net/⚠️ Please note that the final "/" is required.
Once this configuration has been applied, the Jint components should be displayed correctly again on your SharePoint pages.
Next steps
Our teams continue to actively monitor the progress of the fix on Microsoft's side. We will publish another update as soon as the situation is fully resolved without requiring a workaround.
The article will be updated with the status Resolved once the situation is fully stabilized.
What should you do?
- If you have not yet applied the workaround, we invite you to do so with the help of your SharePoint administrator
- There is no need to open a ticket if the workaround resolves your issue
- If you encounter difficulties applying this configuration or if the issue persists, contact Support and specify "Jint components incident"
Thank you for your patience and cooperation.
The Jint Support Team
March 31, 2026
Current status: Investigation in progress
Hello,
We are currently experiencing an incident affecting many environments.
Observed symptoms
- Mozzaik components are no longer displayed on pages
- An error message (blue screen) appears instead of the components
Suspected cause
Initial analyses indicate that this may be behavior related to ongoing changes within the Microsoft environment.
Our teams are continuing their investigation to confirm the exact cause and identify an appropriate solution.
Ongoing actions
Our technical teams are fully engaged in:
- Analyzing the observed behavior
- Precisely identifying the cause of the incident
- Implementing a fix as soon as possible
How you can help
To help us speed up the analysis, you can send us technical information if possible:
- A screenshot of the error message (by clicking “Technical details”)
- The network logs (.HAR)
- The browser console details
🔹 Network logs
- Go to a SharePoint page where the issue is visible
- Open the developer tools (F12 or right-click > Inspect)
- Go to the Network tab
- Refresh the page (F5)
- Once loading is complete, export the logs in .HAR format
🔹 Console
- Go to the Console tab
- Right-click in the area
- Select “Save as”
👉 Detailed instructions are available in our dedicated article.
Next steps
We will publish an update on this page as soon as significant progress is identified (confirmed analysis, workaround, or fix).
The article will be updated with the status Resolved once the situation is fully stabilized.
What should you do?
- There is no need to open a ticket for this incident while it is under investigation
- We invite you to follow updates directly on this page
- If you experience a blocking impact on a critical activity, you can contact Support and specify “Jint components incident”
Thank you for your understanding and cooperation.
Our teams are fully engaged in restoring the situation as soon as possible.
The Jint Support Team
Comments
0 comments
Please sign in to leave a comment.