Connect-MicrosoftTeams not working

Anonymous
2019-09-21T21:59:22+00:00

Hi Team, Please advice am i doing something wrong

PS C:\WINDOWS\system32> find-Module -Name MicrosoftTeams

Version    Name                                Repository           Description

-------    ----                                ----------           -----------

1.0.2      MicrosoftTeams                      PSGallery            Teams Cmdlets module

Installed module using - install-Module -Name MicrosoftTeams.

Getting error when run     Connect-MicrosoftTeams

PS C:\WINDOWS\system32> Connect-MicrosoftTeams

Connect-MicrosoftTeams : The term 'Connect-MicrosoftTeams' is not recognized as the name of a cmdlet, function, script

file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct

and try again.

At line:1 char:1

  • Connect-MicrosoftTeams
  •

    + CategoryInfo          : ObjectNotFound: (Connect-MicrosoftTeams:String) [], CommandNotFoundException

    + FullyQualifiedErrorId : CommandNotFoundException

Microsoft Teams | Microsoft Teams for business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

54 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-10-03T06:50:14+00:00

    Hello Ashka123,

    Haven’t heard from you for a few days. I want to make a summary here to make it clear to you.

    Problem: Getting error when running Connect-MicrosoftTeams: Connect-MicrosoftTeams : The term 'Connect-MicrosoftTeams' is not recognized as the name of a cmdlet, function, script, file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

    What we have done:

    1. Import the module.
    2. Re-install the module.
    3. Get the path of the modules.

    Possible solution:

    1. Create a new windows profile.
    2. Run cmdlet Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

    Regards,

    Rick

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2019-10-04T19:36:35+00:00

    Even after this command its not working.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2019-10-06T22:05:46+00:00

    Hello Ashka123,

    Sorry for the late reply because I was off duty before. In order to look into the issue further, would you please check my reply on September 29, try the 3 points, and let me know results. It is important for the next troubleshooting steps. It may need some time for further investigating but I will try my best to help you.

    Regards,

    Rick

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-10-06T23:08:01+00:00

    yes it works when run powershell ISE as a administrator. Does that mean i need to use powershell ISE to connect team

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Anonymous
    2019-10-08T14:48:44+00:00

    Hello Ashka123,

    Thanks for your prompt update! Since the PowerShell ISE works as expected, we can confirm the issue is related to your PowerShell environment. But I want to set up an expectation that it still may need a long time to reach the endpoint of this investigation. As a temporary workaround, you can use PowerShell ISE and run the cmdlets.

    For the next troubleshooting steps, please run the following commands via PowerShell ISE:

    1. Check if you have custom profile. Run Test-Path $profile separately
    2. Please run the following cmdlet: $host.Runspace | fl separately

    Regards,

    Rick

    Was this answer helpful?

    0 comments