Cannot Create Release or Edit Classic Release Pipelines Azure DevOps

Question

Cannot Create Release or Edit Classic Release Pipelines Azure DevOps

Britt Tucker 40

I have two accounts in our Azure Devops Org. Both are Project Collection Administrators and Project Administrators on all of the project in the org. I returned from about a week off and now neither account can create a release or edit a classic release pipeline.

Creating a release does nothing. Editing a release pipelines spins endlessly.

the accounts are:

******@axxxxlors.com

******@fxxxxxxxlors.com

I have tried clearing all cache, different browsers, different computers with different operating systems. I also removed xxxxx!******@axxxxxlors.com from the organization, and then rejoined. this didn't help.

Other users in our org with lesser permissions sets have no issue with these features.

This is blocking me from important work, I'd like to get a resolution as soon as possible.

Thanks.

Britt Tucker 40 Reputation points

2026-07-30T18:47:24.0666667+00:00
To help us investigate further, could you please provide the following:

Does the page continue loading indefinitely, or do you see any error message? If you notice any errors in the browser's Developer Tools (Console or Network tab), please share them. answer: It continuously attempts to load it does not time out and it does not produce an error.

What is your Azure DevOps organization URL? answer: sent in private message

Does the issue occur only with Classic Release pipelines, or are you seeing the same behavior when creating or editing Build or YAML pipelines? answer: only classic release pipelines

Please share the approximate UTC time when you most recently reproduced the issue.1. 6:40PM UTC (its occurring as I type this post.)
Liam Murphy 0 Reputation points

2026-08-02T22:02:34.7333333+00:00

Getting exactly the same issue. Since last week release pipelines were periodically unavailable; now unable to select existing releases or create new releases across multiple projects and using different user accounts. Selecting an exsting release just shows the spinner; trying to create a new release navigtates to the release page but it remains blank with the spinner. Network trace shows no Release Management API requests being made after page load, only a 204 response from / _apis/customerintelligence/Events. Browser console reports:

Uncaught TypeError: define(...) is not a function

Have logged out, logged in, restarted computer, cleared browser caches, run in private mode...same results.
Sridevi Machavarapu 33,740 Reputation points Microsoft External Staff Moderator

2026-08-03T01:28:50.7133333+00:00

Hello Liam Murphy,

Currently, we are looking into this internally and get back to you soon once we get further update on this.

Answer accepted by question author

Sridevi Machavarapu 33,740 Microsoft External Staff Moderator

Hello Britt Tucker,

Thank you for your patience and for working with us while we investigated this issue.

Based on our findings, we identified that the Azure DevOps organization was still using the legacy URL configuration. The organization was updated to use the current Azure DevOps URL configuration. This change is safe because legacy Azure DevOps URLs are automatically redirected to the current URL.

After the update, the Classic Release Pipelines that were previously experiencing intermittent loading issues opened successfully, and additional release pipelines also loaded as expected. Since then, you've confirmed that the issue is no longer occurring and that the case can be closed.

While we cannot definitively confirm that the legacy URL configuration was the root cause, the behavior has remained stable after the update.

Thank you again for your cooperation throughout the investigation. If you experience the issue again or have any other questions, please feel free to start a new thread.

0 comments

2 additional answers

Your answer

Britt Tucker 40 Reputation points

2026-07-30T18:47:24.0666667+00:00

To help us investigate further, could you please provide the following:

Does the page continue loading indefinitely, or do you see any error message? If you notice any errors in the browser's Developer Tools (Console or Network tab), please share them. answer: It continuously attempts to load it does not time out and it does not produce an error.

What is your Azure DevOps organization URL? answer: sent in private message

Does the issue occur only with Classic Release pipelines, or are you seeing the same behavior when creating or editing Build or YAML pipelines? answer: only classic release pipelines

Please share the approximate UTC time when you most recently reproduced the issue.1. 6:40PM UTC (its occurring as I type this post.)
Liam Murphy 0 Reputation points

2026-08-02T22:02:34.7333333+00:00

Getting exactly the same issue. Since last week release pipelines were periodically unavailable; now unable to select existing releases or create new releases across multiple projects and using different user accounts. Selecting an exsting release just shows the spinner; trying to create a new release navigtates to the release page but it remains blank with the spinner. Network trace shows no Release Management API requests being made after page load, only a 204 response from / _apis/customerintelligence/Events. Browser console reports:

Uncaught TypeError: define(...) is not a function

Have logged out, logged in, restarted computer, cleared browser caches, run in private mode...same results.
Sridevi Machavarapu 33,740 Reputation points Microsoft External Staff Moderator

2026-08-03T01:28:50.7133333+00:00

Hello Liam Murphy,

Currently, we are looking into this internally and get back to you soon once we get further update on this.

Answer 1

Marcin Policht 104.3K MVP Volunteer Moderator

Try turning off and on Disable creation of classic build pipelines and Disable creation of classic release pipelines.

More at https://learn.microsoft.com/en-us/azure/devops/pipelines/security/approach?view=azure-devops

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Britt Tucker 40 Reputation points

2026-07-30T16:48:06.2+00:00

Neither of those settings are enabled at the project or org level. other users have no issue creating releases or editing pipelines.

I
Britt Tucker 40 Reputation points

2026-07-30T16:51:27.1366667+00:00

these settings are disabled and never have been enabled in this organization. other users can perform these tasks without issue.
Sreetheja Adusumilli 965 Reputation points Microsoft External Staff Moderator

2026-08-03T03:07:41.31+00:00

Hello @Britt Tucker ,

We sincerely apologize to hear that the issue has not yet been resolved. Your satisfaction is important to us, and we are committed to working with you toward a resolution. Please share your email ID, feasible time to connect in Private Message.
Ben Weslake 5 Reputation points

2026-08-11T03:50:59.27+00:00

Toggling those settings from disabled -> enabled -> disabled, resolved the issue for me. I also checked our Organisation setting for "Use the new URL:..." as commented below and ours is currently disabled.

Answer 2

Britt Tucker 40

my organization was set to use the legacy url (xxx.visualstudio.com) I was using the dev.azure.com/xxxx from my client.

Once I set the org to use the new URL, my problems went away.

User's image

0 comments