PowerShell command Get-CsTenantFederationConfiguration fails connected to our Microsoft 365 tenant

Question

I have problems with my settings for external access sticking. I have noted several others with the same problem and followed their guidelines to use PowerShell instead. However I get an error when I try to run the command Get-CsTenantFederationConfiguration.

1. I connect with command Connect-MicrosoftTeams -AccountId xxxx
2. I run the Get-CsTenantFederationConfiguration and gets the following error

Get-CsTenantFederationConfiguration : Connecting to remote server api.interfaces.records.teams.microsoft.com failed with the following error

message : The WinRM client received an HTTP status code of 403 from the remote WS-Management service. For more information, see the

about_Remote_Troubleshooting Help topic.

At line:1 char:1

• Get-CsTenantFederationConfiguration

• 
      + CategoryInfo          : ResourceUnavailable: (:) [Get-CsTenantFederationConfiguration], PSRemotingTransportException 
  
      + FullyQualifiedErrorId : System.Management.Automation.Remoting.PSRemotingDataStructureException,Microsoft.Teams.ConfigApi.Cmdlets.GetCsTenant 
  
     FederationConfiguration
  
  

Any ideas on what I can do to get it working? I have done a lot of searching but can not find this specific problem description anywhere. I can understand if it is my local WS-Management service that cause the problem or if it is a problem on the cloud end.

Answer 1

Hello Patrik S_,

Good day to you and hope you are doing well.

Regarding your issue, suggest you to kindly verify your system is supported for Teams PowerShell module via follow Teams PowerShell Module - Supported Versions. If your system is under supported version list and still facing issue, check with uninstall Teams PowerShell module re-install it via follow Install Microsoft Teams PowerShell. After re-install Teams PowerShell module, try to run the cmdlet and check.

If still same error occurs, suggest you to run this PowerShell command from different system. Also if other users in your organization have admin permission, ask that user to run this command with his/her account with own system and on your system and check. With this we can identify where the issue is. At this point, your kind co-operation will be highly appreciated.

Thank you so much for your precious time. Stay safe, happy and healthy forever.

Regards, Ankita Vaidya

Answer 2

Thank you for your time and your answer. Uninstalling and re-installing following the guidelines provided by you above helped!