Microsoft365DSC: Cannot bind parameter 'Certificate'. Cannot convert value "CERTIFICATETHUMBPRINT" to type "Microsoft.TeamsCmdlets.Powershell.Connect.Utilities.CertificateParameter". about microsoft365dsc HOT 6 CLOSED

The certificate must be installed in the LOCALMACHINE store, not on MY (your user account).

from microsoft365dsc.

The certificate must be installed in the LOCALMACHINE store, not on MY (your user account).

I have installed the Certificate under Localmachine:

from microsoft365dsc.

There's definitely a problem with that certificate, I can't see the key in the icon so the private key was either not imported or cannot be read for some reason.

from microsoft365dsc.

There's definitely a problem with that certificate, I can't see the key in the icon so the private key was either not imported or cannot be read for some reason.

Then I will provide you with more informations:
Error:

ConfigurationData.ps1:

localhost.mof:

Certificate with Thumbprint:

I can export the settings with the existing certificate, but the import does not work.

from microsoft365dsc.

Problem solved after creating a new certificate. Thanks for your help.

from microsoft365dsc.

@mheAC - I am facing similar issue for same TeamsAppPermisionPolicy. But my issue during Test-TargetResource is that - it is timing out. It seems to be that during Connect-MicrosoftTeams under MSFT_TeamsAppPermisionPolicy.psm1.
However, just few lines above, I am doing an export command (as a sample to make sure connection is good )-that succeeds. Immediately after that, I am doing start-dsconfiguration against a MOF file. It keeps on timing out in the same PS session.
Just suspecting if my cert info is not getting passed on properly ? But all that is Microsoft code.
But if I specifically do connect-MicrosoftTeams with a cert thumbprint, that works in the same window. Only it timesout while running Start-DSCConfiguration.

Any suggestion on this, be appreciated.

Authentication methods specified:

• Service Principal with Certificate Thumbprint

Connecting to {MicrosoftTeams}...✅
[1/1] Extracting [TeamsUpgradeConfiguration] using {CertificateThumbprint}...✅
⌛ Export took {3 seconds} for {1 instances}
VERBOSE: removing the temporary extract from C:\Windows\Temp\Test-Teams\output\temp
VERBOSE: Applying configuration to the tenant bloombergcorpdev.onmicrosoft.com for component TeamsAppPermissionPolicy at :
C:\Windows\Temp\Test-Teams\Output\MOFFiles\TEAMS\dev\TeamsAppPermissionPolicy
VERBOSE: ...temporarily connecting to teams.....
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' =
MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer E07EFB576A09 with user sid S-1-5-93-2-1.
VERBOSE: [E07EFB576A09]: LCM: [ Start Set ]
VERBOSE: [E07EFB576A09]: LCM: [ Start Resource ] [[TeamsAppPermissionPolicy]TeamsAppPermissionPolicy-New Test app perm - dsc
23112::[BB_TeamsAppPermissionPolicy]AppPermPol]
VERBOSE: [E07EFB576A09]: LCM: [ Start Test ] [[TeamsAppPermissionPolicy]TeamsAppPermissionPolicy-New Test app perm - dsc
23112::[BB_TeamsAppPermissionPolicy]AppPermPol]
VERBOSE: [E07EFB576A09]: [[TeamsAppPermissionPolicy]TeamsAppPermissionPolicy-New Test app perm - dsc
23112::[BB_TeamsAppPermissionPolicy]AppPermPol] Testing configuration of {New Test app perm - dsc 23112}
One or more errors occurred.
+ CategoryInfo : AuthenticationError: (:) [], CimException
+ FullyQualifiedErrorId : Connect-MicrosoftTeams,Microsoft.TeamsCmdlets.Powershell.Connect.ConnectMicrosoftTeams
+ PSComputerName : localhost

from microsoft365dsc.