PurviewConfigAnalyser

Author(s)

• Abhijeet Karki

Tags

Purview Compliance Microsoft365 Security Assessment DLP SensitivityLabels Governance

Functions

Test-PurviewCompliance Invoke-PurviewConfigAnalyser Get-PurviewConfig New-CustomControlBook

Dependencies

• • ImportExcel (>= 7.0.0)

Release Notes

# PurviewConfigAnalyser v1.0.8

## New in v1.0.8 - VERSION-SPECIFIC OUTPUT DIRECTORIES
- [CRITICAL FIX] Fixed output directory structure for multiple module versions
- [FIX] Output directories are now version-specific within each installed module version
- [FIX] Data collection and file lookups now use consistent ../output paths within each version
- [FIX] Prevents conflicts between multiple installed versions (1.0.0, 1.0.6, 1.0.7, etc.)
- [FIX] Each module version maintains its own output folder structure
- [FIX] Resolves issues where older versions were being referenced due to module loading order
- [IMPROVEMENT] Users no longer need to uninstall previous versions before installing new ones
- Module versions now properly isolated and self-contained

## New in v1.0.7 - OUTPUT PATH CONSISTENCY FIX
- [CRITICAL FIX] Fixed output directory path inconsistency between data collection and file lookup
- [FIX] Data collection creates files at module root level (..\output) but lookups were using version-specific path
- [FIX] Aligned all output path references to use module root level consistently (..\..\output from Public folder)  
- [FIX] Resolves "Cannot find path output" error after successful data collection
- [FIX] Files are now correctly found after being created by data collection process
- Module now works correctly for both data collection and subsequent file lookups

## New in v1.0.6 - USER-FRIENDLY VALIDATION
- [CRITICAL FIX] Fixed validation workflow for installed modules without output directory
- [IMPROVEMENT] Interactive prompt for OptimizedReport JSON file when validation tests are run
- [UX] Clear instructions on how to obtain OptimizedReport JSON files
- [FIX] Graceful handling of missing output directory in Run-MaturityAssessment script
- [FIX] Added automatic output directory creation when needed
- [FIX] Better error handling for file path validation
- Validation tests now work seamlessly for installed modules

## New in v1.0.5 - CRITICAL PATH FIX
- [CRITICAL FIX] Fixed config file path resolution for installed modules
- [FIX] Corrected PSScriptRoot path calculations from "../../config" to "../config"
- [FIX] Fixed config lookup in Invoke-PurviewConfigAnalyser, Test-PurviewCompliance, and all scripts
- [FIX] Module now properly finds config files at correct installed location
- [FIX] Resolves "Cannot find path config" error in PowerShell Gallery installations
- Module paths now work correctly for both development and installed environments

## New in v1.0.4 - CONFIG FILES INCLUDED
- [CRITICAL FIX] Added missing config files to PowerShell Gallery package
- [INCLUDE] ControlBook_AUGov_Config.csv - Australian Government compliance framework
- [INCLUDE] ControlBook_Property_AUGov_Config.csv - Property mappings for AUGov framework  
- [INCLUDE] Master control books for reference configurations
- [FIX] Resolves "Cannot find path config" error during validation step
- Module now fully functional with all required configuration files

## New in v1.0.3
- [CRITICAL FIX] Fixed all remaining Unicode quote character issues that caused parser errors
- [FIX] Replaced smart quotes (U+2018, U+2019, U+201C, U+201D) with standard ASCII quotes
- [FIX] Fixed "Array index expression missing" errors in string literals
- [FIX] Fixed "Missing argument in parameter list" errors from malformed quotes
- Module now imports successfully without any syntax errors - FINAL FIX

## Features
- Comprehensive compliance assessment for Microsoft Purview configurations
- Support for Sensitivity Labels, Auto-labeling, and DLP policies
- Advanced parsing for complex nested policy structures
- Excel and CSV reporting capabilities
- 96.3% compliance rate achieved on reference implementation

## Technical Capabilities
- Deep recursive JSON parsing for complex policy conditions
- Case-insensitive property matching
- Support for compound property paths with >> operator
- Enhanced DLP rule parsing for nested SubConditions
- Automated control book validation
- Universal PowerShell environment compatibility

## Requirements
- PowerShell 5.1 or higher
- ImportExcel module 7.0.0 or higher
- Microsoft Purview OptimizedReport JSON export

## Usage
Import-Module PurviewConfigAnalyser
Test-PurviewCompliance -OptimizedReportPath "report.json" -Configuration "AUGov" -OutputPath ".\results"