We’re excited to announce a major upcoming version of Intranet Enterprise.
This release includes several important updates that modernize the platform, replacing legacy components that are being retired by Microsoft.
In this article, we’ll cover what’s changing, what actions are needed, and what additional updates are included in this release.
SharePoint Add-in retirement
Microsoft has announced the retirement of the SharePoint Add-In model for SharePoint Online by April 2, 2026.
Official Microsoft announcement:
🔗 Retirement announcement for Add-Ins – Microsoft Learn
🔗 Add-Ins and Azure ACS Retirement FAQ
In line with this change, the next version of Intranet Enterprise will move from using the SharePoint Add-In authentication model to the Microsoft Authentication Library (MSAL.js) and Client Certificate.
Important note:
The add-in app retirement only affects SharePoint Online environments. However the retirement only affects online environments, Intranet Enterprise's .net framework version has been upgraded to 4.8.1 which means that some changes on your server side are required. If you are using SharePoint Server (on-premises), your existing Add-In setup will continue to work as usual, but changes are needed.
What you need to do
There will be a few steps that require administrator permissions, such as creating an Azure app registration, setting up a Key Vault, and updating application settings. Please follow the installation guide linked below for detailed instructions.
Download: Wizdom 7.0.0.0 migration guide
Exchange Online to retire Basic auth for Client Submission
Microsoft also announced the Exchange Online to retire Basic auth for Client Submission (SMTP AUTH) by April 30th 2026
If your system is currently using the SMTP Email Service and points to the Exchange SMTP endpoint (smtp.office365.com or smtp-legacy.office365.com), you are affected by this change and need to migrate to the Microsoft Graph API.
Important note: If you are using other SMTP provider (like SendGrid), you can skip this part.
As we already created an application during the previous Add-In retirement migration, now we need some extra step:
Open your existing application in Azure Portal.
Go to API Permissions → Add a permission → Microsoft Graph → Application permissions.
Search for and add Mail.Send.
Once added, click Grant admin consent for your tenant to activate the permission.
Next, update your Intranet Enterprise application settings by add 2 new settings, replace the placeholders value with the Client ID and Client Secret from your Azure App Registration:
<add key="EmailSenderClientId" value="<your_application_id>" /> <add key="EmailSenderClientSecret" value="your_application_secret" />
Summary
This Intranet Enterprise release prepares your intranet for the retirement of the SharePoint Add-In model and moves to a modern and secure authentication flow.
Your overall Intranet Enterprise experience will remain familiar, but more secure and future-ready.
For further assistance, please reach out to our support.
Comments
0 comments
Please sign in to leave a comment.