- Graphwise Platform Documentation
- Graphwise Integrations
- Introduction to Graphwise for Microsoft 365
- Installation and Configuration Guide
- Upgrading Graphwise for Microsoft 365
Upgrading Graphwise for Microsoft 365
23/06/2026
This section provides an overview of the steps to upgrade of Graphwise for SharePoint.
Important
Before you start, ensure that you fulfill the minimum prerequisites and requirements.
Follow the steps below to upgrade the Graphwise for Microsoft 365:
Use the
GraphwiseForSharePointAdminStructureUPDATEScript.ps1PowerShell script from the deployment package to update system lists that were created during installation.The procedure is the same as for a new installation: Generate System Lists. In step 1, runGraphwiseForSharePointAdminStructureUPDATEScript.ps1instead.Upload packages with updated SPFx functions into corresponding app catalogs.
Upload the Graphwise for SharePoint Administration application package (
graphwise-for-sharepoint-admin-web-part.sppkg) into the corresponding site app catalog created during installation.Upload the Graphwise for SharePoint Search application package (
graphwise-for-sharepoint-search-web-part.sppkg) into the corresponding site app catalog created during installation if you want to use the Tagging module.Upload the the Graphwise for SharePoint Command Bar and Views extension package (
graphwise-for-sharepoint-list-webparts-client-side-solution.sppkg) into the tenant app catalog for the Tagging module.
Upload packages with updated Azure functions into corresponding function apps. You should have a dedicated function app for each module (Tagging and SharePoint synchronization) that you are using.
Optional: You can change the configuration settings of Azure functions.
Note
If you have already changed those settings during installation or previous upgrades, your changes have been preserved.
You can change the authentication method to protect the API calls between Graphwise for SharePoint and Graph Modeling.
If you want to use the Tagging module, you can lower Azure costs by exclude- and include-listing certain file types for tagging. You can also set a limit on the file size.
Note
The tagging process works with text-based files; other file types will not return any results.
If you want to use the Term Store Synchronization module, you can enable and configure logging of Term Store synchronizations on the concept level.
You can enable Microsoft's built-in App Service authentication to provide the Azure functions with an additional layer of security.
If you are experiencing issues after the upgrade, you can use the
GetVersionandGetWebsitefunctions to test whether the Graph Modeling server running and that Graphwise for SharePoint can access it.