Poweshell script bulk SoD policy: New-V2026SodPolicy Fails Due to Internal Get-DefaultConfiguration Cmdlet Not Recognized

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

Hi Guys,

When attempting to create a new Segregation of Duties (SoD) Policy using the New-V2026SodPolicy cmdlet from the PSSailpoint.V2026 PowerShell module, the cmdlet consistently fails with the error message “The term ‘Get-DefaultConfiguration’ is not recognized.” This occurs despite Set-V2026Configuration reporting success and all external configuration (environment variables/config.json) being correctly provided and recognized. We have experienced this problem across PSSailpoint SDK module versions V2024, V2025, and V2026.

image
image976×139 46.3 KB

Is it an internal failure within the SDK? Does anyone has faced same issue?

Thank you.

2

You haven’t loaded the PSSailPoint PS module. You might have loaded the version-specific PSSailPoint modules (e.g. PSSailPoint.v2025)…but not the base.

image
image1261×178 7.81 KB

If you do a “Get-Command -Module PSSailpoint.v2025”, you’ll see that Get-DefaultConfiguration isn’t part of that .v2025.

1 Like
3

Ah right. That could be the reason. Thank you @David_Norris .