Release - February 27

❤️ = Users feedback
 

🚨 Global Information 🚨

Sharepoint Authentification : Migration from IDCRL to Modern OAuth Authentication

Publishing : End of Support

SharePoint Online Content Security  : Policy Update

Image picker : SPFX synchronization
 

⭐ Foundation Pack ⭐

Features administration

Powell Manager

Content builder :

Event 

 

✈️ Boost Pack ✈️

Newsletter :

 

🤖 Buddy 🤖

 

 


 

🚨 Global Information 🚨


SharePoint Authentication: 

Removed legacy authentication support in preparation for Microsoft's retirement of the IDCRL protocol (January 31, 2026). The application now exclusively uses modern OAuth authentication for all SharePoint connections.

Reference : Migrating from IDCRL authentication to modern authentication in SharePoint
 

Publishing : End of Support

Microsoft is retiring the classic Publishing model and the “Allow custom scripts” setting.
There’s no immediate impact for Powell customers — existing intranets will continue to run normally, as custom scripting is already managed on our side. If needed, scripting can still be temporarily re-enabled using Microsoft’s PowerShell script.

However, Microsoft will fully remove custom script support by March 2026, which means classic components (like Script Editor or custom layouts) will stop working.

To stay secure and supported, we recommend starting your migration to the modern SharePoint experience as soon as possible.

Reference: MC1117115 – Updates to custom scripting in sites and Classic Publishing site creation | Microsoft

 

SharePoint Online Content Security  : Policy Update

To ensure Powell Manager and your intranet function correctly with SharePoint Online's Content Security Policy (CSP), trusted script sources must be configured. 
This is critical to prevent issues with script execution and maintain compatibility with the latest security updates. Microsoft plans to enforce script blocking for non-compliant scripts on March 1st, 2026. 

Why This Matters ?

SharePoint Online's Content Security Policy enhances security by restricting script sources to trusted domains. Starting March 1st, 2026, scripts not listed in the trusted sources will be blocked, which could cause Powell Manager and your intranet to malfunction, significantly impacting user experience and productivity.
If these configurations are not completed before the enforcement date, scripts will no longer be accessible from your intranet, resulting in broken functionality.

Immediate action is recommended to avoid disruptions.

Key Actions :  

Powell Software has automated the deployment of trusted script sources to minimize manual actions. Two configuration methods are available depending on your environment:

Testing and Validation 
After configuring the trusted script sources (either automatically or manually), verify that all Powell Manager features and intranet components function as expected

Recommended Validation Steps: 

  • Test all custom web parts and dashboards

  • Verify navigation and search functionality

  • Check for script-related errors in the browser's developer console

  • Monitor user feedback for any functionality issues

References: 
For more information on Content Security Policy in SharePoint Online, please refer to the official Microsoft documentation :

Image Picker : Need for a SPFX synchronization

Microsoft is rolling out a new way to handle the image picker in the modern Microsoft SharePoint experience.

To avoid compatibility issues or broken media selection, a synchronization and validation of our SPFx components against the latest supported Microsoft 365 picker implementation is required.

 

⭐ Foundation Pack ⭐

 

Features administration
Audience your features

A new option is now available in:

Manager → Tenant Settings → Environment Settings

You can define an AD group, Microsoft 365 group or SharePoint group as Powell Administrators.

Users included in this configuration can access the Feature Administration section from the Feature dashboard.


 

Feature Administration Dashboard

When accessing Feature Administration, administrators see:

  • The full list of features available in the site collection

  • The audiences currently assigned to each feature

From there, they can manage who is allowed to view and configure each feature.

For each feature, it is possible to assign AD groups, Microsoft 365 groups, or SharePoint groups. These groups determine which users can see and manage the feature.
 

Portal-Based or Autonomous Configuration

Each site can be configured in one of two ways:

  • Linked to the portal configuration
    The site inherits feature audience settings directly from the portal. Any change made at portal level is reflected automatically.

  • Autonomous configuration
    The site manages its feature audiences independently from the portal and can be configured locally.

This allows organizations to manage feature governance at tenant level while still giving flexibility to specific sites when needed.


Powell Manager - User and group selection

