Skip to content

Commit f95696c

Browse files
felickzElazarK
andauthored
Update articles/defender-for-cloud/quickstart-onboard-github.md
Co-authored-by: Elazar Krieger <[email protected]>
1 parent a0a467d commit f95696c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/defender-for-cloud/quickstart-onboard-github.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ The Defender for Cloud service automatically discovers the organizations where y
9090
> [!NOTE]
9191
> To ensure proper functionality of advanced DevOps posture capabilities in Defender for Cloud, only one instance of a GitHub organization can be onboarded to the Azure Tenant you are creating a connector in.
9292
93-
The **DevOps security** pane shows your onboarded repositories grouped by Organization. The **Recommendations** pane shows all security assessments related to GitHub repositories. The onboarding may take up to 8 hours to show the initial DevOps security results.
93+
Upon successful onboarding, DevOps resources (e.g., repositories, builds) will be present within the Inventory and DevOps security pages. It may take up to 8 hours for resources to appear. Security scanning recommendations may require [an additional step to configure your pipelines](azure-devops-extension.md). Refresh intervals for security findings vary by recommendation and details can be found on the Recommendations page.
9494

9595
## Next steps
9696

0 commit comments

Comments
 (0)