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 No comments

54 answers

Sort by: Most helpful
  1. Anonymous
    2021-06-17T11:25:19+00:00

    I've come across this issue, and I've discovered it's because my profile is on a UNC path, and if I've run as Administrator (as instructions invariably do...), I lose permissions to access the UNC path.

    The best solution for me is to either avoid using Administrator privileges or just use a local profile if needing to escalate.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-04-01T15:57:03+00:00

    Unfortunately, it does not work either. BTW I checked most solutions from many forums/tutorials/solutions and nothing.

    Still disappointed Microsoft don't have a real solution to refresh/reinstall/heal faulty PowerShell or PowerShell module.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-10-26T07:38:36+00:00

    depending on what you need, I would advise you to connect to MS first, and start a powershell session from there :

    I hardly use the 'local' cmdlets anymore


    #connect to office365 without MFA

    $Office365Admin = Get-Credential ******@heliconnl.onmicrosoft.com #use youre officeadmin account

    $SESSION = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "https://outlook.office365.com/powershell-liveid/" -Credential $O365CREDS -Authentication "Basic" -AllowRedirection

    Import-PSSession $SESSION

    Connect-MicrosoftTeams -Credential $Office365Admin

    regards Tom

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-09-25T09:05:56+00:00

    Hello Ashka123,

    May I know if there is any update for next troubleshooting steps? 

    Regards,

    Rick

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-09-23T03:36:59+00:00

    Do not know what wrong i am doing

    Was this answer helpful?

    0 comments No comments