🛣️ Roadmap phase 1: Migrating Provisioning and Modernization Engines to PnP Core SDK
@Adam-it ya está trabajando en esto.
Desde el 12/8/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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.
- Lenguaje dominante
- C#
- Estrellas
- 259
- Forks
- 161
- Merge medio
- 13 d 21 h
- PR fusionados (30 d)
- 2
Preparar el entorno
Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de pnp/pnpframework
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
pnp/pnpframework#1284 ·
-
area: provisioning ⚙
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
pnp/pnpframework#1170 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
pnp/pnpframework#913 ·
-
PnP Provisioning futureAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
pnp/pnpframework#1286 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
pnp/pnpframework#1283 ·
Todos los issues de pnp/pnpframework
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
SubtitleEdit/subtitleedit#15462 ·
Los mantenedores suelen responder en 1 día
-
:watch: Not Triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
comp:instrumentation.aspnetcore
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
open-telemetry/opentelemetry-dotnet-contrib#5427 ·
Los mantenedores suelen responder en 1 día
-
design-proposal
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
dotnet/aspnetcore#69592 ·
Los mantenedores suelen responder en 1 día
-
Client Container Registry customer-reported needs-team-attention question Service Attention
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Azure/azure-sdk-for-net#63470 · 3 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día