Feb 01 2022 05:25 AM
Feb 01 2022 05:25 AM
Ok, we dont know when this has happened. But we created a Office 365 group via the admin gui portal. its been used as a document library and its the main teams group in MS Teams. Now, the company wants to use the group 365 calendar. however, when users are trying to access the calendar, its not visible in Outlook and when they try to use it online, it goes to their calendar. In the URL, it has:
https://outlook.office365.com/calendar/group/<tenantIDName>/<office 365 group>/view/month
now, using the channel calendar in teams works. Reading the channel calendar, it seems its a filtered view of the office 365 calendar. which has been tested on another group and seems to be true.
we have called office 365 support and they are stumped as well.
Is there anything we can do (powershell cmdlets) toget this working/visible?
Mar 11 2022 05:38 AM
Mar 21 2022 02:46 AM - edited Mar 21 2022 03:40 AM
I have found the cause of the problem in my instance so I've place the fix below for you. Please check that this is actually the same problem before using the fix.
In Feb 2018 Microsoft by default HIDE email groups by default. What I found was that the group was there, but actually hidden. There is a way to list the hidden groups and then a way to unhide that group. The SharePoint groups I had that were not hidden were created before Feb 2018, those after wards are hidden from both the calendar and from the address book.
This solution worked for me
#Early 2018 MS stopped Groups from appearing in Outlook calendars or the address book by default
#If a SharePoint sites needs it's original Group Calendar or a Group Calendar is missing from Outlook then you have to unhide that group using Powershell.
#Connect to ExchangeOnline. You will be prompted to log in with your O365 credentials and MFA Connect-ExchangeOnline -UserPrincipalName xxxxxxxxxxx # Gets a list of all groups that are hiddenfrom* Get-UnifiedGroup |ft DisplayName,HiddenFrom* #Sets a group so that it is not hidden from Outlook or the address book #Change "Group Name" to the name of the group to unhide #Unhides the group from SharePoint Set-UnifiedGroup -Identity "Group Name" -HiddenFromExchangeClientsEnabled:$false #Unhides the group from the address book Set-UnifiedGroup -Identity "Group Name" -HiddenFromAddressListsEnabled:$false
Aug 03 2022 08:51 AM
Here's the kicker - even though I've connected to exchange online management via powershell, the set-unifiedgroup command consistently returns an error that it doesn't exist (though the get-unifiedgroup command works just fine).
Set-UnifiedGroup : The term 'Set-UnifiedGroup' 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 + Set-UnifiedGroup -Identity "Marcom" -HiddenFromAddressListsEnabled:$f ... + ~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Set-UnifiedGroup:String) , CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
Aug 08 2022 02:55 AM
Aug 09 2022 02:00 AM
Aug 10 2022 06:39 AM
That would seem to be the case. However, I've tried installing the Exchange Online Powershell module V1 and V2 to no avail. No one on my team can get any cmdlet with the word 'Unified' to work except for 'Get-UnifiedGroup'. After importing the exchange online module, we can run a 'Get-Command' and it returns no 'unified' cmdlets, save 'Get-' I don't know if it matters, but we are an all Azure environment, and do not have any on-premises Exchange servers. @paulcreedy710
Aug 10 2022 06:50 AM
Aug 10 2022 06:58 AM - edited Aug 10 2022 07:00 AM
We don't use on premises exchange either. The Exchange Online Powershell module is an add on for the online version of exchange, not the on premises one.
You can still use built in Powershell but it gets complicated if the credentials you use have MFA enabled. The Exchange Online Powershell supports MFA as it gives you the appropriate prompts when you log.
Further down that article is a link from where you can download it. Here is the direct link
Aug 10 2022 07:05 AM
Aug 11 2022 09:44 AM
Aug 12 2022 01:20 AM
To be honest, I'm not sure what's going on there as it works for me; I've not had that issue.
If you put this as the first line in the Powershell script that you are running before you connect to Exchange does it make any difference:
Connect-ExchangeOnline -UserPrincipalName xxxxxxx
I also launched Powershell itself 'As Administrator' because our set up here is very locked down permission wise.
Are you using Privilege Identity Management (PIM). I'm not for my user account but some posts I've seen elsewhere mention about having to additionally grant the Exchange online role.
Aug 12 2022 06:54 AM
Good morning, Paul,
Yeah, I've tried just about everything under the sun from as many articles as I can find. I always launch powershell as admin because almost everything I do with powershell requires it. We do use PIM, but not for my Global Admin account. I entered a support request to Microsoft, but haven't heard back yet. At this point, I've long given up and created the group a separate shared mailbox so they could have a calendar; just holding out hope that a solution eventually comes a long.
Thank you for all your help and suggestions :)
Aug 12 2022 06:57 AM - edited Aug 12 2022 07:01 AM
Going for the long shot here, could you try from a different workstation with Powershell installed etc installed or possibly from another global user account too. Just to rule out glitches with specific user or workstation permissions?
It seems one of those edge case scenarios, and permission or installation related.
Maybe even create another Global admin user just to try it out?
Aug 12 2022 07:21 AM
Aug 12 2022 09:29 AM