@Samerkassem yes, you are right, the scheduling is a piece of code that needs a long-running process to work properly, short-lived execution like azure functions won't work as expected for you. i suggest just installing an on-premise server in a long-running process as usual if the scheduling is a core piece for your use case.
having said that, you can definitely create a serverless architecture if you implement the scheduling on your own, i mean using some azure or AWS service that can queue tasks and execute the azure function. of course, this is a bit more complex than a traditional server but just mentioning this because if you really want to go serverless then implementing the scheduling on your own is not a bad thing and it definitely worth the tradeoff if you want to have everything serverless. we are just starting to experiment with the serverless use case so maybe in future maybe we can find more out of the box solutions for all the features of jsreport that are tied to a long-running process