You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/deployment/managed-scanning/azure.md
+4
Original file line number
Diff line number
Diff line change
@@ -96,6 +96,10 @@ The following steps revoke the code access you previously granted Semgrep for al
96
96
2. Find the Azure DevOps entry on the list of **Source code managers** and click **Remove**.
97
97
3. Click **Remove** to confirm.
98
98
99
+
## Troubleshooting: multiple projects
100
+
101
+
If you currently scan Azure DevOps repositories in your CI pipeline, you may see findings assigned to two separate projects once you enable Semgrep Managed Scanning. For example, findings from Managed Scanning go to the `semgrep/frontend/webpage` project, while findings from CI scans go to the `frontend/webpage` project. If this is the case, Semgrep AppSec Platform flags these findings with **Possible duplicate**. Please [contact support](/support) for addition assistance.
0 commit comments