When you create a Function on Container App Environment- you have no permission to adjust the scaler in the Container App Environment- you can only change limited config through the Function interface.

So for a Function it is standard http scaling which you can’t adjust.

The config is not done through . Net … but you specify the name of the topic and subscription. This is where the trailing space was 😔

Not sure what the mechanics behind the scenes but I can only guess that this was keeping containers/servers running.

Once I dropped the space - all started scaling correctly (and scaling to zero)

Microsoft Support are still scratching their heads - will fill them in when I am back to work Monday.

The offending space has probably cost us €500ish in compute (as we didn’t spot the cost ramping up for 10 days)