In previous versions when D365 was called Dynamics AX and on prem we had the ability when architecting the solution to have user, batch, and integration AOS'. This allowed us to separate out specific workloads to not only ensure performance but also reliability (such as a user process not crashing an AOS that runs integrations).

We would like to see Microsoft add the ability to dedicate AOS' for integrations so that we can ensure that business critical integrations are not impacted by user or batch processes that are not performant or crash a system. This would also allow us to ensure that integrations that have high resource needs are not impacting user interactions and batch processes on the AOS (acknowledging that there is still SQL impact that is not addressed by this enhancement). Note that while the priority based batch feature is helpful in certain circumstances it does not address all scenarios.

I suspect this would come with a need to license this type of AOS and accept that (in 2012 and previous versions we would get additional aos licenses to handle the batch and/or integration load).