Additional features, settings, or issues not covered by specific Microsoft Teams categories
You need to execute Import-Module MicrosoftTeams after Install-Module.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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
+ CategoryInfo : ObjectNotFound: (Connect-MicrosoftTeams:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Additional features, settings, or issues not covered by specific Microsoft Teams categories
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.
You need to execute Import-Module MicrosoftTeams after Install-Module.
I am getting same error in ISE also.
Thanks for sharing.
How do i install an earlier version? do i have to uninstall my current version?
Hello Ashka123,
We haven’t heard back from you. Do you need any further assistance?
Best Regards,
Sylvie
Hello Ashka123,
Sorry for the delay reply. We escalated your case as your problem persists after a lot of troubleshooting. This is Sylvie and I am writing this thread by now. We truly appreciate all your efforts and patience during our troubleshooting process.
Currently we identified that the main problem could be related to your PS environment. For the above cmdlets provided by Rick, it was his typo, the two cmdlets should be as following:
Test-Path $profile
$host.Runspace | fl
This can help you check whether you have the correct PowerShell profile configured in your Windows PC.
Meanwhile, for the new problem you encountered, I would like to confirm the following:
Rick suggested creating a new Windows profile before, but we haven’t received the feedback from you. If haven’t did it before, please kindly try to do it to check the outcome.
Please feel free to share the updates with us.
Best regards,
Sylvie