New design related changes

06-Customizing AzTS for your org/Extending AzTS/ManagementGroupBasedComplianceInitiative.md

@@ -1,8 +1,9 @@
 ## Management Group driven Compliance Initiative
-To drive compliance for specific set of controls driven on Mangement Group hierarchy, AzTS provides feature to configure Management Group driven Compliance Initiative.
+To drive compliance for specific set of controls driven on the basis of  Mangement Group hierarchy, AzTS provides feature to configure Management Group driven Compliance Initiative.
 
-This feature is disabled by default. Please follow below steps to enable the same:
+By default, this feature is not turned on. If you haven't enabled it in your AzTS setup yet, please follow the steps below:
 
+## Steps to enable Management Group driven Compliance Initiative feature
 ### **1. Add Required configuration to the API application settings:**
 1. Go to Azure Portal.
 2. Navigate to AzTS host subscription -> AzTS host resource group.
@@ -17,21 +18,21 @@ This feature is disabled by default. Please follow below steps to enable the sam
 
 ![Resources](../../Images/06_MGCI_AddCOnfig_2.png)
 
-8. Add new application setting 'ComplianceInitiativeActionItem__0__PrivilegedEditorIds__0' with value as 'user object id'. Click 'OK'. This step needs to be done per user who needs access to set/update Management Group driven Compliance Initiative.(PrivilegedEditorIds is an array so should beincremented sequentially for further users being added.)
+8. Add new application setting 'ComplianceInitiativeActionItem__0__PrivilegedEditorIds__0' with value as 'user object id'. Click 'OK'. This step needs to be done per user who needs access to set/update Management Group driven Compliance Initiative.(PrivilegedEditorIds is an array so should be incremented sequentially for further users being added.)
 
 ![Resources](../../Images/06_MGCI_AddConfig3.png)
 
 > **Note:** User's object id can be referenced from Azure AD.
 
-9. Add new application setting 'ControlActionItem__0__PrivilegedEditorIds__0'  with value as 'user object id'. Click 'OK'. This step needs to be done per user who needs access to set/update Management Group driven Compliance Initiative(PrivilegedEditorIds is an array so update the array index and add users one by one).
-
+9. Add new application setting 'ControlActionItem__0__PrivilegedEditorIds__0'  with value as 'user object id'. Click 'OK'. This step needs to be done per user who needs access to set/update Management Group driven Compliance Initiative(PrivilegedEditorIds is an array so should be incremented sequentially for further users being added.)
 ![Resources](../../Images/06_MGCI_AddConfig_4.png)
-> **Note:** User's object id can be referenced from Azure AD.
+> **Note:** User's object id can be referenced from Azure AD.This step can be skipped if already completed as part of adding user as Privileged editor for CMET.
 
 10. Add new application setting 'ControlEditorFeatureConfiguration__IsBulkEditEnabled' with value as true. Click 'OK'. 
 
 ![Resources](../../Images/06_MGCI_AddConfig_5.png)
 
