msgraph-sdk-javascript | Microsoft Graph client library for JavaScript | SDK library

I have several Office 365 SharePoint sites. I would like my NodeJS based daemon that is registered as an Azure App Registration to write to several different folders within these SharePoint sites. I am struggling to get the correct syntax of the request url correct to create a resumable upload session. This is made worse by fairly unclear and non working examples provided by Microsoft. An important detail here is that the application is doing this without user delegation, meaning no user is using the application to cause these files but rather it is and should be the entity who owns the file uploads. Many examples show how to do this with user delegation. Some of the files being uploaded include binary or text content.

I have read quite a bit of the ms docs and referred to many questions. I even watched many videos on YouTube and started digging through source code with the microsoft-graph-client incase there were insights to be had there. I don't think I can review graph server code or if that would be helpful. Below are just a few that I still I have open due to being closely related.

• Samples from GitHub
• GitHub repo docs - LargeFileUploadTask
• MS Docs - Getting drive item children
• MS Docs - createuploadsession
• SO - sharepoint-create-a-new-file-in-a-specific-drive-with-graph-api

Here is my latest attempt which I feel should be getting pretty close:

Desired Behaviour

Create a group via Microsoft Graph, using the JavaScript SDK and MSAL in a single tenant application with delegated API permissions.

Actual Behaviour

My goal is to create a local account, like michele@gmail.com, in Azure Active Directory B2C.

I want to use my own UI, so I started to look at how to implement the API. After some research, it looks like the best way to do it should be via Microsoft Graph.

I started by following Manage Azure AD B2C user accounts with Microsoft Graph, and I properly created an app (not sure if I need to choose the third options, but looks like the broader one):

with the following permissions (updated following also @Tony Ju screenshot):

Then I created the client secret and coded my own auth provider