Working with @akinm we realized that the wrong project key was being used – the result of having two repositories in separate Azure DevOps projects (in the same organization) with the same name. Once the right project key was used, the issue was resolved.