You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error during export in SCComplianceSearch in reference to missing credentials but Certificate Thumbprint was used. A call to Get-TargetResource on line 561 of MSFT_SCComplianceSearch.psm1 appears to be using an incomplete parameter array.
Microsoft 365 DSC Version
1.23.719.1
Workload
Azure Active Directory
Exchange Online
Office 365 Admin
OneDrive for Business
Planner
Power Platform
Security & Compliance Center
SharePoint Online
Teams
other
The DSC configuration
Extracting [SCComplianceSearch] using {CertificateThumbprint}
[1/20] Searches assigned to case ...
Verbose logs showing the problem
{OperationStopped}
System.Management.Automation.RuntimeException: You must specify either the Credential or ApplicationId, TenantId and CertificateThumbprint parameters.
"Error during Export:"
at New-M365DSCConnection, C:...\WindowsPowerShell\Modules\Microsoft365DSC\1.23.719.1\modules\M365DSCUtil.psm1: line 1732
at Get-TargetResource, C:...\WindowsPowerShell\Modules\Microsoft365DSC\1.23.719.1\DSCResources\MSFT_SCComplianceSearch\MSFT_SCComplianceSearch.psm1: line 92
at Export-TargetResource, C:...\WindowsPowerShell\Modules\Microsoft365DSC\1.23.719.1\DSCResources\MSFT_SCComplianceSearch\MSFT_SCComplianceSearch.psm1: line 561
at Start-M365DSCConfigurationExtract, C:...\WindowsPowerShell\Modules\Microsoft365DSC\1.23.719.1\modules\M365DSCReverse.psm1: line 620
at Export-M365DSCConfiguration, C:...\WindowsPowerShell\Modules\Microsoft365DSC\1.23.719.1\modules\M365DSCUtil.psm1: line 1310
at , C:...\GetConfigs-SecComp.ps1: line 31
Environment Information + PowerShell Version
OsName : Microsoft Windows 10 Enterprise
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture : 64-bit
WindowsVersion : 2009
WindowsBuildLabEx : 19041.1.amd64fre.vb_release.191206-1406
OsLanguage : en-US
OsMuiLanguages : {en-US}
Key : PSVersion
Value : 5.1.19041.3031
Name : PSVersion
Key : PSEdition
Value : Desktop
Name : PSEdition
Key : PSCompatibleVersions
Value : {1.0,2.0,3.0,4.0...}
Name : PSCompatibleVersions
Key : BuildVersion
Value : 10.0.19041.3031
Name : BuildVersion
Key : CLRVersion
Value : 4.0.30319.42000
Name : CLRVersion
Key : WSManStackVersion
Value : 3.0
Name : WSManStackVersion
Key : PSRemotingProtocolVersion
Value : 2.3
Name : PSRemotingProtocolVersion
Key : SerializationVersion
Value : 1.1.0.1
Name : SerializationVersion
The text was updated successfully, but these errors were encountered:
Description of the issue
Error during export in SCComplianceSearch in reference to missing credentials but Certificate Thumbprint was used. A call to Get-TargetResource on line 561 of MSFT_SCComplianceSearch.psm1 appears to be using an incomplete parameter array.
Microsoft 365 DSC Version
1.23.719.1
Workload
The DSC configuration
Extracting [SCComplianceSearch] using {CertificateThumbprint}
[1/20] Searches assigned to case ...
Verbose logs showing the problem
{OperationStopped}
System.Management.Automation.RuntimeException: You must specify either the Credential or ApplicationId, TenantId and CertificateThumbprint parameters.
"Error during Export:"
at New-M365DSCConnection, C:...\WindowsPowerShell\Modules\Microsoft365DSC\1.23.719.1\modules\M365DSCUtil.psm1: line 1732
at Get-TargetResource, C:...\WindowsPowerShell\Modules\Microsoft365DSC\1.23.719.1\DSCResources\MSFT_SCComplianceSearch\MSFT_SCComplianceSearch.psm1: line 92
at Export-TargetResource, C:...\WindowsPowerShell\Modules\Microsoft365DSC\1.23.719.1\DSCResources\MSFT_SCComplianceSearch\MSFT_SCComplianceSearch.psm1: line 561
at Start-M365DSCConfigurationExtract, C:...\WindowsPowerShell\Modules\Microsoft365DSC\1.23.719.1\modules\M365DSCReverse.psm1: line 620
at Export-M365DSCConfiguration, C:...\WindowsPowerShell\Modules\Microsoft365DSC\1.23.719.1\modules\M365DSCUtil.psm1: line 1310
at , C:...\GetConfigs-SecComp.ps1: line 31
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: