This is a very obscure problem, so I’m recording this more for my own reference in future rather than expecting anyone else to have the same issue! The issue occurs when a migration from a hybrid exchange domain to another domain which uses AD Sync has been completed in the following manner: filter/delete user in…
I was getting pretty confused with the various options around powershell commands to use with Exchange online. For example, to add a user to a distribution group in O365, I had come across 4 different commands:
|
1 2 3 4 |
[cc lang="powershell"]Add-AzureADGroupMember Add-AzureRMADGroupMember Add-DistributionGroupMember Add-MsolGroupMember[/cc] |
So after some digging I realised that the *-AzureRM* are powershell cmdlets to modify general Azure resources using…
A script I recently used to add members to an office 365 distribution group using a remote exchange session in a hybrid setup (covered at the end).
|
1 2 3 4 5 |
[cc lang="powershell"]$SourceFile = "" Import-CSV $SourceFile | ForEach ` {Add-DistributionGroupMember -Identity "Group Name" -Member $_.UPN Write-Host -ForegroundColor Green "Processed the record for $($_.UPN)" }[/cc] |
CSV file contains UPNs of all users to be added. I also found it useful to see who had permissions to send to this group using
|
1 |
[cc lang="powershell"](Get-DistributionGroup -Identity "Group Name").AcceptMessagesOnlyFrom | ForEach {Get-User -Identity $_}[/cc] |
…
The scenario is that a user account has been created in Office 365 in a hybrid setup. This scenario is actually ok and is supported by Microsoft. However, it causes problems for an Office 365 user when they require access to public folders on the on-premises Exchange server. First make sure you have the correct…