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
    2021-04-09T00:34:47+00:00

    Most likely the reason is the meanwhile un-supported TLS 1.0 and 1.1. but it may still be the setting for some PowerShell versions. To work around:

    Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord

    Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord 

    Then exit and re-start PowerShell as admin.

    It did the job for me.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2021-05-09T13:58:58+00:00

    Sweet. Worked like a Charm !!

    I didn't have to downgrade MS Teams module.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-06-08T08:22:03+00:00

    It worked for me like this:

    1. Install module in Administrator's powershell

    2. Then run powershell as user

    PS C:\Users\t> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process

    Execution Policy Change

    The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose

    you to the security risks described in the about_Execution_Policies help topic at

    https:/go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?

    [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"): y

    PS C:\Users\t> Import-Module MicrosoftTeams

    PS C:\Users\t> Connect-MicrosoftTeams

    (asks for credentials)

    Account                       Environment Tenant                               TenantId

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

    Worked for me, thanks!

    Was this answer helpful?

    0 comments
  5. 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