Perhaps you need an app principal to be able to access a particular SharePoint site? You could be using the great SharePoint PnP PowerShell module and you want to connect via an AppId and AppSecret.
By default, all SharePoint sites created in SharePoint Online are set to the United States time zone and locale. In the past, you had to either manually or programmatically set the timezone, region and locale for every site including all sites generated by the creation of an Office 365 group.
If you've used SharePoint Online before you've probably come across some of it's limitations. Of course you can store up to 30 million items or file in a SharePoint list but if a list view shows more than 5,000 item then you will probably see a nice error either in the web UI or from console if you use any of the SharePoint tools.
So you have a project that will only run/build using an old Node.js version that you can't upgrade but you also do development using the latest version. What do you do? Only build using your CI pipelines? That could work but would make the development process slow.
I've run into this problem a few times, mainly with SharePoint Framework (SPFx) solutions that only support a particular (old) node version. This is where the Node Version Manager comes in and saves us!