最后，我找到了问题。我想知道这是一个错误，还是文献记载不充分。...（或者我只是没有正确解释它。）

Finally, I found the problem. I wonder if this is a bug, or just poorly documented....(or maybe I just didn't interpret it correctly).

根据Leo Lui-MSFT的说法上面的建议（由Microsoft记录），我向NuGet提要添加了权限，但这没有用。但是，我对他的一句话很感兴趣：

As per Leo Lui-MSFT's suggestion above (documented by Microsoft), I'd added the permissions to the NuGet feed, and this didn't work. However, I was intrigued by his sentence:

如果您将构建更改为在项目范围内运行

If you've changed your builds to run at project scope

我个人没有，所以我和系统管理员一起学习了所有可能的设置。最终，我们找到了它-我没有能力进行更改。

Personally, I hadn't, so I got with our System Administrator and we went through all the possible settings. Eventually, we found it - it wasn't something I had the ability to change.

因此，在上面的示例中，BLUE和GREEN是两个试图改变的项目。使用RED的Artifact提要中的NuGet包。

So in my example above, BLUE and GREEN are the two projects that are trying to use the NuGet package in RED's Artifact feed.

因此，选择BLUE（或GREEN），在Azure DevOps的左下角，您将看到一个链接 Project Settings 。在管道>设置下，有四个设置。我们必须将以下内容更改为：

So picking BLUE (or GREEN), in the bottom left hand corner of Azure DevOps you'll see a link "Project Settings". Under "Pipelines > Settings" there are four settings. We had to change the following to be:

将作业授权范围限制为当前项目= false

Limit job authorization scope to current project = false

希望有帮助！