April 24, 2026

Current Status: Cause Identified – Workaround Available

We have an important update to share: the 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 involves adding our CDN to the allowed script sources of your SharePoint tenant. This operation must be performed by your SharePoint administrator.

🔹 Instructions

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

Once this configuration is applied, the Jint components should display 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 a new update as soon as the situation is fully resolved without requiring a workaround.

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

What You Should Do

• If you have not yet applied the workaround, we invite you to do so with the help of your SharePoint administrator
• It is not necessary to open a ticket if the workaround resolves your issue
• If you encounter difficulties applying this configuration or if the problem persists, contact support specifying "Incident Jint components"

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 affecting many environments.
 

Observed Symptoms

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

Suspected Cause

Initial analyses indicate that this may be related to ongoing changes within the Microsoft environment.

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

Current Actions

Our technical teams are fully engaged 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 items from 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).

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

What You Should Do

• It is not necessary 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 specifying “Incident Jint components”

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

The Jint Support Team