Apr 05 2018 06:08 AM
Teams now hides the Office 365 Groups that it creates from Exchange clients (Outlook, OWA, and the mobile apps). That’s as it should be for groups created for new teams. If you want to hide groups created for older teams, you can run the Set-UnifiedGroup cmdlet, but that soon becomes boring when you might have hundreds of groups to process. PowerShell to the rescue once again.
https://www.petri.com/hiding-office-365-groups-exchange-clients
Apr 05 2018 10:18 AM
Hm, so am I to assume that it actually works for you? None of the Teams I toggled the flags for have disappeared from either Outlook and OWA. And while Outlook can be excused as I'm on the deferred channel, shouldn't OWA at least be aware of the flags? Sigh...
P.S. Ordered hash tables and such, color me impressed :)
Apr 05 2018 10:27 AM
As I say in the piece, the change is rolling out... and while the change is effective in the back-end (i.e. you can set groups to be hidden from Exchange clients now), some client updates are also necessary. These will come in OWA and Outlook (to respect the flag) and Teams (to set the flag). Don't be so impatient.
As to ordered hash tables, I used these a lot to capture Office 365 data with PowerShell. Once in the hash table, you can do so much with data... as proven here.
Apr 24 2018 03:36 AM
This seems to be live now, both in OWA and Outlook (9126.2152).
Apr 24 2018 04:06 AM
Yep, working in both OWA, Outlook desktop, and Outlook for iOS (latest update). Groups disappear after a client refreshes, which in the case of Outlook desktop means the next time it runs Autodiscover (15 minutes). Outlook for iOS appears to refresh its folder list if you access it or the Groups section of the folder list. OWA refreshes itself periodically, or you can refresh the browser.
One of the side-effects (logical) is that if a group is hidden from Exchange clients, it disappears from Favorites. Just saying...
Apr 24 2018 04:23 AM
Apr 24 2018 05:53 AM
Teams doesn't appear in an address list like other mail-enabled objects unless its Office 365 Group is not hidden from the lists, so it is hard to know when private teams are available. Public teams can be found by the Join or Create a team option, which presents a list of suggested public teams available to the user. The search function on the same screen can be used to find other public teams that don't make the suggested list, which is determined by reference to signals in the Graph. Private teams don't appear in suggestions, so the only way to join them is to contact the team owner (how you learn about the existence of the team is another matter - perhaps via a coffee room conversation?).
Apr 24 2018 07:34 AM
Apr 24 2018 09:20 AM
The simple solution is to create a mail contact in your tenant directory for a channel email address in the teams that you think people will want to email. The mail contact will be in the GAL and can be addressed like any other email recipient. Messages will show up in the channel in the target team and can be actioned there by the sales team or whatever. And if you are nice, they might invite you into the team.
Seriously, this discussion shows that moving from Outlook to Teams is not possible if you still need some of the functionality available in Outlook...
Apr 24 2018 11:18 AM
Apr 24 2018 12:18 PM
The ability to @mention a team would require you to know the name of the team, no?
It's worth also saying that if you do not hide groups (used for teams) from Exchange, you will certainly see them in the GAL and other address lists, and you will be able to send email to those groups, but there's no guarantee that your email will reach anyone because a) the members of the team you send email to might never look at conversations in the group mailbox, which is where email will end up, and b) the group might not distribute copies of conversations to members in email, so the message won't reach members that way either...
Apr 24 2018 11:43 PM
Apr 17 2019 11:04 PM - edited Apr 17 2019 11:04 PM
If the group is potentially expecting external messages from people outside the group, perhaps the owner of the group should create the corresponding Yammer group which could either be left open or private. Allow said guest to request to join the Yammer group (still keeping that outside communication outside of Teams) but then add a new tab in the group within Teams with the Yammer group. I've been thinking how I can do this going forward with some of our scenarios as well (haven't done so as yet).
The only issue I still believe is that there is no notifications baked in to Teams for when a new Yammer message arrives in the Yammer group via the Teams Tab. Would be nice to have a Teams Banner who up but for now I'd imagine it's just the usual notifications via Yammer.
I realise this is an old topic now so please disregard if not required anymore.
Apr 26 2019 09:50 AM
Aug 20 2020 02:20 PM
Just FYI all as no one had actually posted commands yet to get this done, i thought i would asssit. I used some of the links and adapted the power shell so that it works for me in the most direct way.
First examine the problem, my groups that were showing the GAL had HiddenFromAddressListsEnabled set to both true and false, but ALWAYS had HiddenFromExchangeClientsEnabled set to false. So that is the property i need to modify in order to correct the issue.
First we need to connect to office365 powershell. I have opened a powershell command prompt locally and run the following commands:
$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $Session -DisableNameChecking
Second we run the command to see how many groups are affected:
Get-UnifiedGroup -ResultSize Unlimited | select Name, DisplayName, HiddenFromExchangeClientsEnabled, HiddenFromAddressListsEnabled | where {$_.HiddenFromExchangeClientsEnabled -eq $False}
Third We dump those groups to a CSV file. Make sure the c:\temp\teams\ path exists or script will fail.
Get-UnifiedGroup -ResultSize Unlimited | select Name, DisplayName, HiddenFromExchangeClientsEnabled, HiddenFromAddressListsEnabled | where {$_.HiddenFromExchangeClientsEnabled -eq $False} | Export-csv -Path c:\temp\teams\HiddenGroups1.csv -NoTypeInformation -Encoding Ascii
Fourth, we fix them. I loaded this code into its own .ps1 file and ran it from the command line, but i think you could paste in the code directly.
$GroupList = Import-CSV "c:\temp\teams\HiddenGroups1.csv"
ForEach ($G in $GroupList) {
If ($G.HiddenFromExchangeClientsEnabled -eq "FALSE") {
Write-Host "Hiding" $G.DisplayName "from Exchange Clients"
Set-UnifiedGroup -Identity $G.Name -HiddenFromExchangeClientsEnabled:$True }
}
Worked for all but two test groups, not sure why those ones it did not work for, but i just deleted them as they were from old tests.
hope it helps someone.
Jan 21 2021 09:56 AM
Set-UnifiedGroup -Identity Team1 -HiddenFromExchangeClientsEnabled:$True |
it served the purpose best for me - thanks!
Jul 02 2021 12:38 PM
@Tony Redmond This simply is not true. Every single team we create has its O365 group show up in the GAL.
Jul 02 2021 01:03 PM
@PhilHemingwaySTV I'm sure that every team does turn up in the GAL, but only if an action is taken to update its HiddenFromExchangeClientsEnabled property. All teams created through team-aware admin interfaces set this property to $False. If you create using an ISV app, PowerShell, or some Graph-enabled app, you might find that the property is set to $True. For instance, even Teams sets the property to $True for the special team it creates to control who's allowed to create approvals templates. But the general point holds true: teams created through Teams set HiddenFromExchangeClientsEnabled to $False.
Jul 06 2021 01:42 PM
Jul 06 2021 02:16 PM