Hi Sun, Di ,
I was not able to reproduce this in my tenant. However, if you are not seeing any results for your DevOps organization, I would recommend trying these steps:
- Make sure you don't change artifact name. This can result not seeing the results for your project, even if it is showing up as Connected, as noted here: https://learn.microsoft.com/en-us/azure/defender-for-cloud/faq-defender-for-devops
- Ensure you are using the same Subscription ID for the DevOps organization and Defender for Cloud.
- The Azure DevOps Org and Microsoft Defender for DevOps instance must belong to the same Tenant so ensure that this is the case.
- Verify that you have the correct permissions from the prerequisites:
- Admin privileges in order to enable the Microsoft Security DevOps extension
- Defender for Cloud permissions here (Defender for DevOps specific):
- Azure Account- with permissions to sign into Azure portal
- Contributor role- on the relevant Azure subscription
- Security Administrator role- on the relevant subscription
- OAuth enabled in the Azure DevOps Organization Settings
- The Azure DevOps subscription needs to be in the same tenant as your Azure subscription where you use Microsoft Defender for Cloud.
https://learn.microsoft.com/en-us/azure/defender-for-cloud/faq-defender-for-devops
If you have validated these possibilities but are still not seeing the results, let me know.
If the information helped you, please Accept the answer. This will help us as well as others in the community who may be researching similar questions.