July 8, 2026

Current Status: Cause Identified – Updated Procedure

We inform you that the incident affecting the display of components 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 procedure below.

Procedure

1. Add Jint domains to SharePoint Trusted Script Sources

⚠️ This operation must be performed by a SharePoint administrator.

1. Go to the SharePoint Admin Center.
2. In the left menu, click on Advanced.
3. Access the Trusted Script Sources section.
4. Add the following addresses:
   • https://sp-cdn.jint.io
   • https://cdn.jint.io
   • https://cdn.mozzaik365.net/ ⚠️ The trailing "/" is mandatory.
5. Save the changes.

2. Allow Jint domains in your network infrastructure

⚠️ This step applies only 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.io
• https://cdn.jint.io
• https://cdn.mozzaik365.net/ ⚠️ The trailing "/" is mandatory.

If the problem persists

If these actions are not sufficient to restore the display of components, you can send us your network and console logs to help us further analyze the issue.

👉 See the network trace extraction procedure to learn how to retrieve them, then send us the .HAR file along with the console screenshot via 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 is available.

What to do on your side?

• 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 problem persists after these actions, send us your network and console logs following the procedure above

We 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: the root cause of the incident has been identified. It is related to a recent change made 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 allowed script sources of your SharePoint tenant. This operation must be performed by your SharePoint administrator.

🔹 Procedure

1. Go to the SharePoint Admin Center > Advanced > Script Sources
2. Click Add a source
3. Copy-paste the following URL: https://cdn.mozzaik365.net/ ⚠️ Note, the trailing "/" is mandatory.

Once this configuration is applied, Jint components should display correctly again on your SharePoint pages.

Next steps

Our teams continue to actively monitor the progress of the fix from Microsoft. We will publish a new 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 to do on your side?

• 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 have difficulties applying this configuration or if the problem persists, contact support specifying "Jint components incident"

We thank you for your patience and cooperation. 

The Jint Support Team

March 31, 2026

Current Status: Investigation Underway

Hello,

We are currently experiencing an incident impacting many environments.
 

Observed symptoms

• Mozzaik components no longer display on pages
• A blue error message appears instead of the components

Suspected origin

Initial analysis indicates this might be related to ongoing changes within the Microsoft environment.

Our teams continue investigations to confirm the exact cause and identify an appropriate solution.

Actions underway

Our technical teams are fully mobilized to:

• Analyze the observed behavior
• Precisely identify the cause of the incident
• Implement a fix as soon as possible

How you can help

To help us accelerate the analysis, you can provide technical information if possible:

• A screenshot of the error message (by clicking on “Technical details”)
• The network traces (.HAR)
• The contents of the browser console

🔹 Network traces

1. Go to a SharePoint page where the problem is visible
2. Open the developer tools (F12 or right-click > Inspect)
3. Go to the Network tab
4. Refresh the page (F5)
5. Once loading is complete, export the traces in .HAR format

🔹 Console

1. Go to the Console tab
2. Right-click in the area
3. Select “Save as”

👉 A detailed procedure is available in our dedicated article.

Next steps

We will publish an update on this page as soon as a significant development is identified (confirmed analysis, workaround, or fix).

The article will be updated with the status Resolved once the situation is fully stabilized.

What to do on your side?

• 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 critical activity, you may contact support specifying “Jint components incident”

We thank you for your understanding and cooperation.
Our teams are fully mobilized to restore the situation as quickly as possible.

The Jint Support Team