Forum Discussion
Office 365 group calendar missing?
You also get that error if the group you are targeting doesn't exist.
If you go into Exchange Admin to see the groups, it could be there's a typo on the name or the name you are using wasn't the one that was created. Groups can also have alias names which may not match the actual group name.
Does this bring back any results?
Get-UnifiedGroup |ft DisplayName,HiddenFrom*
"Set-UnifiedGroup -Identity "<groupID>" -HiddenFromExchangeClientsEnabled:$false"
I get the error:
"Set-UnifiedGroup: The term 'Set-UnifiedGroup' is not recognized as a name of a cmdlet, function, script file, or executable program."
If I run "Get-Command" I can verify that the cmdlet is missing from the list. It's not a permissions issue, as I am the Global Administrator. It's not a misspelling of the group name or the ID string. And yes, I am able to run "Get-UnifiedGroup |ft DisplayName,HiddenFrom*", and verify the group I'm attempting to edit is in the list. The "HiddenFromExchangeClientsEnabled" parameter is set to True, and I want to set it to False. Unfortunately, I can't because the "Set-UnifiedGroup" cmdlet simply does not exist. A conundrum indeed.
- The issue is happening for everyone on my team. I just can't seem to narrow down the cause. I've been playing around with various roles in both AAD and Exchange Admin Center to try and track down the root cause, but my other Global Admin and both my Exchange Admins are having the same issue. Some of us are on Windows 11, but most of us are on 10. Everyone uses Windows Powershell, though I installed Powershell 7 on my machine to troubleshoot. It's clearly something organization specific - however, as I am the O365 admin, I cannot think of anything I'd have done that would have triggered this. I've had no other issues with Exchange Online Management. I'll keep digging around in my spare time and if I eventually figure out the cause/resolution, I'll post it here.
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?
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 🙂
Hi
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:
Import-Module ExchangeOnlineManagement
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.