SharePoint Online Provisioning Service


See the possibilities
Deploy > Test

The SharePoint PnP Page Transformation UI solution

Objectives of this solution

Important: Please be aware that the Page Transformation UI solution is currently in preview

The Page Transformation UI solution makes it possible for end users to request a modern version of a wiki or web part page. The generated modern page will have a page banner web part on top of the page which will allow the user to keep the generated page or discard it. When the user discards the page the solution will show a feedback dialog asking for a reason why the page was not good.

page transformator web part

Below diagram shows the high level architecture of the solution:

  1. From any of the UI elements the users triggers the creation of a modern version of the selected wiki or web part page. This will be done by calling a "central" proxy page which is hosted in the modernization center site collection
  2. The "central" proxy page contains an SPFX web part that makes a call to an Azure AD secured Azure Function
  3. The Azure Function uses the SharePoint Modernization Framework to create a modern version of the page. This created modern version does contain a banner web part which provides the end user with the option to keep or discard the created page. Important to understand is that this modern page is a new page with name like migrated_oldpagename.aspx
  4. If the page is discard a feedback dialog is shown asking the user for a reason why the page was not good. This information is then stored in a central list in the modernization center site collection.
  5. If the users keeps the page then the modern page gets the name of the original page and the original page is renamed with an old_ prefix

page transformator web part

Note - There might be small differences between the screenshot from the SharePoint look book and the end results of the template. Template automation will get you as close as possible given certain API level limitations. Templates are also designed to be as independent as possible, which has resulted some compromises on the implementation.


Here are current prerequisites for making this solution work in your tenant.

Important: You do have to setup the needed Azure function app upfront. See for details on how to do that.

  • You will need to be a tenant administrator to be able to deploy this solution
  • Automatic end-to-end provisioning only works with English tenants
    • All solutions and web parts are also English in the current implementation
  • A tenant 'App Catalog' must have been created within the 'Apps' option of the SharePoint Admin Center

Permissions required

Tenant Admin

Try it and


  • Business Processes
  • Technology Samples