Start-DSCConfiguration is returning an error - Custom Application

[JonasCordsen]

Hello

I am trying to test this Solution, but I am getting an error when I try to deploy the new configuration. Do you know if I am missing something in the configuration or if this is a bug?

The Error is as follows

PowerShell DSC resource MSFT_AADGroupsNamingPolicy  failed to execute Set-TargetResource functionality with error message: Der  opstod en eller flere fejl.                                                                                                       + CategoryInfo          : InvalidOperation: (:) [], CimException                                                               + FullyQualifiedErrorId : ProviderOperationExecutionFailure                                                                    + PSComputerName        : localhost                                                                                        



VERBOSE: [DESKTOP-FOSRNEN]: LCM:  [ End    Set      ]
The SendConfigurationApply function did not succeed.
    + CategoryInfo          : NotSpecified: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : MI RESULT 1
    + PSComputerName        : localhost

The following is the Configuration I am trying to deploy:

param(
    [Parameter()]
    [System.String]
    $ApplicationId,

    [Parameter()]
    [System.String]
    $ApplicationSecret,

    [Parameter()]
    [System.String]
    $TenantId
)

Configuration AzureAD
{
    param(
        [Parameter()]
        [System.String]
        $ApplicationId,

        [Parameter()]
        [System.String]
        $ApplicationSecret,

        [Parameter()]
        [System.String]
        $TenantId
    )

    Import-DscResource -ModuleName 'Microsoft365DSC' -ModuleVersion '1.22.720.1'

    Node localhost
    {
        AADGroupsNamingPolicy AzureADGroupNaming
        {
            ApplicationId                 = $ApplicationId;
            ApplicationSecret             = $ApplicationSecret;
            CustomBlockedWordsList        = @();
            Ensure                        = "Present";
            IsSingleInstance              = "Yes";
            PrefixSuffixNamingRequirement = "GRP[GroupName]";
            TenantId                      = $TenantId;
        }
    }
}

$ConfigurationData = @{
    AllNodes = @(
        @{
            NodeName                    = "localhost"
            PSDscAllowPlainTextPassword = $true;
            PSDscAllowDomainUser        = $true;
            #region Parameters
            # Default Value Used to Ensure a Configuration Data File is Generated
            ServerNumber = "0"

        }
    )
}
AzureAD -ConfigurationData $ConfigurationData -ApplicationId $ApplicationId -ApplicationSecret $ApplicationSecret -TenantId $TenantId

[andikrueger]

Could you share the verbose log?

Start-dscconfiguration -usexisting -verbose -wait -force

[JonasCordsen]

Here they are file.log

[JonasCordsen]

I have tested this via pipeline, and here it runs without a issue. Is there a compatibility or some prerquirements that I might need?

I run it on windows 11 Powershell 5

[jackmurphy89]

I am having the same issue on a Windows Server

[ReneRebsdorf]

@andikrueger is this issue still pending information?

[andikrueger]

Yes and no...We do have one report, that it is working and one, that it is not. :) On our end, we are not able to reproduce this issue.

@ReneRebsdorf Are you seeing any error with this resource and what version of M365DSC are you using?

[andikrueger]

Closing due to inactivity.