An angry developer desided to remove our build policies on a repository. We've later changed the repository Security for Azure DevOps Groups and Users, so only select users can edit policies.
Despite this, I'm unable to edit the branch policies of this particular repository on two branches. The Policies view is grayed out and Security view shows
Going to Branch Security directly, shows
I have "all" permissions on repository level
What rights are needed to be able to edit policies for this repository?
Had to talk with an organization-wide admin who could re-enable Inheritance for the branches in question, and remove explicit Deny settings.
Once we got in there, it was blocked like this:
After explicit Deny was removed, the branch could inherit repository security.
TL;DR: Always implement principle of least priviledge.