We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Export-M365DSCConfiguration -Components @("EXOPlace", "TeamsEmergencyCallRoutingPolicy") -ApplicationId $AppId -TenantId $Tenant -CertificateThumbprint $thumbprint -Path $localPath *>$1 | out-null
New-M365DSCDeltaReport -Source "$localPath\GoldM365TenantConfig.ps1" -Destination "$localPath\M365TenantConfig.ps1" -OutputPath $driftFileName
V1.24.626.1
Teams, Exchange Online
The parsing happens both onPrem and Azure Runbook
See screenshot
see screenshot
The text was updated successfully, but these errors were encountered:
Run the below in a prompt as admin
winrm quickconfig -force
Sorry, something went wrong.
@ricmestre would it work in Azure Automation runbook?
No branches or pull requests
Description of the issue
Export-M365DSCConfiguration -Components @("EXOPlace", "TeamsEmergencyCallRoutingPolicy") -ApplicationId $AppId -TenantId $Tenant -CertificateThumbprint $thumbprint -Path $localPath *>$1 | out-null
New-M365DSCDeltaReport -Source "$localPath\GoldM365TenantConfig.ps1" -Destination "$localPath\M365TenantConfig.ps1" -OutputPath $driftFileName
Microsoft 365 DSC Version
V1.24.626.1
Which workloads are affected
Teams, Exchange Online
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: