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
2022-05-21T01:18:22.963+00:00

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.
692 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Kumar, Amit 0 Reputation points
    2023-08-24T07:22:46.4033333+00:00

    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
    2024-07-31T17:08:33.2733333+00:00

    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.