Pipelines are stuck in queued status after connecting to the Organization to Entra

Question

Pipelines are stuck in queued status after connecting to the Organization to Entra

NAG 0

Pipelines are stuck in queued status after connecting the Organization to Entra. The Pipeline never runs and gets the following error:

##[error]The request: 447 was abandoned due to an infrastructure failure. Notification of assignment to an agent was never received.

We have completed all the suggestions on the support and help page. They still will not run. The pipelines worked fine before connecting to Entra.

Host agent is online and enabled.

Region is Switzerland.

We have free trier 1 parallel job.

We have completed and checked all suggestions:

Make sure you haven't exceeded the parallel job limits.

Make sure your jobs aren't waiting for approval.

Check the agent pools page to see if all your available agents are in use.

Check the Azure DevOps status page to make sure there aren't any ongoing or past incidents in Azure Pipelines.

This error might happen if you've removed the Agent Pool Service (xx) user from Organization Settings > Permissions > Security Service Group. The Agent Pool Service (xx) user is unique for each project. You can also check the auditing logs to see if this user was removed from the group. If the user has been removed, add the user back to the group.

Removed and re-added the users and groups needed from the Pipeline Security and Agent

Anonymous

2025-09-10T21:33:30.63+00:00
@NAG

Thank you for using Q&A Platform

Pipelines stuck in the queued status with the error "The request: 447 was abandoned due to an infrastructure failure. Notification of assignment to an agent was never received" after connecting an organization to Entra (formerly Azure Active Directory) is often caused by an agent pool security issue or a misconfiguration in parallel jobs. The fact that the pipelines worked before the connection strongly suggests that the Entra integration is the root cause, as it can affect how the Agent Pool Service user and its permissions are handled.

Potential Solution Steps

The error message "Notification of assignment to an agent was never received" indicates that the job was queued but could not be assigned to an agent, even though agents appear to be available and online. This is a classic symptom of a permissions issue.

Re-verify the Agent Pool Service User: The most common cause is the removal of the unique Agent Pool Service user from the Project Collection Build Service Accounts group or a similar security group. This user is critical for the pipeline to communicate with the agent pool.

   * Navigate to Organization Settings > Permissions > Security tab.

   * Find the Project Collection Build Service Accounts group.

   * Check if the Agent Pool Service user for your project is a member. The user name is typically in the format [Project Name] Build Service (Organization Name). If it is not present, add it back.

   * Verify that this user has the necessary permissions to use the agent pool, such as "Use" and "Manage" permissions.

Check Service Connection Permissions:

   * Go to Project Settings > Service connections.

   * Select the service connection used by your pipeline.

   * Click on Security.

   * Ensure that the Project Collection Build Service Accounts group and the specific Agent Pool Service user have the necessary permissions (e.g., "User" permission).

Validate Parallel Job Configuration: While you have checked the parallel job limits, the Entra integration can sometimes cause issues with how these are allocated.

   * Go to Organization Settings > Parallel jobs > Organization-level parallel jobs.

   * Confirm that your free tier parallel job is correctly configured and not in an expired or disabled state.

   * Sometimes, after an Entra integration, a new security context might prevent the pipeline from correctly "claiming" a free parallel job. You may need to refresh or re-configure this setting.

Audit Logs: As the error message suggests, check the audit logs for any changes that might have occurred during or after the Entra connection. This can help pinpoint if the Agent Pool Service user or any relevant permissions were inadvertently removed.

   * Navigate to Organization Settings > Audit.

   * Filter the logs for events related to Permissions or Security Groups around the time you connected to Entra.

Re-register the Agent: If the above steps fail, a possible, though less likely, solution is to re-register the agent. This can sometimes resolve communication issues that are not immediately obvious.

   * Unconfigure the agent from the machine.

   * Re-download and re-configure the agent, ensuring the correct security token is used.

The fact that you have a single free parallel job and are in the Switzerland region is less likely to be the direct cause of this specific error, which is clearly pointing to an inability to assign the job to an agent due to a security or communication breakdown. The Entra integration is the most probable trigger for this change in behavior.

I hope this helps in resolving the issue, do let me know if you have any further questions on this
Anonymous

2025-09-11T18:38:00.87+00:00

@NAG Just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.
Anonymous

2025-09-12T16:17:03.6666667+00:00

@NAG Following up to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
NAG 0 Reputation points

2025-09-18T15:52:36.4866667+00:00

Your suggestions don't work. The Pipeline is still stuck.
Anonymous

2025-09-23T07:45:44.93+00:00
@NAG

The pipeline is still stuck acquiring an agent despite all permissions for the Project Collection Build Service account being in place and no audit log clues.

This is a sign of a deeper infrastructure bottleneck or misconfiguration after switching to Entra, or possibly regional capacity issues for Microsoft-hosted agents .

What the Evidence Shows

Parallel Jobs:

Free tier 1 slot is available, and no minutes have been consumed for the current period, confirming quota is not exceeded

Agent Pool:

Pipeline targets the “Azure Pipelines” pool, seeks windows-latest image, but agent cloud does not provide further status and reports, “Pool provider seems slow... still agent has not started” for hours.

Service Account Membership:

The correct Build Service account is present under Project Collection Build Service Accounts, which is necessary for pipeline-agent communication .

Current Theory and Next Steps

Microsoft-hosted Agents Delay:

Microsoft has confirmed that significant regional delays or slowdowns can impact job startup time, even with no quota issues, especially in smaller regions or during maintenance. This can happen independently of your organization’s configuration, leading to extended “Acquiring agent from the cloud...” stalls.

Capacity Constraints in Switzerland:

If other organizations in your region are experiencing the same, support may be needed. Check the Azure DevOps service status dashboard for any region-specific issues. However, absence of public incident reports does not rule out resource pooling bottlenecks behind the scenes.

