MC1515315 Medium
Dataverse – Information about support for .NET Framework 4.8 Plugins and custom workflow activities
Summary AI-generated
Support for .NET Framework 4.8 expands across Dataverse plug-ins and custom workflow activities starting October 26, 2026, enabling modernization and continued access to security updates.
Suggested actions AI-generated
- Review existing plug-ins and workflow activities
- Update applicable projects to .NET Framework 4.8
- Recompile and test in non-production
- Deploy through standard release process
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1266693 Microsoft Dataverse - Discover, build, customize, and extend with management MCP server
- MC1527468 Microsoft Dataverse - Custom connector definition access update
- MC1464869 Dynamics 365 Contact Center - Platform observability and plug-in performance
- MC1210142 Microsoft Dataverse - Build your agentic flows with Dataverse SDK for Python
- MC1472179 Dataverse - Assign non-Power Platform licensed Entra users to Dataverse Activities
- MC1421853 Dynamics 365 Finance - Unified e‑invoicing integration framework
Original post from Microsoft
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:
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.
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.
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.