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
Update-M365DSCAzureAdApplication when used with the -CreateSelfSignedCertificate switch, creates a certificate in the CurrentUser store.
Unfortunately, the other scripts in the module assume certificates specified with -CertificateThumbprint are in the LocalMachine store.
Passing the thumbprint as ..\..\LocalMachine\My\abced... does not work either.
I suggest we change the location of the generated cert to match the expectation and make it easier for new users to correctly authenticate with an app ID and certificate.
Additionally, this should be combined with -certificatePath to export the cert to a file. However, the export is only the public key which cannot be used for authentication. Is the intention here that the export should be a pfx?
The text was updated successfully, but these errors were encountered:
Update-M365DSCAzureAdApplication
when used with the-CreateSelfSignedCertificate
switch, creates a certificate in the CurrentUser store.Unfortunately, the other scripts in the module assume certificates specified with
-CertificateThumbprint
are in the LocalMachine store.Passing the thumbprint as
..\..\LocalMachine\My\abced...
does not work either.I suggest we change the location of the generated cert to match the expectation and make it easier for new users to correctly authenticate with an app ID and certificate.
Additionally, this should be combined with
-certificatePath
to export the cert to a file. However, the export is only the public key which cannot be used for authentication. Is the intention here that the export should be a pfx?The text was updated successfully, but these errors were encountered: