Azure DevOps: Unexpected Queued Geography Migration Without Authorization — Assistance Needed

Question

Problem description

I am experiencing an unexpected queued geography migration in my Azure DevOps organization from United States to United States. All services, including Core Services, Boards, Pipelines, Repos, Test Plans, Artifacts, and others, are listed as queued. I did not initiate or authorize this migration, and I am seeking clarification on the cause and implications.

Environment

Azure DevOps Services organization in the United States.

What I've already tried

I reviewed Azure DevOps documentation regarding organization geography and confirmed that the geography is managed from Organization settings by an organization owner. I also checked the Azure DevOps audit logs for any change events around the time the status changed to queued. Additionally, I have not received any email or in-product notification about this migration.

Current status

Currently, the migration remains queued, and I am seeking assistance to understand why this occurred, whether it can be canceled, and what the expected timeline and impact might be.

Answer 1

Hi @Luís Vieira ,

Thank you for reaching out to Microsoft Q & A !

The United States → United States queued status requires organization-specific investigation. The displayed status alone does not establish what initiated the operation, whether a migration is actually scheduled, or what impact it may have. We should not assume that an organization owner initiated it.

Since you have already reviewed the documentation and checked the audit logs, please open an Azure DevOps Support request using Microsoft’s Get support and provide feedback guidance. [learn.microsoft.com]

Include the following information in the private support request:

• Your Azure DevOps organization URL.
• A screenshot showing the United States → United States queued status and the listed services.
• When you first noticed the status, in UTC, and any displayed request or correlation ID.
• The findings from your audit-log review and whether the organization owner is aware of any geography-change request.
• Whether Boards, Repos, Pipelines, or other services are affected, including exact errors and any blocked production workflows.

Share organization-specific information privately, and exclude credentials, personal access tokens, and other secrets.