
Hi @Jean Niblett,
Good day! Thank you for reaching out to the Microsoft Q&A forum and sharing the details of your issue.
Microsoft has confirmed that the retirement of SharePoint Add-Ins applies directly to Project Online, as it is built on top of SharePoint Online. This means:
- Any SharePoint Add-In used in Project Online will cease to function after April 2, 2026.
- Custom scripting, which is essential for editing Classic SharePoint pages and accessing project data webparts, will no longer be supported.
- Modern pages cannot currently replicate the functionality of Classic Project Pages due to the lack of editable project data webparts.
Therefore, Microsoft strongly encourages migration from Add-In models to the SharePoint Framework (SPFx). This is the modern, supported extensibility mechanism for SharePoint Online.
- SharePoint-hosted Add-Ins should be rewritten as SPFx web parts.
- Provider-hosted Add-Ins are best moved to external services secured via Microsoft Entra ID, with SPFx used for SharePoint-hosted UI layers
Assessment Tools and Reports:
You can scan your tenant with the Microsoft 365 Assessment tool, then generate a Power BI report to identify:
- Where SharePoint Add-Ins are being used
- In which sites
- Their dependency on Azure ACS (for provider-hosted solutions)
This helps map out migration priorities and potential remediation paths.
For more detail, you can take a look at: SharePoint Add-In retirement in Microsoft 365
Here're suggestions you can try before functionality loss:
1. Run the Microsoft 365 Assessment Tool now
- Identify all current Add-In dependencies inside Project Online and SharePoint.
2. Engage with Microsoft Support Representative or your account team
- Request official guidance regarding Project Online classic page editing and availability of project data post - April 2026.
3. Evaluate alternative solutions
- Can core project features be moved to SPFx-based custom web parts?
- Or could another hub like Dataverse + Power Apps, or even PM platforms like Planner or Project for the Web serve as a temporary or long-term solution?
4. Plan a migration or redesign roadmap
- Prioritize areas where custom scripting and project field editing are essential.
- Build prototypes using SPFx and modern pages now - before changes crash past the retirement date.
5. Monitor Microsoft 365 Message Center
- For updates specific to your tenant.
I hope this information is helpful. Please follow these steps and let me know if it works for you. If not, we can work together to resolve this.
Thank you for your patience and your understanding. If you have any questions, please feel free to reach out.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.