update to catch up with main

Author: mattbriggs

articles/defender-for-cloud/azure-devops-extension.yml

@@ -117,16 +117,52 @@ procedureSection:
           
           ```
 
-          > [!NOTE]
-          > The artifactName 'CodeAnalysisLogs' is required for integration with Defender for Cloud. For additional tool configuration options, see [the Microsoft Security DevOps wiki](https://github.com/microsoft/security-devops-action/wiki)
+        > [!NOTE]  
+        > The artifactName 'CodeAnalysisLogs' is required for integration with
+        > Defender for Cloud. For additional tool configuration options and environment variables, see
+        > [the Microsoft Security DevOps wiki](https://github.com/microsoft/security-devops-action/wiki)
+
       - |
         To commit the pipeline, select **Save and run**.
 
         The pipeline will run for a few minutes and save the results.
 
         > [!NOTE]
-        > Install the SARIF SAST Scans Tab extension on the Azure DevOps organization in order to ensure that the generated analysis results will be displayed automatically under the Scans tab.
+        > Install the SARIF SAST Scans Tab extension on the Azure DevOps
+        > organization in order to ensure that the generated analysis results
+        > will be displayed automatically under the Scans tab.
 
+  - title: |
+      Uploading findings from third-party security tooling into Defender for Cloud
+    summary: |
+      While Defender for Cloud provides the MSDO CLI for standardized
+      functionality and policy controls across a set of open source security
+      analyzers, you have the flexibility to upload results from other
+      third-party security tooling that you may have configured in CI/CD
+      pipelines to Defender for Cloud for comprehensive code-to-cloud
+      contextualization. All results uploaded to Defender for Cloud must be in
+      standard SARIF format.
+
+      First, ensure your Azure DevOps repositories are
+      [onboarded to Defender for Cloud](quickstart-onboard-devops.md). After
+      you successfully onboard Defender for Cloud, it continuously monitors the
+      'CodeAnalysisLogs' artifact for SARIF output.
+
+      You can use the 'PublishBuildArtifacts@1' task to ensure SARIF output is
+      published to the correct artifact. For example, if a security analyzer
+      outputs 'results.sarif', you can configure the following task in your job
+      to ensure results are uploaded to Defender for Cloud:
+    code: |
+        ```yml
+        - task: PublishBuildArtifacts@1
+          inputs:
+            PathtoPublish: 'results.sarif'
+            ArtifactName: 'CodeAnalysisLogs'
+        ```
+
+        Findings from third-party security tools will appear as 'Azure DevOps
+        repositories should have code scanning findings resolved' assessments
+        associated with the repository the secuirty finding was identified in.
 
 relatedContent:
   - text: Create your first pipeline
@@ -138,4 +174,4 @@ relatedContent:
 
 
 # Learn more about [DevOps Security in Defender for Cloud](defender-for-devops-introduction.md).
-#Learn how to [connect your Azure DevOps Organizations](quickstart-onboard-devops.md) to Defender for Cloud.
+# Learn how to [connect your Azure DevOps Organizations](quickstart-onboard-devops.md) to Defender for Cloud.