Skip to content

Commit d5f2cc8

Browse files
authored
Merge pull request #121455 from felickz/patch-10
Update docs for AzDO onboarding delay
2 parents 793d763 + f95696c commit d5f2cc8

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ To connect your Azure DevOps organization to Defender for Cloud by using a nativ
8787
> [!NOTE]
8888
> To ensure proper functionality of advanced DevOps posture capabilities in Defender for Cloud, only one instance of an Azure DevOps organization can be onboarded to the Azure Tenant you're creating a connector in.
8989
90-
The **DevOps security** blade shows your onboarded repositories grouped by Organization. The **Recommendations** blade shows all security assessments related to Azure DevOps repositories.
90+
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.
9191

9292
## Next steps
9393

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.
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)