diff --git a/.github/renovate.json b/.github/renovate.json
index 414daf8a85..3b30eb7ce0 100644
--- a/.github/renovate.json
+++ b/.github/renovate.json
@@ -3,7 +3,7 @@
   "extends": [
     "config:base"
   ],
-  "enabledManagers": ["npm"],
+  "enabledManagers": ["npm", "nuget"],
   "rangeStrategy": "update-lockfile",
   "rebaseWhen": "conflicted",
   "schedule": [
@@ -15,7 +15,7 @@
       "enabled": false
     },
     {
-      "groupName": "Dependencies",
+      "groupName": "npm dependencies",
       "matchDepTypes": ["dependencies"],
       "matchPackagePatterns":[
         "^@microsoft/fast",
@@ -28,7 +28,7 @@
       "enabled": true
     },
     {
-      "groupName": "Dev Dependencies",
+      "groupName": "npm dev dependencies",
       "matchDepTypes": ["devDependencies"],
       "matchPackagePatterns":[
         "^@ni/eslint-config",
@@ -36,6 +36,11 @@
         "storybook"
       ],
       "enabled": true
+    },
+    {
+      "groupName": "Nuget dependencies",
+      "rangeStrategy": "auto",
+      "enabled": true
     }
   ]
 }
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 263fe16ae7..4f8aed53ac 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -181,7 +181,7 @@ npm install @ni/nimble-tokens --workspace=@ni/nimble-components
 
 This repository uses [Renovate](https://docs.renovatebot.com/) to automatically create pull requests that bump the version of dependencies on a schedule. Renovate is configured via [`renovate.json`](./.github/renovate.json).
 
-Code owners are responsible for completing or rejecting Renovate PRs. Completing a PR may require manually adding a beachball change file to the branch. The change `type` will typically be `patch` if any `package.json` is changing. The `comment` should summarize which set of dependencies are being updated. To complete a PR you may need to manually trigger a rebase by clicking the checkbox in the PR description. **Note:** prefer the checkbox over GitHub's "Update branch" button so that Renovate can remain in control of all commits to its branch.
+Code owners are responsible for completing or rejecting Renovate PRs. Completing a PR may require manually adding a beachball change file to the branch. The change `type` will typically be `patch` if any `package.json` or `.csproj` is changing. The `comment` should summarize which set of dependencies are being updated. To complete a PR you may need to manually trigger a rebase by clicking the checkbox in the PR description. **Note:** prefer the checkbox over GitHub's "Update branch" button so that Renovate can remain in control of all commits to its branch.
 
 ## Handling intermittent test failures