Skip to content

Commit ba589a3

Browse files
authored
Merge pull request #267907 from AlizaBernstein/WI-216452-update-devops-security-faq
WI-216452-update-devops-security-faq
2 parents 96ea032 + b2160b5 commit ba589a3

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed

articles/defender-for-cloud/faq-defender-for-devops.yml

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,8 +80,13 @@ sections:
8080
- question: |
8181
Why am I not able to see GitHub Advanced Security for Azure Devops (GHAzDO) results in Defender for Cloud?
8282
answer: |
83+
Confirm your connectors is properly [authorized](#why-am-i-getting-an-error-while-trying-to-connect-).
84+
8385
Ensure you are using the same Subscription ID for GHAzDO and Defender for Cloud. If you are still unable to see the results, the issue might be caused by your ADO connector lacking the necessary scope. DevOps security introduced new scopes to Azure DevOps connectors in June. If you created the connector before June and haven't updated it, you won't be able to see GHAzDO results due to missing scope on the connector. You would need to create a new ADO connector, which will automatically include the new scopes.
84-
86+
87+
Ensure the user permissions for the Microsoft Defender for DevOps have `Advanced Security: view alerts` and `Read` set to `Allow`. These permissions may have changed if the "Inheritance" toggle was switched off. If the necessary permissions are set to `Not set` or `Deny`, they will need to be manually updated to `Allow` otherwise the GHAzDO findings will not show up in Defender for Cloud recommendations.
88+
89+
:::image type="content" source="media/faq-defender-for-devops/devops-user-permissions-set.png" alt-text="Screenshot that shows advanced security permissions." lightbox="media/faq-defender-for-devops/devops-user-permissions-set.png":::
8590
- question: |
8691
Is continuous, automatic scanning available?
8792
answer: |
82.3 KB
Loading

0 commit comments

Comments
 (0)