Conversation in FR: https://teams.microsoft.com/l/message/19:afba3d1545dd45d7b79f34c1821f6055@thread.skype/1731402718890?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=4d73664c-9f2f-450d-82a5-c2f02756606d&parentMessageId=1731402718890&teamName=.NET%20Core%20Eng%20Services%20Partners&channelName=First%20Responders&createdTime=1731402718890

Internal FR conversation: https://teams.microsoft.com/l/message/19:276707cdcf5d431caaa8792b29bd832d@thread.skype/1731431255182?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=147df318-61de-4f04-8f7b-ecd328c256bb&parentMessageId=1731431255182&teamName=.NET%20Eng%20Services&channelName=FR%20Internal&createdTime=1731431255182

Next steps for investigation:

• Looks like this is new VS behavior, we should probably investigate what changed in nuget / VS between what we had and what we deployed
• It doesn't seem to repro for repos that build with arcade, but roslyn's build step seems to be building with VS, not with Arcade, so that might be why we're not seeing it everywhere, is that relevant?
• It's not clear to me why the build step is trying to restore from the internal feeds, since that happened in a previous step of the build.
• I doubt it's service connection related, since the internal restore steps all work, but always worth seeing if they are using a different service connection than the one we expect

Release Note Category

• Feature changes/additions
• Bug fixes
• Internal Infrastructure Improvements

Release Note Description