This implementation is using the OAuth 2.0 Authorization Code Flow, which means that the access to SharePoint will be performed with the credentials of the currently logged-on user, i.e. the user permissions will apply.

According to Microsoft’s documentation:

You are authenticating on behalf of a user who is currently logged in to the BC client.

You cannot – but PR is underway to add metadata.

The file can be accessed as long as the user has access to the same Sharepoint. This can also be achieved by providing the necessary API permissions within the Azure portal.

There is a chance that we may look into the OneDrive functionalities and perhaps even the differences between Sharepoint and OneDrive as well, we do not wish to make promises, but this is one of the ideas that we may realize in the future.

I recommend using Sharepoint for long-term file storage. If there is anything that uses BLOBs or media within your solution, there is also a chance to save database space by using Sharepoint/OneDrive to save BLOBs or images. If you’re using an OnPrem solution, this can help save disk space.

The limits are described here in Microsoft’s documentation. Generally speaking, the size limitations are based on your subscription plan.

This is one of the ideas that we may explore later in the future, especially if we’ll explore OneDrive connector functionalities as well. We do not wish to make promises, but this is one of the ideas that we may realize in the future.