🛣️ Roadmap phase 1: Migrating Provisioning and Modernization Engines to PnP Core SDK

Overview

As part of our long-term strategy to evolve the PnP ecosystem, we are thinking of migrating the Provisioning Engine and Modernization Engine from PnP Framework into PnP Core SDK. This is being carefully planned, and we are committed to making it as smooth and supported as possible for every team.

Why are we doing this?

PnP Core SDK was built from the ground up for modern .NET development. It runs cross-platform - anywhere .NET runs - and represents the long-term future of PnP tooling for SharePoint Online. Consolidating the Provisioning and Modernization engines into PnP Core SDK means:

• A single, actively maintained SDK for all your needs
• New features and improvements land in one place
• Full cross-platform support out of the box
• A healthier, more sustainable codebase for the community

What do we plan to change?

We are thinking of copying the Provisioning and Modernization engines into PnP Core SDK as new, dedicated projects. Once that work is complete, those specific parts of PnP Framework will be marked as deprecated.

After deprecation:

• Developers using Provisioning or Modernization functionality in PnP Framework will receive deprecation warnings pointing them to PnP Core SDK.
• No new PRs or features will be accepted for these parts of PnP Framework.
• Everything else in PnP Framework remains unchanged at this stage.

Timeline

🗓️ Target: We would like to do this during the 4th quarter of this year (2026)

What should you do?

• If you rely on the Provisioning or Modernization engines, start planning your migration to PnP Core SDK.
• Watch this repo and the PnP Core SDK repo for updates.
• Reach out in community calls or GitHub Discussions - we're happy to help you plan your migration.

This is Phase 1 of the PnP Framework deprecation roadmap.
See the companion issue for Phase 2: full PnP Framework deprecation.