Beginning on October 26, 2026, we are expanding support for.NET Framework 4.8 across plug-ins and custom workflow activities in Microsoft Dataverse. Migration to this framework follows the standard .NET Framework upgrade approach, while accounting for Dataverse-specific compatibility and deployment requirements.
How does it affect me?
Migrating to .NET Framework 4.8 provides the following benefits for your plugins and custom workflows:
- Keep custom plugins and workflow activities on a supported framework version.
- Maintain access to applicable security and servicing updates.
- Modernize solutions currently targeting older framework versions, such as .NET Framework 4.6.2.
- Use a consistent framework target for individual plugin assemblies and plugin packages.
Continue using existing plugin code with minimal changes - .NET Framework 4.8 is backward compatible with applications built for earlier .NET Framework versions.
Existing plug-ins targeting older supported framework versions are expected to continue running, and existing assemblies will not be automatically upgraded, retargeted, or recompiled.
Following the deployment of Microsoft Dataverse Build version
9.2.26092.xxxxx or higher, both individual plug-in assemblies and plug-in packages will support .NET Framework 4.8. Individual plug-in assemblies targeting .NET Framework 4.8 can already be registered. Please note that
Microsoft Dataverse service update 9.2.26092.xxxxx or higher must be applied for .Net framework 4.8.
Plug-ins and packages targeting .NET Framework 4.8.1 or above will remain unsupported.
What action do I need to take?
This message is for awareness, and no action is required.
We recommend admins to review existing plug-ins and custom workflow activities, update applicable projects to .NET Framework 4.8, recompile and test them in a non-production environment, and deploy through their standard release process.
For more information, please visit
Supported customizations for Microsoft Dataverse.