Forum Discussion
Defender for Devops showing deleted connection repositories
Ok so I've made some progress here
elieelkarkafi Its been about a week since I removed my existing Github connector in Defender for devops and all the old repositories were still showing in the inventory blade.
I decided to create a new connector with new naming conventions for the connector and resource group as well as new org in github with no pre-existing authorisation from Defender for cloud. This seems to have initiated a clean up of the existing repos in the Defender for
Devops blade as now I am seeing the new repositories and the old ones have dissapeared.
The old repos are still reporting however in the inventory blade and i guess this will remain in the defender logs for a period of time untill the data is eventually archived or purged (I'm guessing).
Also in Defender for devops under 'defender coverage' shows as having 11 (old) repos when reality is i have only 3 but im also assuming that this will be updated once the initial synchronisation process completes in the console.
Always fun testing out new products in public preview, thanks for your help elieelkarkafi
it’s been over 24 hours now and the devices are still reporting in the inventory list. Also if I create a new connection in defender for cloud to a separate GitHub repository all these old repositories appear in the list even tho they no longer exist. Is there any way these can be removed from defender logs?
I've left it over the weekend and still the same elieelkarkafi I'm running a vs studio enterprise sub so dont have access to technical support. Is there anyway to report this via another channel as a bug or something?
- did the exercise triggered an alert in MDE ?
Ok so I've made some progress here
elieelkarkafi Its been about a week since I removed my existing Github connector in Defender for devops and all the old repositories were still showing in the inventory blade.
I decided to create a new connector with new naming conventions for the connector and resource group as well as new org in github with no pre-existing authorisation from Defender for cloud. This seems to have initiated a clean up of the existing repos in the Defender for
Devops blade as now I am seeing the new repositories and the old ones have dissapeared.
The old repos are still reporting however in the inventory blade and i guess this will remain in the defender logs for a period of time untill the data is eventually archived or purged (I'm guessing).
Also in Defender for devops under 'defender coverage' shows as having 11 (old) repos when reality is i have only 3 but im also assuming that this will be updated once the initial synchronisation process completes in the console.
Always fun testing out new products in public preview, thanks for your help elieelkarkafi