Hello MK/IO Community,

I hope this message finds you well. I have a query regarding the limitations on the number of jobs per single encoding transform within Microsoft Media Services (MK/IO).

In the past, while using Azure Media Services (AMS), there were restrictions on the number of jobs that could be processed per single encoding transform. To address this limitation, users typically created a separate transform for each job and then deleted the transform after successful encoding.

I'm now exploring Microsoft's Media Services (MK/IO) and would like to understand if similar limitations exist within this platform. Specifically, I'm interested in knowing if there are constraints on the number of jobs that can be associated with a single encoding transform and if there are any recommended best practices to optimize job processing efficiency within MK/IO.

Your insights and guidance on this matter would be greatly appreciated. Thank you in advance for your assistance.