Path length check incorrectly applies Windows 255-char limit on Linux

[PTippner]

Description
The path length check in EntraExporter incorrectly applies a 255-character limit on Linux systems. The code checks for Windows registry key HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled, which doesn't exist on Linux, causing all paths > 255 characters to be skipped.

Affected Files

• Get-AzurePIMResources.ps1 (lines ~278, ~289)
• Get-AzurePIMDirectoryRoles.ps1 (line ~231)
• Get-AzurePIMGroups.ps1 (line ~128)

Code Pattern

if ($outputFileName.Length -gt 255 -and (Get-ItemPropertyValue HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem -Name LongPathsEnabled -ErrorAction SilentlyContinue) -ne 1) 
{Write-Warning "Output file path '$outputFileName' is longer than 255 characters. Enable long path support to continue!"
    return
}

Problem

1. Linux supports path lengths up to ~4096 characters (only individual filename components are limited to 255)
2. The registry check fails silently on Linux, always triggering the warning
3. PIM Resources with long Azure resource paths are skipped entirely

Expected Behavior

• On Linux/macOS: Skip the 255-char check or use OS-appropriate limits
• Consider using shorter filenames (e.g., hash the resource ID instead of full path with & separators)

Environment

• EntraExporter Version: 3.0.1
• OS: Debian Bookworm (Linux)
• PowerShell: 7.x (pwsh)

Example Skipped Path

/home/user/backup/PIM/Resources/Subscriptions/&subscriptions&12345678-1234-1234-1234-11111111111&resourceGroups&rg-examplerg-xy-dev&providers&Microsoft.CognitiveServices&accounts&fd-example-abc-xy-dev&providers&Microsoft.Authorization&roleEligibilityScheduleRequests&1234567-1234-1234-1234-11111111111.json

Suggested Fix

# Check if running on Windows before applying Windows-specific path limit 
$isWindows = $PSVersionTable.PSVersion.Major -ge 6 ? $IsWindows : $true
if ($isWindows -and $outputFileName.Length -gt 255 -and (Get-ItemPropertyValue HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem -Name LongPathsEnabled -ErrorAction SilentlyContinue) -ne 1) {
    Write-Warning "Output file path '$outputFileName' is longer than 255 characters. Enable long path support to continue!"
    return
}

[ztrhgf]

The issue here will still be FileName length. I've fixed 255 limit check to apply only for Windows OS in my https://www.powershellgallery.com/packages/EntraExporterFast/1.0.8, but that won't fix the main issue, unfortunately.

Using a hash instead of a resource path is possible, but I was trying to achieve discoverability when implemented this feature so you can easily view, what resource the JSON was exported for.

I will try to replace the long file name with nested folder hierarchy, so instead of "&subscriptions&12345678-1234-1234-1234-11111111111&resourceGroups&rg-examplerg-xy-dev&providers&Microsoft.CognitiveServices&accounts&fd-example-abc-xy-dev&providers&Microsoft.Authorization&roleEligibilityScheduleRequests&1234567-1234-1234-1234-11111111111.json" file

create:
12345678-1234-1234-1234-11111111111\resourceGroups\rg-examplerg-xy-dev\providers\Microsoft.CognitiveServices\accounts\fd-example-abc-xy-dev\1234567-1234-1234-1234-11111111111.json

[ztrhgf]

OK its implemented in my EntraExporter fork available here https://www.powershellgallery.com/packages/EntraExporterFast/1.0.9-preview4 so you can test it. I've switched my pipeline to linux machine and it seems to be working fine (sort error issue was fixed too).
Resources in the PIM , IAM and AccessPolicy exports are now put into the hierarchy of the folders representing the item scope/id .

If you don't find any issues I will create an PR to official EntraExporter module.

[PTippner]

Thank you very much for your swift response! The issues are fixed :-)

[ztrhgf]

Created PR #113