Skip to content
English
Sign in
  • There are no suggestions because the search field is empty.

Important Announcement about OneNote

This article references changes to how Orchestry will handle OneNote Notebooks during provisioning

Please read the important announcement below as it may impact the functioning of your Orchestry templates. 

Context 

As you may know, Orchestry’s Provisioning engine currently supports the cloning of custom OneNote notebooks via the Live Template feature. This allows customers to setup template-specific notebooks that are prepopulated with sections and content appropriate for a newly created workspace. 

On February 20, 2025, Microsoft shared via the Message Center (see message MC1011142) that it was retiring the use of App-Only authentication for OneNote in Microsoft Graph and that this would take effect on March 31, 2025. 

Impact on Orchestry 

The Orchestry platform utilizes the most current Microsoft APIs to ensure stability and performance are maintained. Orchestry prefers to use App-Only authentication because this allows the application to act without needing to route requests through a user (or service account).

In our experience, as these user accounts become inactive, their authentication expires, rendering core functionality increasingly unstable. Using App-Only authentication remains a best practice for long running background tasks and is one of the intended purposes of App-Only. In fact, Microsoft continues to roll out updated APIs that offer App-Only authentication – a recent example being Microsoft Planner. 

Impact to Customers 

Orchestry has been investigating possible solutions to address this gap since the announcement on February 20th, but have concluded that there are no good solutions that do not impact Orchestry stability and functionality.

Beginning on or before March 31, 2025, Orchestry will no longer be able to: 

  • Clone custom notebooks to new sites 
  • Create tabs in Teams that point to those notebooks 
  • Create links on the SharePoint site’s navigation that point to those notebooks 
  • Workspace Details will no longer display a link to the associated notebook 
  • Team Information Tab/Web Part will no longer display the associated notebook

Next Steps 

While this change was very abrupt, it does reflect a general change in direction away from OneNote and towards Microsoft Loop. We suspect this trend will continue in the future. 

If this change is unwanted, please share your feedback directly with Microsoft, via the message center, or via your Microsoft customer account representative(s). 

If the persistence of customized OneNote notebooks is absolutely necessary, you may want to consider using a Provisioning Webhook to call custom automation (e.g,: Power Automate or Azure Logic) to continue cloning notebooks using the delegated approach.