Agent Pool Health and Trial with Self-hosted Agent:

Self-hosted jobs appear enabled in your organization. To rule out a hosted agent bottleneck, set up a minimal pipeline targeting the self-hosted pool and observe if it starts instantly. This will definitively prove whether the issue is Microsoft-hosted agent capacity-related or an Entra-related pipeline scope loss.

Final Recommendation

Attempt rerunning the problem pipeline but targeting your self-hosted agent (not Microsoft-hosted) as a test.

If the pipeline executes immediately using self-hosted, this confirms a Microsoft-hosted agent pool allocation issue in Switzerland, not a permission or identity bug.

If the self-hosted agent also fails to start jobs, escalate to Microsoft support with evidence of empty quotas, complete service account memberships, and a description of regional behavior.

For persistent Microsoft-hosted queue stalls with all permissions confirmed and no audit log issues, support escalation is recommended citing the “agent not assigned for hours, no infrastructure error in logs, Switzerland region, after Entra ID connection” use case

You can refer the below documents for troubleshooting :

Troubleshoot Managed DevOps Pools issues - Managed DevOps Pools | Microsoft Learn

Microsoft-hosted agents for Azure Pipelines - Azure Pipelines | Microsoft Learn

Troubleshoot pipeline runs - Azure Pipelines | Microsoft Learn

I hope this helps resolving the issue, do let me know if you have any further questions on this
Anonymous

2025-09-24T01:33:15.2666667+00:00

@NAG Just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.
Anonymous

2025-09-26T01:33:56.3166667+00:00

@NAG Following up to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.
Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-09-30T18:58:58.5666667+00:00
Hi NAG,

Thank you for posting your question in the Microsoft Q&A forum

The Agent Pool Service user (unique for each project) may have been removed or lost permissions in Azure DevOps organization after Entra integration.

Agent Pool Service account requires correct permissions in the Project Collection Build Service Accounts or equivalent security groups.

Entra conditional access policies or group mappings may inadvertently block pipeline agents or service accounts from authenticating or running jobs.

Parallel job limits or other job queue resource constraints may come into play as well.

Confirm your hosted or self-hosted agents are online, enabled, and available to pick jobs.

Reference

Create and Manage Agent Pools - Azure Pipelines | Microsoft Learn

Queue jobs stuck in Azure Devops pipelines - Stack Overflow

I hope the provided answer is helpful,

Please "Up Vote" if the information helped you. This will help us and others in the community as well.

Thanks
Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-09-30T19:02:59.8966667+00:00

Hi NAG,

Thanks for reaching out on Microsoft Q&A. Please provide the information requested in the private message so we can look into this further.

Thanks
NAG 0 Reputation points

2025-12-02T10:37:45.8333333+00:00

@Pashikanti Kumar Yes, it is still not working.
NAG 0 Reputation points

2025-12-04T10:55:40.8066667+00:00

When we create an new Project inside the Organization, the pipeline will also not run. Same problem, timeout.
Siddhesh Desai 8,210 Reputation points Microsoft External Staff Moderator

2025-12-30T08:45:24.6833333+00:00

Hi,

I have messaged you in Private conversation, Can you please respond for me to take this issue offline.
Siddhesh Desai 8,210 Reputation points Microsoft External Staff Moderator

2026-01-08T14:23:03.61+00:00

Hi,

Did you get chance to look at my message in Private conversation?

1 answer

Your answer

Anonymous

2025-09-11T18:38:00.87+00:00

@NAG Just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.
Anonymous

2025-09-12T16:17:03.6666667+00:00

@NAG Following up to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
NAG 0 Reputation points

2025-09-18T15:52:36.4866667+00:00

Your suggestions don't work. The Pipeline is still stuck.
Anonymous

2025-09-24T01:33:15.2666667+00:00

@NAG Just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.
Anonymous

2025-09-26T01:33:56.3166667+00:00

@NAG Following up to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.
Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-09-30T18:58:58.5666667+00:00

Hi NAG,

Thank you for posting your question in the Microsoft Q&A forum

The Agent Pool Service user (unique for each project) may have been removed or lost permissions in Azure DevOps organization after Entra integration.

Agent Pool Service account requires correct permissions in the Project Collection Build Service Accounts or equivalent security groups.

Entra conditional access policies or group mappings may inadvertently block pipeline agents or service accounts from authenticating or running jobs.

Parallel job limits or other job queue resource constraints may come into play as well.

Confirm your hosted or self-hosted agents are online, enabled, and available to pick jobs.

Reference

Create and Manage Agent Pools - Azure Pipelines | Microsoft Learn

Queue jobs stuck in Azure Devops pipelines - Stack Overflow

I hope the provided answer is helpful,

Please "Up Vote" if the information helped you. This will help us and others in the community as well.

Thanks
Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-09-30T19:02:59.8966667+00:00

Hi NAG,

Thanks for reaching out on Microsoft Q&A. Please provide the information requested in the private message so we can look into this further.

Thanks
NAG 0 Reputation points

2025-12-02T10:37:45.8333333+00:00

@Pashikanti Kumar Yes, it is still not working.
NAG 0 Reputation points

2025-12-04T10:55:40.8066667+00:00

When we create an new Project inside the Organization, the pipeline will also not run. Same problem, timeout.
Siddhesh Desai 8,210 Reputation points Microsoft External Staff Moderator

2025-12-30T08:45:24.6833333+00:00

Hi,

I have messaged you in Private conversation, Can you please respond for me to take this issue offline.
Siddhesh Desai 8,210 Reputation points Microsoft External Staff Moderator

2026-01-08T14:23:03.61+00:00

Hi,

Did you get chance to look at my message in Private conversation?

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

1 deleted comment

Comments have been turned off. Learn more