This article is for users of Lasernet Core 10.12.1 and earlier versions.
If your Lasernet Core 10 version is between 10.0 and 10.12.1 (inclusive) and your configuration contains an affected module, but you do not follow the steps in this article, your Lasernet Core system will stop working on the 1st April, 2027.
As a result of our renaming from Formpipe to Lasernet Group, we updated the Microsoft Azure app registrations that underpin the user-based authentication for the OneDrive, Outlook Mail, and SharePoint modules in Lasernet Core 10. Due to these changes, if your Lasernet Core configurations use any of the affected modules, you must upgrade to Lasernet Core 10.13.3 and then update and redeploy those configurations.
Note for Users of Lasernet 9 and Earlier
This issue also affects Lasernet 9 and earlier versions. If your Lasernet version is Lasernet 9 or earlier and your configuration contains an affected module, you must upgrade to Lasernet Core 10.13.3.
Affected Modules
If your Lasernet Core 10 workflow contains any of the modules listed below, you must follow the steps in this article:
Input
OneDrive input
Outlook Mail input
Output
OneDrive output
Outlook Mail output
SharePoint output (only if the module connects through Graph API and user-based authentication. Modules that use Graph API and application authentication are not affected)
Before proceeding to the update process, determine whether your workflow contains an affected module.
The Update Process
The update process involves upgrading Lasernet Core and updating your Lasernet Core configuration, testing the updated configuration, and then deploying it to production environments.
To achieve this, follow these steps:
Upgrade to Lasernet Core 10.13.3. You must upgrade Lasernet Server and all client applications, such as Lasernet Developer and the Lasernet Printer Service app. For upgrade instructions, see the Lasernet Core Upgrade Guide.
Note
If you are a hosted customer, the Lasernet Cloud team will carry out this update for you.
Load your Lasernet Core configuration in Lasernet Developer.
For every affected module in the workflow defined by the configuration:
Open the module’s Properties window.
Reauthorize the module (refreshing the access token is not sufficient). The Lasernet Administrator user must carry out this step. The method depends on the module:
OneDrive: On the Setup tab, click Remove Authorization (if the button is available), then Obtain Authorization, and follow the authorization process.
Outlook Mail: On the Setup tab, click Remove Authorization (if the button is available), then Obtain Authorization, and follow the authorization process.
SharePoint: On the Setup tab, click Remove Authorization (if the button is available), then Obtain Authorization, and follow the authorization process.
Note
The SharePoint list in a SharePoint output module contains connections that are either:
Embedded, meaning that the connection is defined within that SharePoint module and can be used only by that module.
Defined in the Connections list in the Commands tool in Lasernet Developer. These connections can be used by any SharePoint module in the workflow defined by the Lasernet Core configuration.
If the SharePoint module uses an embedded connection, follow the “obtain authorization” instructions below this Note box.
Else, if the SharePoint module uses a connection defined in the Commands tool, you can either follow the “obtain authorization” instructions below this Note box, or you can edit the connection in the Commands tool (and use the Obtain Authorization and Test Connection buttons in the connection’s Properties window). Regardless of how you edit the connection, your changes are available to every SharePoint module that uses the connection.
On the Setup tab of the SharePoint module’s Properties window, click the Connection tab.
From the SharePoint list, select the SharePoint 365 connection that the module is using.
Click Edit.
In the connection properties window, click Obtain Authorization.
As part of the authorization process, grant the new app registration access to your organization’s tenant.

Note
Depending on your organization’s Microsoft Azure configuration, this part of the process might require an Azure administrator to approve the access request. In this scenario, follow these steps:
Request admin approval for the access request:
Enter a justification for the request.
Click Request approval.

Azure will confirm that the request has been sent:

If a Redirection Error message is displayed, click OK.

The Azure administrator must approve your request in the Azure Portal.
In Lasernet Developer, click Obtain Authorization again, and then follow the authorization process.
SharePoint module only: After the authorization process completes, click Test Connection.
Delete
C:\ProgramData\Formpipe Software\Lasernet 10\Service\Instance\Retainer. If you are a hosted customer, the Lasernet Cloud team will carry out this update for you.Patch the updated configuration to a test Lasernet Core server. Thoroughly test the updated modules.
When the configuration is verified as working, commit your configuration changes. The Lasernet Administrator user must carry out this step.
Deploy the new configuration revision to the production Lasernet Core server. The Lasernet Administrator user must carry out this step.
Now that your Lasernet Core configuration has been updated, you can remove the Formpipe apps from your tenant.
Remove the Old Apps from your Tenant
After you have performed the upgrade process steps and verified that Lasernet Core is working with the new modules, you can remove the old apps from your tenant.
To do this, follow the process described in the Determine Whether Your Workflow Contains a Module Affected by the Lasernet Group App Registrations Changes article to find the Formpipe apps. Use the provided application IDs to verify that the listed apps relate to the Formpipe tenant, and then delete them.

