Teams Export is failing

[NaveenRamakrish]

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

[NaveenRamakrish]

Module Version: 1.23.517.1

[NikCharlebois]

We would need additional details here. Can you share the error in the log? Also, are you using Credentials to authenticate or a Service Principal? Thanks

[NaveenRamakrish]

We would need additional details here. Can you share the error in the log? Also, are you using Credentials to authenticate or a Service Principal? Thanks

I am using credentials, Attaching the error logs
LogFile_09June2023.log

[NikCharlebois]

Looks like a licensing issue. Can you try the following and post the output?

$creds = Get-Credential -Message "Your credentials"
Connect-M365Tenant -Credential $creds -Workload SecurityComplianceCenter

Get-Command 'Get-AuditConfigurationPolicy'

Thanks

[NaveenRamakrish]

$creds = Get-Credential -Message "Your credentials"
Connect-M365Tenant -Credential $creds -Workload SecurityComplianceCenter

Get-Command 'Get-AuditConfigurationPolicy'

Below is the result.

[NikCharlebois]

Definitively looks like a licensing issue. What roles/licenses is the user you are connecting with assigned? Thanks

[NaveenRamakrish]

Definitively looks like a licensing issue. What roles/licenses is the user you are connecting with assigned? Thanks

It has Global Reader Permission, I am using this module for the last 5 months and everything was working fine. It stopped working after May 18th, 2023.

Can you let me know what has changed and what changes need to be done on our end?

-Naveen

[NikCharlebois]

Nothing has changed in the underlying module for the past 2 months. The error is not coming from M365DSC but from its underlying Exchange Online Management PowerShell module. The only other recommendation I would have would be for you to run Update-M365DSCModule and make sure you only have 1 instance of the ExchangeOnlineManagement module installed on the machine, or try the tool from another machine to see if you get different results.

[NaveenRamakrish]

Nothing has changed in the underlying module for the past 2 months. The error is not coming from M365DSC but from its underlying Exchange Online Management PowerShell module. The only other recommendation I would have would be for you to run Update-M365DSCModule and make sure you only have 1 instance of the ExchangeOnlineManagement module installed on the machine, or try the tool from another machine to see if you get different results.

I understand, But the issue is only with Teams Services, the remaining services are getting exported without any issues. And in Teams Service I do see some components are getting exported without any issues and stop in the mid and not proceeding.

-Naveen

[NikCharlebois]

Got it, sorry I was looking at the wrong entry in the error log. Let's dive into the authentication stack here. Can you try the following two set of commands, each in separate PowerShell consoles and let me know if you get any errors?

#1

$creds = get-Credential
Connect-M365Tenant -Workload MicrosoftTeams -Credential $creds
Get-CsTeamsAppPermissionPolicy

#2

$creds = get-Credential
Connect-MicrosoftTeams -Credential $Creds
Get-CsTeamsAppPermissionPolicy

[NaveenRamakrish]

```powershell
$creds = get-Credential
Connect-M365Tenant -Workload MicrosoftTeams -Credential $creds
Get-CsTeamsAppPermissionPolicy

#2

$creds = get-Credential
Connect-MicrosoftTeams -Credential $Creds
Get-CsTeamsAppPermissionPolicy

I didnt get any error, I was able to execute the command successfully. When I execute any export configuration command it gives the errors mentioned in the screenshot.

Export-M365DSCConfiguration -ConfigurationName SPOTenantSettings -Credential $Credential -FileName C:\temp\SPO_Test.ps1 -Verbose

[NaveenRamakrish]

Please close this issue, Issue got resolved after reinstall the module.