No certificate details in Security and Compliance workload to configure DSC.

[maheshdalavi]

ISSUE TITLE:

• No certificate details in Security and Compliance workload to configure DSC.

ISSUE DESCRIPTION (this template):

• Trying to use CertBased Authentication to configure the DSC for SC workload
• Pulled SC workload components.
• No Details about the Certificate Thumbprint, AppID and Org ID.
• Hence, while loading the Localhost.mof in DSC gives the error.
• Things are fine with Credentials based Auth.

Details of the scenario you tried and the problem that is occurring

• Run the below command.

Export-M365DSCConfiguration -Components @("SCComplianceCase", "SCComplianceSearch") -ApplicationId $ApplicationId -CertificateThumbprint $CertificateThumbprint -TenantId $TenantId -path C:\Microsoft365DSC\SC_CertBased

• OR

Export-M365DSCConfiguration -Workloads SC -Mode full -ApplicationId $ApplicationId -CertificateThumbprint $CertificateThumbprint -TenantId $TenantId -path C:\Microsoft365DSC\SC_CertBased_all

• Check the M365TenantConfig.ps1
• Nodes are missing with App, cert, and Tenant details. ( Config Attached)

SCComplianceTag 45850c48-1356-4191-bdff-d61da7a80c1b
        {
            Comment              = "Office365Securityclassification_Retention_label_policy_autoapply_admins description";
            Ensure               = "Present";
            IsRecordLabel        = $False;
            Name                 = "Office365Securityclassification_Retention_label_policy_autoapply";
            Notes                = "Office365Securityclassification_Retention_label_policy_autoapply_user Description";
            Regulatory           = $False;
            RetentionAction      = "KeepAndDelete";
            RetentionDuration    = "1";
            RetentionType        = "CreationAgeInDays";
            ReviewerEmail        = @("mahesh@$OrganizationName");
        }

• Successfully configured the Localhost.mof
• Tried configuring the DSC node and got the error.

Verbose logs showing the problem

S-1-5-21-2627641904-1758875185-3138976982-1001.                                                                         VERBOSE: [DESKTOP-514K4OO]: LCM:  [ Start  Set      ]                                                                   VERBOSE: [DESKTOP-514K4OO]: LCM:  [ Start  Resource ]  [[SCComplianceSearch]8beea1b1-68a9-4ada-97a0-7e5e8f677d85]       VERBOSE: [DESKTOP-514K4OO]: LCM:  [ Start  Test     ]  [[SCComplianceSearch]8beea1b1-68a9-4ada-97a0-7e5e8f677d85]       VERBOSE: [DESKTOP-514K4OO]:                            [[SCComplianceSearch]8beea1b1-68a9-4ada-97a0-7e5e8f677d85]       Testing configuration of SCComplianceSearch for New content Search
VERBOSE: [DESKTOP-514K4OO]:                            [[SCComplianceSearch]8beea1b1-68a9-4ada-97a0-7e5e8f677d85]
Getting configuration of SCComplianceSearch for New content Search
VERBOSE: [DESKTOP-514K4OO]: LCM:  [ End    Test     ]  [[SCComplianceSearch]8beea1b1-68a9-4ada-97a0-7e5e8f677d85]  in
1.4500 seconds.
PowerShell DSC resource MSFT_SCComplianceSearch  failed to execute Test-TargetResource functionality with error
message: You must specify either the Credential or ApplicationId, TenantId and CertificateThumbprint parameters.
    + CategoryInfo          : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : localhost

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

VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 1.708 seconds

Suggested solution to the issue

The DSC configuration that is used to reproduce the issue (as detailed as possible)

The operating system the target node is running

OsName : Microsoft Windows 11 Home Single Language
OsOperatingSystemSKU : 100
OsArchitecture : 64-bit
WindowsVersion : 2009
WindowsBuildLabEx : 22621.1.amd64fre.ni_release.220506-1250
OsLanguage : en-US
OsMuiLanguages : {en-US, en-GB}-->

Version of the DSC module that was used ('dev' if using current dev branch)

[maheshdalavi]

If i manually add it in the node few or mostly the first node will work and the rest of the nodes will fail with winrm error.
May be IPPSSession get disconnected.