All ID-based  pickers within Powell Manager have been replaced with the modern AD group and user picker. This update standardizes the component, aligning the management interface with the modern pickers currently utilized on the front end.

Content builder

Fixed control panel

The floating panel has been replaced with a fixed menu located at the top of the page. This new layout centralizes access to display options, import/export functions, and editing modes, providing a more stable and organized workspace.

Media captions

Captions can now be attached directly to media elements. This addition provides better context for visual content and improves overall accessibility, specifically for users relying on screen-reader software.

Fixed media width

A new formatting option enables users to lock the size and position of media elements, ensuring precise control over the layout and preventing accidental shifts during editing.

Anchor for sections

Direct links can now assign to sections, enabling targeted redirection within a page. Contributors can access these anchor links directly from the section settings. For readers, a clickable link icon now appears when hovering over a section title, making it easy to find and share specific content.

 

Improved widget

Widget loading times have been optimized to improve overall page performance. Additionally, the process for adding widgets has been simplified; the catalog button is now located directly within the webpart slot, reducing the number of clicks needed to configure a page.

 

Event webpart - Outlook Integration

Event WebPart now allow to manage the display and validation of Outlook events directly within the view

Outlook Calendar Sources

You can now select event sources from:
 

  • The current user’s Outlook calendar

  • Calendars shared with the user

  • Pre-configured (pre-set) calendars

These Outlook events are displayed exclusively in the Calendar view.

Note: Outlook events displayed in this web part are view-only. Actions such as registration are not available. However, recurring events are fully supported and managed based on Outlook event settings.

Once configured, available calendars can be selected directly within the Calendar view, allowing users to choose and display their preferred calendars dynamically.


Also, sharepoint event saving process is now automated. Clicking "Add to Outlook" immediately saves the selected event directly into the user's Outlook calendar, streamlining schedule management.

 

 

 

✈️ Boost Pack ✈️

Newsletter

Color background definition

Contributors creating template can now set a default background color for their designs. When users build a newsletter from these templates, they have the flexibility to either retain the predefined background color or remove it entirely based on their needs.

 

Template restriction option

To help preserve the original structure and design of a template, contributors can now restrict the addition of new content blocks. Users working with these specific templates will still be able to delete existing blocks, but they will be prevented from inserting new ones.

Placeholder completion warning

Templates containing placeholders now require user action before the workflow can advance to the next step. Users must either fill in the required content for the placeholder or delete the placeholder block completely. This prevents incomplete drafts or empty tags from moving forward in the creation process.

 

🤖 Buddy 🤖

Knowledge Base: Full Reindex (Force Reindex)

A new Force full reindex action is now available on knowledge bases.Previously, indexing only processed items that had changed since the last indexing run. With this new option, administrators can now trigger a complete reindex of the knowledge base, including all content, even if no changes were detected.
This is especially useful in the following cases:

  • Rebuilding an index after a configuration change
  • Refreshing a knowledge base with inconsistent or outdated indexed data
  • Reindexing an existing knowledge base to the new Cosmos DB storage model (Powell-managed or customer-hosted)

    This full reindex capability is a key step to migrate existing knowledge bases to the new storage approach and unlock advanced Buddy capabilities, including:
  • SharePoint page indexing
  • SharePoint user permission preservation (permission-aware answers)

     

Usage Analytics: Page Refresh

The Usage page in Powell Buddy has been slightly redesigned to improve readability and make agent activity easier to understand.This update helps administrators:

  • Better understand how agents are being used
  • Read usage signals more clearly
  • Manage the lifecycle of agents more effectively (adoption, iteration, cleanup)

    The goal of this refresh is not to change the analytics scope, but to provide a clearer experience for teams monitoring adoption and optimizing agent value over time.

     

 

Chatbot Webpart in Intranet: Visual Identity Alignment

When Powell Buddy is displayed inside Powell Intranet, the chatbot now automatically reuses key visual settings from the intranet theme.The embedded bot can now inherit:Primary colorIntranet font

This improves visual consistency and creates a more native experience for end users, so the AI assistant feels fully integrated into the intranet environment rather than appearing as a separate interface.

 

Was this article helpful?
0 out of 0 found this helpful