applying fine-grained control over scale out

Question

I have a blob-triggered function that will take the contents of the blob and send it to an sftp drop location.

Depending on the sftp destination, I need to be able to control the scale out.

For example: If destination == 'sftp.alex.com' then scale the function out to no more than 5 instances, if destination == 'sftp.othersite.com' then scaleOut to no more than 20.

Blob example:

{
  "payload":"binary-formatted string",
  "destination":"sftp.alex.com"
}

Is this type of fine-trained control over the scale out of the azure function available?

Answer 1

Is this type of fine-trained control over the scale out of the azure function available?

No, it's impossible.

For Consumption Plan, you can't directly affect the scaling algorithm of Azure Functions. This serverless plan scales automatically , and you're charged for compute resources only when your functions are running.

For App Service Plan, you can scale out instance count manually or automatically .

Blob Trigger specifically has some known limitations. Particularly, there are might be delays in processing blob . For faster scaling, I suggest you using Event Grid triggers , which should scale pretty well for both "priority" and "non-priority" customers of yours. Refer to this similar issue .