Azure DevOps Connection with an unchangeable ORganization field

[bygones123]

HI,

due to restrictions, I cannot set the ALL_ACCESSIBLE_ORGANIZATIONS for the Organization field, as it is greyed out and disabled for my company setup.

Is there any other way to be able to connect Azure DevOps ? Or is this a hard limitation ?

Thank you

[dosubot[bot]]

Hi @bygones123! I'm Dosu and I’m helping the incubator-devlake team.

This is a hard limitation imposed by your Azure DevOps or company policy, not by DevLake. DevLake requires either a token with access to all organizations or an organization-scoped token with the organization specified. If the Organization field is greyed out and you can't select "All accessible organizations," there isn't a workaround in DevLake to bypass this requirement—it's enforced by Azure DevOps or your admin settings. If neither option is available, connecting Azure DevOps to DevLake isn't possible under these constraints. You may need to contact your Azure DevOps administrator to adjust the policy if you require broader access.
Reference: DevLake Azure DevOps connection docs and code
Reference: DevLake Azure DevOps connection backend code

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[bygones123]

Thank you for the answer. As the restriction will not be lifted by any chance, it seems that DevLake cannot be utilized in our setup.