@Elizaveta Omelyusik This is the expected behavior since a single container can handle many requests and would eventually scale out as many more requests come in at the same time. Or if each request is compute intensive, then that could trigger a scale out as well.
If your scenario demands lower concurrency, you could tweak the host.json settings for HTTP to reduce the number of requests handled per instance, forcing it to scale out.
@Pramod Valavala No, the issue is in the request handling. Azure function does not create container each time the request comes. it creates one container and it handles every incoming request in that container. I was wondering how to deal with it