## The problem
Issue dependabot/dependabot-core#11525 (closed, 44 comments): ### Is there an existing issue for this? - [x] I have searched the existing issues ### Package ecosystem nuget ### Package manager version _No response_ ### Language version _No response_ ### Manifest location and content before the Dependabot update Our repos have multiple csproj files (under various subfolders like src/ and test/) and Directory.Build.props at the root ### dependabot.

## What to do
If Dependabot ignores your custom NuGet feed and falls back to nuget.org, check the casing of your NuGet config filename. NuGet only recognizes exactly 'nuget.config', 'NuGet.config', or 'NuGet.Config'; variants like 'Nuget.config' are silently not found, and NuGet falls back to the default api.nuget.org feed. Rename the file to one of the three allowed casings. (Separately, NU1507 warnings can be suppressed with a NoWarn entry; the updater-side fix went out via dependabot-core PR #11718.)