An Azure Pipelines build job for App1 runs on a Microsoft-hosted Windows agent and intermittently times out. To ensure the build completes while minimizing administrative effort, what should you do?

Purchasing more parallel jobs increases the number of concurrent pipelines your organization can run, which can reduce queue times and indirectly help with intermittent timeouts if the timeouts are due to agents being oversubscribed or slow to become available. It doesn't directly solve a timeout within a single job execution but ensures that jobs start promptly, preventing delays that might contribute to perceived timeouts. Changing the configuration of the build agent is not possible with Microsoft-hosted agents beyond selecting the image. Deploying a self-hosted agent would require significant administrative effort for maintenance and updates, which the question aims to minimize. Changing to a Microsoft-hosted Linux agent might change performance characteristics but doesn't guarantee a resolution to timeouts and doesn't address the core issue of potential resource contention or pipeline queuing.