-
Notifications
You must be signed in to change notification settings - Fork 532
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
Issue when trying to export all O365 resources #5759
Comments
Running in Visual Studio code (environment), PowerShell Version 5.1 |
Also when trying to authenticate and connect to the Service Principal using Secret rather than Certificate thumbprint, I get this: 'Connecting to {ExchangeOnline}...❌
|
One more update - I hadn't tried to map O365Group previously and this resource DOES seem to work okay with the script above. So the issue is confined to the other O365 resources, i.e. "O365AdminAuditLogConfig", "O365OrgCustomizationSetting", "O365OrgSettings", and "O365SearchAndIntelligenceConfigurations" - these all return the errors detailed above when using the Service Principal and authenticating with either certificate thumbprint or secret. |
Looks like many things are failing, including ExchangeOnlineManagement & Entra ID login w/ Service principal & Cert Thumbprint. Anyway our team is encountering issues as well. |
+1 |
Description of the issue
I am using a certificate thumbprint to authenticate to the service principal. This works for other workloads; however for O365 (all resources) I am consistently getting a message that says 'Failed to Export', e.g.
Failed to
export M365 DSC Configuration for The role assigned to
application xxxxxxxxxx isn't supported in this
scenario. Please check online documentation for assigning correct Directory
Roles to Azure AD Application for EXO App-Only Authentication.
I get this error message for all the O365 resources.
(full error detailed in log below).
Microsoft 365 DSC Version
1.25.205.1
Which workloads are affected
Office 365 Admin
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: