Unable to enable Pipelines in one repository — asks for 2FA, but workspace setting is Premium-only

[pepe]

Hi Atlassian team,

I’m having an issue enabling Bitbucket Pipelines for one specific repository.

I’ve enabled Pipelines successfully in other repositories before, but in this repo, when I try to activate it, I get a message saying:

“Two-step verification is required to enable Pipelines.”

The confusing part is that when I check the workspace settings, the two-step verification requirement appears under Access controls, but that option seems to be tied to a Premium feature. So even if I want to enable it from there, I can’t.

A bit more context:

• I already linked Bitbucket to my organization.

• In our organization, we usually authenticate through Google, so we do not normally use Bitbucket 2FA separately.

• This is happening only for one repository. I have been able to enable Pipelines in other repos without this requirement appearing.

So my questions are:

1. Why is this repository specifically requiring two-step verification to enable Pipelines?

2. Is this requirement coming from the repository, workspace, or organization level?

3. If workspace-enforced 2FA is a Premium feature, how are we supposed to satisfy this requirement for Pipelines in a standard setup using Google login?

4. Why did this not happen in other repositories where Pipelines was enabled successfully?

Any guidance would be appreciated. Thanks.

[Ben]

Hi @pepe 

This behaviour reflects a bug that was present as a result of a rollout. This has since been fixed - can you please try again and let me know if you encounter any issues?

Cheers!

- Ben (Bitbucket Cloud Support)

[Prasanna Ravichandran]

Hi,

This looks more like an account-level security requirement for the user enabling Pipelines, rather than something unique to that single repository. Even if workspace-enforced 2FA is a Premium feature, Bitbucket may still require the individual Atlassian account to have two-step verification enabled before allowing a sensitive action like turning on Pipelines. Since other repositories worked earlier, it could be due to a newer security check, a different admin/account context, or that this repo is triggering an additional validation path.