Skip to content

Commit b2160b5

Browse files
authored
Acrolinx
1 parent 9486481 commit b2160b5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ sections:
8484
8585
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.
8686
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 is 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.
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.
8888
8989
:::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":::
9090
- question: |

0 commit comments

Comments
 (0)