updates to PBI template

azsk · Nov 19, 2021 · a6eb864 · a6eb864
1 parent 2a84c49
commit a6eb864
Show file tree

Hide file tree

Showing 11 changed files with 9 additions and 8 deletions.
diff --git a/02-Monitoring security using AzTS/README.md b/02-Monitoring security using AzTS/README.md
@@ -8,7 +8,7 @@
 ## On this page:
 
 - [Tenant Security Solution - under the covers (how it works)](README.md#tenant-security-solution---under-the-covers-how-it-works)
-- [Create cloud security compliance report for your org using PowerBI](README.md#create-security-compliance-monitoring-solutions)
+- [Security Compliance and Inventory Monitoring](README.md#security-compliance-and-inventory-monitoring)
 
 -------------------------
 
@@ -25,7 +25,7 @@ The diagram below depicts a high level overview of the hybrid solution:
 
 [Back to top…](README.md#tenant-security-solution---under-the-covers-how-it-works)
 
-# Create security compliance monitoring solutions
+# Security Compliance and Inventory Monitoring
 Once you have an Tenant Security setup running smoothly with multiple subscriptions across your org, you will need a solution that provides visibility of security compliance for all the subscriptions across your org. This will help you drive compliance/risk governance initiatives for your organization. 
 
 When you setup your Tenant Security endpoint (i.e. policy server), one of the things that happens is creation of an Log Analytics workspace for your setup. After that, whenever someone performs an AzTS scan for a subscription that is configured to use your Tenant Security, the scan results are sent (as 'security' telemetry) to your org's Log Analytics workspace. Because this workspace receives scan events from all such subscriptions, it can be leveraged to generate aggregate security compliance views for your cloud-based environments. 
@@ -54,8 +54,8 @@ The table below describes the different columns in the CSV file and their intent
 
 | ColumnName  | Description | Required?	|Comments|
 | ---- | ---- | ---- | ---- |
-| OrganizationName | Name of Organization(s) within your enterprise | No | This you can consider as level 1 hierarchy for your enterprise |
-| DivisionName | Name of Division(s) within your organization | No | This you can consider as level 2 hierarchy for your enterprise |
+| DivisionName | Name of Division(s) within your enterprise | No | This you can consider as level 1 hierarchy for your enterprise |
+| OrganizationName | Name of Organization(s) within your division | No | This you can consider as level 2 hierarchy for your enterprise |
 | ServiceGroupName | Name of Service Line/ Business Unit within an organization | No | This you can consider as level 3 hierarchy for your enterprise |
 | TeamGroupName | Name of Team(s) within an organization | No | This you can consider as level 4 hierarchy for your enterprise |
 | ServiceName | Name of Service(s) within your organization | No | This you can consider as level 5 hierarchy for your enterprise |
@@ -143,7 +143,8 @@ In Inventory dashboard, 4 tabs are present. Inventory Overview tab shows distrib
 
 ![Update LA Connection String](../Images/13_TSS_OrgPolicy_PBI_OrgMetadata_LA_4.png)
 
-[a4] Repeat this operation for SubscriptionInvLA, SubscriptionComplianceLast7daysLA, BaselineControlsInvLA, ControlResultsLA, ResourceInvInfoLA, and RBACSummaryLA data tables.
+[a4] For compliance dahsbaord, repeat this operation for SubInventory, BaselineControlsInv, ControlResults, ResourceInvInfo,SubscriptionComplianceLast7daysLA and RBACSummaryLA data tables.
+For inventory dashboard, repeat this operation for Assessments, AssessmentsMetadata,AssessmentsMetadataExtended, SubInventory, BaselineControlsInv, ControlResults, ResourceInvInfo, VMExtensionDetails,SubscriptionComplianceLast7daysLA, RBACSummaryLA, ControlScore, SecureSCore, VMCount and VMPowerState data tables.
 
 [a5] Click on "Close and Apply".
 

diff --git a/Images/13_TSS_OrgMappingCSV.png b/Images/13_TSS_OrgMappingCSV.png
diff --git a/Images/13_TSS_PBIDashboardAssessmentsMetadata.png b/Images/13_TSS_PBIDashboardAssessmentsMetadata.png
diff --git a/Images/13_TSS_PBIDashboardComplianceDetails.png b/Images/13_TSS_PBIDashboardComplianceDetails.png
diff --git a/Images/13_TSS_PBIDashboardComplianceSummary.png b/Images/13_TSS_PBIDashboardComplianceSummary.png
diff --git a/Images/13_TSS_PBIDashboardInventoryOverview.png b/Images/13_TSS_PBIDashboardInventoryOverview.png
diff --git a/Images/13_TSS_PBIDashboardSecureScore.png b/Images/13_TSS_PBIDashboardSecureScore.png
diff --git a/Images/13_TSS_PBIDashboardVMExtensions.png b/Images/13_TSS_PBIDashboardVMExtensions.png
diff --git a/TemplateFiles/OrgMapping.csv b/TemplateFiles/OrgMapping.csv
@@ -1,3 +1,3 @@
-OrganizationName,DivisionName,ServiceGroupName,TeamGroupName,ServiceName,SubscriptionId,SubscriptionName
-OrgName1,DivisionName1,ServiceGroupName1,TeamGroupName1,ServiceName1,SubscriptionId1,SubscriptionName1
-OrgName2,DivisionName2,ServiceGroupName2,TeamGroupName2,ServiceName2,SubscriptionId2,SubscriptionName2
+DivisionName,OrganizationName,ServiceGroupName,TeamGroupName,ServiceName,SubscriptionId,SubscriptionName
+DivisionName1,OrgName1,ServiceGroupName1,TeamGroupName1,ServiceName1,SubscriptionId1,SubscriptionName1
+DivisionName2,OrgName2,ServiceGroupName2,TeamGroupName2,ServiceName2,SubscriptionId2,SubscriptionName2
diff --git a/TemplateFiles/TenantSecurityInventoryReport.pbit b/TemplateFiles/TenantSecurityInventoryReport.pbit
diff --git a/TemplateFiles/TenantSecurityReport.pbit b/TemplateFiles/TenantSecurityReport.pbit