Reputation: 2263
We're working in a shared repository where we're not the owner. Our AAD accounts have been invited - [email protected]. We have no issues accessing the Git repo.
THE ISSUE: We can't access the NuGet repo. We can access it in ADO and see all the artifacts. However, when we try to pull the repo in VS, we get a 401 Unauthorized.
The workaround is to use a personal Microsoft Account (MSA). That's understandably not a good idea - it's customer work.
THE QUESTION: Is ADO's NuGet feature only supported by MSA and not AAD accounts when the invited AAD account isn't part of the owner organization? Is this a hard limit?
Thanks!
Upvotes: 2
Views: 176
Reputation: 18556
Authentication with Azure Artifacts can be a bit of a pain... but it works (even with guest AAD accounts). I am using it like this every day. If you can download the file from the feed via the UI, you will also be able to download it via VisualStudio or other tools.
VisualStudio should have no issue at all when talking to the feed, at least if it is a somewhat current version. For VSCode and others you should try the Azure Artifacts Credential Provider and run something along these lines: dotnet restore --interactive
Upvotes: 0