-
Notifications
You must be signed in to change notification settings - Fork 517
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The permissions needed for using application id/certificate authentication on Export-M365DSCConfiguration with Power Platform workload is unknown #1979
Comments
Please follow this article about permissions and authentication methods to determine the needed permissions for power platform. https://microsoft.github.io/Microsoft365DSC/user-guide/get-started/authentication-and-permissions/ If there is something missing, provide more details about the Szenario you are trying to realise. |
The latest M365DSC module returns error with "Certificate Thumbprint" authentication. Will the authentication table be updated ? PS C:\WINDOWS\system32> Export-M365DSCConfiguration -Path $Path -FileName $FileName -ApplicationId $ApplicationId -CertificateThumbprint $CertificateThumbprint -TenantId $TenantId -Workload PP |
Any updates? |
There are various improvements in this PR: #2005 Please have a look at this PR to complete. |
This was also reported in issue #2032. As it turns out, the Planner APIs currently only support credentials authentication. I am working on an update of the Planner resource to fix this issue and to switch to Credentials authentication. This PR will be submitted asap. Currently testing some last items. |
How about Power Platform? What types of authentication is supported? |
That should support Credential, Certificate Thumbprint and Application Secret. |
Please see the result of using certificate thumbprint authentication. PPTenantIsolationSettings cannot be extracted with it. PS C:\WINDOWS\system32> Export-M365DSCConfiguration -Path $Path -FileName $FileName -ApplicationId $ApplicationId -CertificateThumbprint $CertificateThumbprint -TenantId $TenantId -Workload "PP" |
After further investigation, while the PowerApps module accepts ApplicationId/TenantId/Thumbprint/secret, it does not support authenticating with it. Please ensure you connect using Credentials for the Power Platform resources. We will be updating documentation and removing the parameters. |
Details of the scenario you tried and the problem that is occurring
Verbose logs showing the problem
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration here
The operating system the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
The text was updated successfully, but these errors were encountered: