AADRoleAssignmentScheduleRequest incorrectly thinks if found existing Principal found

[mpoulson]

Description of the issue

Code below assumes the principal was found with one of the 3 attempts. However, there needs to be a check if $PrincipalValue is still null.

Write-Verbose -Message 'Getting Role Eligibility by PrincipalId and RoleDefinitionId'
$PrincipalValue = $null
if ($PrincipalType -eq 'User')
{
Write-Verbose -Message "Retrieving Principal by UserPrincipalName {$Principal}"
$PrincipalInstance = Get-MgUser -Filter "UserPrincipalName eq '$Principal'" -ErrorAction SilentlyContinue
$PrincipalValue = $PrincipalInstance.UserPrincipalName
}
elseif ($null -eq $PrincipalIdValue -and $PrincipalType -eq 'Group')
{
Write-Verbose -Message "Retrieving Principal by DisplayName {$Principal}"
$PrincipalInstance = Get-MgGroup -Filter "DisplayName eq '$Principal'" -ErrorAction SilentlyContinue
$PrincipalValue = $PrincipalInstance.DisplayName
}
else
{
Write-Verbose -Message "Retrieving Principal by DisplayName {$Principal}"
$PrincipalInstance = Get-MgServicePrincipal -Filter "DisplayName eq '$Principal'" -ErrorAction SilentlyContinue
$PrincipalValue = $PrincipalInstance.DisplayName
}

    Write-Verbose -Message 'Found Principal'

Microsoft 365 DSC Version

DEV

Which workloads are affected

Azure Active Directory (Entra ID)

The DSC configuration

Verbose logs showing the problem

Environment Information + PowerShell Version