+>Note: If you have already enabled [bulk edit feature for CMET](./FeaturesInCMET.md#bulk-edit), you can skip step 11 and 12.
 11. Add new application setting 'FeatureManagement__BulkEdit' with value as true. Click 'OK'.
 
 ![Resources](../../Images/06_MGCI_AddConfig_6.png)
@@ -55,40 +56,47 @@ This feature is disabled by default. Please follow below steps to enable the sam
 5. Click on ‘New application setting’ to add required app settings.
 6. Add new application setting 'FeatureManagement__ManagementGroups' with value as true. Click 'OK'. 
 
-(![Resources](../../Images/06_MGCI_EnableMGTree.png))
+![Resources](../../Images/06_MGCI_EnableMGTree.png)
 
+>Note: Please follow steps 7 and 8 in case of Single tenant AzTS setup. These can be skipped for Multi-Tenant AzTS setup.
 7. Click on 'New application setting' to add required app settings.
 8. Add new application setting 'ManagementGroupConfigurations__ManagementGroupId' with value as parent Management Grroup Id. Click 'OK'. 
 
 9. Add new application setting ‘AuthzSettings__IsPIMEnabled’ with value as true. Click ‘OK’. (This to enable PIM API calls to fetch RBAC details).
 
 10. Click 'OK' and then click 'Save'.
-(![Resources](../../Images/06_MGCIEnableMGAndSave.png))
+![Resources](../../Images/06_MGCIEnableMGAndSave.png)
 
 ### 3.	Add Custom tags to controls (in bulk edit mode) for compliance initiative
-Compliance initiative feature requires common tag on all controls which are part of an initiative. Common tag to a set of controls can be easily added by using CMET bulk edit mode. Please follow the steps mentioned [here](../../06-Customizing%20AzTS%20for%20your%20org/Extending%20AzTS/FeaturesInCMET.md) to add tags to controls.
+Compliance initiative feature requires common tag on all controls which are part of an initiative. Common tag to a set of controls can be added by using CMET bulk edit mode. Please follow the steps mentioned [here](../../06-Customizing%20AzTS%20for%20your%20org/Extending%20AzTS/FeaturesInCMET.md) to add tags to controls.
+
+
+### 4. Create new compliance initiative 
+Please make sure that [Step 1](#1-add-required-configuration-to-the-api-application-settings),[Step 2](#2-add-required-configuration-to-metadata-aggregator-to-enable-mgtreeprocessor-and-pim-api-support) and [Step 3](#3-add-custom-tags-to-controls-in-bulk-edit-mode-for-compliance-initiative) are completed as pre-requisite to create new compliance initiative. Please follow below steps post pre-requisites are completed:
+
+1. Click on the CIMT(Compliance initiative metadata tool) Icon.
+![Resources](../../Images/06_MGCI_CIMT_1.png)
+
+2. Click on 'New Compliance Initiative'.
+![Resources](../../Images/06_MGCI_CIMT_5.png)
 
+3. Fill all the required information. 'Default control tag filter' should be same tag that is added in [step-3](#3-add-custom-tags-to-controls-in-bulk-edit-mode-for-compliance-initiative). Click Save.
+![Resources](../../Images/06_MGCI_CIMT_6.png)
 
-### 4. Create new Compliance initiative and Add compliance initiative to the Mangement Group
-1. Click on the CIMT(Compliance initiative metadata tool) Icon and select the Tenant.
-(![Resources](../../Images/06_MGCI_CIMT_1.png))
 
-2. Select the Root Level MG from the dropdown.
-(![Resources](../../Images/06_MGCI_CIMT_2.png))
+### 5. Add compliance initiative to the Mangement Group
+1. Select the Root Level MG from the dropdown.
+![Resources](../../Images/06_MGCI_CIMT_2.png)
 
-3. Select the MG where you want to configure the Compliance Initiative. Click Apply.
-(![Resources](../../Images/06_MGCI_CIMT_3.png))
+2. Select the MG where you want to configure the Compliance Initiative. Click Apply.
+![Resources](../../Images/06_MGCI_CIMT_3.png)
 
-4. Click on 'New Tag'.
-(![Resources](../../Images/06_MGCI_CIMT_4.png))
+3. Click on 'New Tag' and fill all the required information.
+![Resources](../../Images/06_MGCI_CIMT_7.png)
 
-5. Click on 'New Compliance Initiative'.
-(![Resources](../../Images/06_MGCI_CIMT_5.png))
+4. Click on 'Save'.
 
-6. Fill out all the required information. 'Default control tag filter' should be same tag that is  added in [step-3](#3-add-custom-tags-to-controls-in-bulk-edit-mode-for-compliance-initiative). Click Save.
-(![Resources](../../Images/06_MGCI_CIMT_6.png))
+After completion of above steps, AzTS UI will have additional filter for Management Group. If Management group is selected in this filter and it has a compliance initiative configured for it, then configured compliance initiative would become the default compliance initiative and user would see the compliance summary for only those controls which are part of the configured compliance initiative. 
 
-7. Select the Newly added compliance Initiative and corresponding subscription id (same as custom control tag). Click Save.
-(![Resources](../../Images/06_MGCI_CIMT_7.png))