Missing menu items under the Pipilines menu of Azure DevOps

Hi @Flow Forge ,

Thank you for reaching out to Microsoft Q & A !

If the missing items are Releases, Task groups, or Deployment groups, check whether classic release pipeline creation is disabled. Microsoft’s states that these navigation items aren't shown when classic pipeline creation is disabled and no corresponding assets exist. That article describes the older combined setting; current documentation lists separate build and release controls.

For Azure DevOps Services, if your organization permits classic releases, ask your administrator to:

1. Open Organization settings → Pipelines → Settings. Check Disable creation of classic release pipelines and, if approved, turn it Off. Confirm the setting remains Off.
2. Open Project settings → Pipelines → Settings and confirm the same setting is Off there too. An organization-level restriction applies to all projects, so changing only the project setting is insufficient when organization-level enforcement is enabled.
3. Refresh the project, expand Pipelines, and check whether the expected menu items appear.

If they remain missing, please share the three labels currently visible and the options you expect, or a screenshot in private message and organization details hidden. If you use Azure DevOps Server, please include its version.​‌

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.

The missing menu items are related to Classic pipeline functionality in Azure DevOps.

Why are these items disabled?

If options such as Releases, Task groups, or Deployment groups are missing under the Pipelines menu, Classic pipeline creation may be disabled at the organization or project level.

Microsoft has been moving customers toward YAML-based pipelines, and for new Azure DevOps organizations/projects, the ability to create Classic pipelines is disabled by default. When Classic pipeline creation is disabled and there are no existing Classic assets that require those options, the corresponding menu items may not be displayed.

Recommended approach

For new implementations, I recommend not relying on the legacy Classic pipeline experience. Instead, use YAML pipelines, particularly multi-stage YAML pipelines, to define your CI/CD process.

With YAML, your pipeline definition is stored alongside your source code and can be version-controlled, reviewed, and managed through your normal development workflow. Microsoft currently recommends starting with YAML for new Azure Pipelines implementations.

For example, a multi-stage YAML pipeline can model a flow such as:

Build → Test → Dev → QA → Production

with conditions, approvals, environments, and deployment jobs defined in YAML.

If you still need the Classic pipeline options

If you have an existing requirement to use Classic pipelines, you can enable the Classic release pipeline functionality.

Please refer to the steps provided in the answer above by Tejaswini Billakurthi, which explain how to check the settings at both the Organization and Project levels.

In particular, check:

Organization Settings → Pipelines → Settings

and

Project Settings → Pipelines → Settings

and verify that Disable creation of classic release pipelines is turned off, if your organization has approved the use of Classic releases. An organization-level restriction can take precedence over the project-level setting.

For new development, however, I would recommend using YAML/multi-stage YAML pipelines rather than introducing new Classic pipelines. Existing Classic pipelines can continue to be used, and Microsoft also provides guidance for migrating Classic pipelines to YAML.

Please "Upvote the Answer" if this information helped you. This helps us and other members of the community as well.