Share via

Microsoft Defender For Cloud - error occured for security connector: Failed to create security connector, another security connector with same heirarchyId already exists

Jeevan Reddy 1 Reputation point
May 21, 2022, 1:18 AM

As part of onboarding Microsoft Defender for Cloud-AWS, Was able to create CFN stack successfully in AWS but getting the following error after clicking on the Generate button while setting up Environment for AWS:

{"statusCode":409,"errorMessage":"error occured for security connector: Failed to create security connector, another security connector with same heirarchyId already exists for this native cloud account","errorCorrelation":"94ab46bf-6aed-45b8-9a88-feaba6949358"}

Not sure where to find this conflict/heirarchyId. Any help is much appreciated

Azure Cloud Services
Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
730 questions
{count} votes

2 answers

Sort by: Oldest
  1. Kumar, Amit 0 Reputation points
    Aug 24, 2023, 7:22 AM

    Is there any update on this issue as its been a while? I am having the same issue.

    Please share if someone has found the solution for this.

    Thanks

    0 comments No comments

  2. sarah 0 Reputation points
    Jul 31, 2024, 5:08 PM

    Circling back, I am having this exact same issue in two different azure environments ---- was there ever a resolution? I am assuming at this point that its an MDC back end issue where metadata is not getting erased from the deleted aws account. If I have to Ill submit a ticket, but hoping not to. Thank you all in advance for any input and support!

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.