This release is about restoring trust where it matters most. Two issues introduced after the April 29 update were seriously affecting how customers publish, engage, and work day to day: BindTuning web parts failing to render in Microsoft Teams, and the loss of Social Engagement capabilities across several web parts.

Both have been resolved quickly and decisively. This reflects our commitment to listening, responding fast, and strengthening quality controls as Microsoft 365 and SharePoint continue to evolve. Platform changes are constant, and our responsibility is to make sure our components stay reliable, predictable, and safe to use through every shift.

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Social Engagement restored across all applicable web parts: Following the April 29 release, the Social Engagement configuration was no longer available. The field appeared to be missing globally rather than in any single web part, pointing to a regression in a shared component. The field is now restored and behaves consistently across all supported web parts.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Social Engagement restored across all applicable web parts: Following the April 29 release, the Social Engagement configuration was no longer available. The field appeared to be missing globally rather than in any single web part, pointing to a regression in a shared component. The field is now restored and behaves consistently across all supported web parts.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Social Engagement restored across all applicable web parts: Following the April 29 release, the Social Engagement configuration was no longer available. The field appeared to be missing globally rather than in any single web part, pointing to a regression in a shared component. The field is now restored and behaves consistently across all supported web parts.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Social Engagement restored across all applicable web parts: Following the April 29 release, the Social Engagement configuration was no longer available. The field appeared to be missing globally rather than in any single web part, pointing to a regression in a shared component. The field is now restored and behaves consistently across all supported web parts.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Social Engagement restored across all applicable web parts: Following the April 29 release, the Social Engagement configuration was no longer available. The field appeared to be missing globally rather than in any single web part, pointing to a regression in a shared component. The field is now restored and behaves consistently across all supported web parts.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Card and text colors now applied correctly in the "outlined strip" layout: When using the outlined strip layout, text color was applied only to icon text and not to the link title. Text color is now applied consistently to link titles in all cases. Card color continues to apply only to the icon background and is visually hidden when an image is used. A tooltip now clarifies that valid images take priority over card color and icon, reducing configuration confusion.
​

Default image no longer pixelates in wider column layouts: When no custom image was uploaded, the default link image was scaling beyond its native resolution in wider column configurations, resulting in visible pixelation. The default image now scales responsively across all supported column widths, matching the rendering quality of uploaded custom images.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Microsoft Teams rendering restored across all Teams apps: BindTuning apps added to Microsoft Teams tabs were failing to render, and existing apps could not be edited because the configuration panel did not open. The issue was caused by a structural change on Microsoft's side that affected how apps are loaded in Teams. BindTuning components have been updated to align with this change, restoring correct rendering and full add/edit functionality across Teams tabs and channels.
​

Social Engagement restored across all applicable web parts: Following the April 29 release, the Social Engagement configuration was no longer available. The field appeared to be missing globally rather than in any single web part, pointing to a regression in a shared component. The field is now restored and behaves consistently across all supported web parts.
​

Video player now loads correctly when using SharePoint Search as the data source: SharePoint Online's Content Security Policy (CSP) enforcement was blocking the script responsible for rendering the video player when SharePoint Search was configured as the data source, leaving the web part with a broken or empty container. The video player script is now loaded through a CSP-compliant SPFx mechanism, with all scripts served from trusted, SPFx-approved locations in line with SharePoint Online's CSP rollout. Videos render correctly and no CSP violations appear in the browser console.

Fixing issues fast is essential. This release restores key functionality and ensures BindTuning web parts work reliably again across SharePoint and Teams, but it also reinforces something bigger: we are doubling down on resilience and quality as external platform changes roll out at scale.
​

We will continue to respond quickly when something goes wrong, and we will keep investing in the safeguards, testing, and monitoring needed to protect your everyday work. If anything still feels off after updating, let us know through the feedback link in your web part settings. Your input helps keep BindTuning steady, dependable, and ready for what Microsoft ships next.