Forum Discussion
Office 365 group calendar missing?
Hi
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
https://docs.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps#install-and-maintain-the-exo-v2-module
- Hi
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*- Sorry, Paul. The problem is that I *am* using Exchange Online Powershell v2.0.6 (although I also tried this with 2.0.5 prior to today; updating did not resolve the issue). I can connect to ExchangeOnlineManagement via Windows Powershell or Powershell 7. In either case, when using the command:
"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.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.