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
Exporting Microsoft 365 configuration for Components: SPOHomeSite
Authentication methods specified:
Service Principal with Application Secret
Could not determine authentication method
Partial Export file was saved at: C:\Users\xxxxxx\AppData\Local\Temp\3a5a5c01-c7b8-4da9-a07a-4ec2ff35029e.partial.ps1_
Details of the scenario you tried and the problem that is occurring
Before updating the module to the latest version, I could successfully export selected config using, for example:
Export-M365DSCConfiguration -Components @("AADNamedLocationPolicy") -ApplicationId $ApplicationId -TenantId $TenantId -ApplicationSecret $ApplicationSecret
Now, when I run the exact same cmdlet, the code returns 2 things:
I can run the same cmdlet using -Credential $credential but this was not required before.
Verbose logs showing the problem
A failed run goes as follows:
_PS C:\WINDOWS\system32> Export-M365DSCConfiguration -Components @("SPOHomeSite") -ApplicationId $ApplicationId -TenantId $TenantId -ApplicationSecret $ApplicationSecret
Exporting Microsoft 365 configuration for Components: SPOHomeSite
Authentication methods specified:
Could not determine authentication method
Partial Export file was saved at: C:\Users\xxxxxx\AppData\Local\Temp\3a5a5c01-c7b8-4da9-a07a-4ec2ff35029e.partial.ps1_
A successful run goes as follows:
_PS C:\WINDOWS\system32> Export-M365DSCConfiguration -Components @("AADNamedLocationPolicy") -Credential $credential
Exporting Microsoft 365 configuration for Components: AADNamedLocationPolicy
Authentication methods specified:
Connecting to {MicrosoftGraph}...✅
[1/1] Extracting [AADNamedLocationPolicy] using {Credentials}...
|---[1/5] Rxxxxxx✅
|---[2/5] Sxxxxx]✅
|---[3/5] [Mxxxxxx✅
|---[4/5] [Mxxxxxxxxxxxxx✅
|---[5/5] Test✅
⌛ Export took {26 seconds}
Destination Path:_
Suggested solution to the issue
N/A
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
OsName : Microsoft Windows 10 Enterprise
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture : 64-bit
WindowsVersion : 2009
WindowsBuildLabEx : 19041.1.amd64fre.vb_release.191206-1406
OsLanguage : en-GB
OsMuiLanguages : {en-GB, en-US}
Version of the DSC module that was used ('dev' if using current dev branch)
1.22.1005.1
The text was updated successfully, but these errors were encountered: