Skip to content

Commit 34b5b00

Browse files
authored
Merge pull request #279871 from ElazarK/WI274814-AWS-onboarding-faq
added new FAQ
2 parents 94e4d12 + 141168f commit 34b5b00

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

articles/defender-for-cloud/faq-general.yml

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ metadata:
77
ms.author: dacurwin
88
manager: raynew
99
ms.topic: faq
10-
ms.date: 05/22/2024
10+
ms.date: 07/03/2024
1111
title: Common questions - General questions
1212
summary: |
1313
@@ -368,6 +368,19 @@ sections:
368368
answer: |
369369
No, if the region or scan interval is changed, there is no need to re-run the CloudFormation template or Cloud Shell script. The changes will be applied automatically.
370370
371+
- question: |
372+
How does onboarding an AWS organization or management account to Microsoft Defender for Cloud work?
373+
answer: |
374+
Onboarding an organization or a management account to Microsoft Defender for Cloud initiates the process of [deploying a StackSet](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-getting-started-create.html). The SteckSet includes the necessary roles and permissions. The StackSet also propagates the required permissions across all accounts within the organization.
375+
376+
The included permissions allow Microsoft Defender for Cloud to deliver the selected security features through the created connector in Defender for Cloud. The permissions also allow Defender for Cloud to continuously monitor all accounts that might be added using the auto-provisioning service.
377+
378+
Defender for Cloud is capable of identifying the creation of new management accounts and can leverage the granted permissions to automatically provision an equivalent member security connector for each member account.
379+
380+
This feature is available for organizational onboarding only and allows Defender for Cloud to create connectors for newly added accounts. The feature also allows Defender for Cloud to edit all member connectors when the management account is edited, delete all member accounts when the management account is deleted, and remove specific member account if the corresponding account is removed.
381+
382+
A separate stack must be deployed specifically for the management account.
383+
371384
additionalContent: |
372385
373386
## Next steps

0 commit comments

Comments
 (0)