Currently, Azure compute environments in our system are confined to a single pool, meaning jobs are executed solely on instances of the same type.

Supporting multiple pools for Azure compute environments, each possessing the same customization properties currently available for the single pool implementation, would allow users to more flexibly shape their pipeline processes and direct processes to the most appropriate queue for execution. This would provide more versatility and contribute to increased efficiency and resource optimization for pipelines.