Forum Discussion
How do i change Properties of teams using powershell?
I was setting up a new team for my organisation and I wanted to add a calendar to the team by importing it as a site. For the calendar, i planned on using the Office 365 group calendar but the group didn't pop up in my outlook groups. Here (https://www.synigopulse.com/blog/item/office-365-groups-created-from-microsoft-teams-will-be-hidden-from-outlook-by-default) I found out that Office groups aren't visible by default when creating a team.
In the article they state that by changing "HiddenFromExchangeClientsEnabled" property, you can make the group appear as a office 365 group.
So i did some research on how to use Powershell. I installed the Microsoft Teams module (install-module -name MicrosoftTeams). I then tried to connect to ms teams (connect-microsoftteams) but this gave an error. The error said I need to run 'import-module MicrosoftTeams' but this command didn't give any result when entering.
I'm really new to PowerShell and don't know if this is the only and perfect solution to my problem. Anyone who could provide some help?
Set-UnifiedGroup is part of the Exchange Module.
https://docs.microsoft.com/en-us/powershell/module/exchange/set-unifiedgroup?view=exchange-ps
You can install this by running:
Install-Module -Name ExchangeOnlineManagementConnect by running:
Connect-ExchangeOnlineBe aware that for managing all aspects of Teams you might need 4 PowerShell modules.
1. AzureAD Module
2. Exchange online module
3. SharePoint module
4. Teams Module
6 Replies
You can try to run
Get-Module -ListAvailableAnd check if you see the MicrosoftTeams module.
To install the module with
Install-Module MicrosoftTeamsmake sure you are running the PowerShell as Administrator.
After installing the module
Import-Module MicrosoftTeamswill make the command available to you.
ShellBlazer thank you for your (very fast) reply! 🙂
I've checked the list of modules:
I then tried to install the module by using the command provided by you. Funny enough, nothing happened...
I then tried the last command u provided, which also gave an error.
Best check your current execution policy.
Get-ExecutionPolicyI'm guessing it is set to restricted.
You can set the execution policy to be bypassed for your current PowerShell session by running:
Set-ExecutionPolicy Bypass -Scope Process
