This is my installation of Windows WSL and SharePoint Development Environment. The procedure and technology is ever-changing, the details might change, but the process is worth documenting, at least for myself, this is a working guide as of writing (2021-12-20).

Installing Windows Terminal

Installing Windows Terminal is not a prerequisite, but it will make your life much easier. Open Windows Store and search for Windows Terminal and click on Install.

Installing WSL 2

Installing WSL has never been easier than now. For that you only need to run a command in terminal as an Administrator and restart your computer:

In this post I would like to share some findings from setting a deployment of SPFx. In my work:

• I need to deploy SPFx solutions using Azure Pipelines
• I need to use the least privileges/permissions
• I cannot use Legacy Authentication

First of all, big thanks to @waldekm and the whole community of @office365cli and @m365pnp for the quick help, and that outside working hours.

Let’s take a look at the setup piece by piece

Site Collection App Catalogs are great for special cases (like developing apps or site unique apps), but using them on scale would be a mess.

I got a question: Why should we use the Tenant App Catalog at all when we could enable a Site Collection App Catalog on every teamsite? So the suggestion here is to install SharePoint Framework Packages on many Site Collection App Catalogs, instead of the Tenant App Catalog. In that way those wouldn’t be visible for all users in the “Add an app” page.

Once you approve a permission request from an SPFx app, it will grant the same permission to all other apps in the same tenant.

Nothing new, but I want to emphasize that in that blog post only dedicated to that. You can read it here:

• MS Docs. Connect to Azure AD-secured APIs in SharePoint Framework solutions

A simple sketch over the permissions.

Here is a simple FAQ to explain what it means: