We're currently in the process of building a solution that's very similar to SharePoint's built-in Content Organizer:
- Documents are uploaded to a central location (Document Library)
- Document metadata is applied
- Document is moved to it's determined target location based on the metada applied in step 2
- Additional metadata is applied
We've decided to built our own content-organizer because of the current limitations in SharePoint Online. Most obvious: There's a maximum of 3 days documents stay in the Drop Off Library before they're routed (The Timer Job in SPO runs once every 3 days). Also, modern UI is not available / fully working for Drop Off library.
Our content organizer logic is triggered by a Web Hook on the document library. Changes are then queued in Azure storage queues and the logic to move documents and apply metadata is executed from an Azure Function making use of Office Dev PnP and SharePoint CSOM libraries.
When hosting our Azure Function in a Consumpion plan we have limited control over the amount of instances our function is ultimately running. During tests we ran into throttling issues that didn't happen when our code was executed from a single instance process (console application). So I suspect multiple instances of this Function cause throttling issues to arise, at least quicker...
We've followed the throttling prevention guidance written in the article below:
https://docs.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-o...
Are Functions calling CSOM hosted in a Consumpion plan a viable / supported approach? Should we go for hosting 1 instance in a more traditional App Service plan? What are your thoughts?
