Forum Discussion
Set-UnifiedGroup -EmailAddresses does not update Azure AD proxyAddresses property
Here's how to recreate the problem: 1. Set-UnifiedGroup -Identity XYZ -EmailAddresses @{ Add = 'additional address' } 2. (Get-UnifiedGroup -Identity XYZ).EmailAddresses and confirm additional ad...
Two points. First, IIRC only the primary SMTP is synchronized to other parts of the service (which is the reason why DBEB doesn't support secondary aliases for Groups). The workaround is to use the PrimarySMTPAddress instead, and change it twice to have the new alias recorded as secondary:
Set-UnifiedGroup blabla -PrimarySmtpAddress 'email address removed for privacy reasons'
Set-UnifiedGroup blabla -PrimarySmtpAddress 'email address removed for privacy reasons'
The other thing that comes to mind is that the process is not always synchronous and when the initial "signal" fails, it can take up to 24h to sync. If you are in a hurry, use the method above.
Set-UnifiedGroup blabla -PrimarySmtpAddress 'email address removed for privacy reasons'
Set-UnifiedGroup blabla -PrimarySmtpAddress 'email address removed for privacy reasons'
The other thing that comes to mind is that the process is not always synchronous and when the initial "signal" fails, it can take up to 24h to sync. If you are in a hurry, use the method above.
VasilMichev Thanks for the information. If I understand you correctly, you'd use Set-UnifiedGroup to set the secondary email address first and then the use it again to set the primary email address second, thus bumping the previously set address to a secondary position. I can't do that with the architecture of our code, where the ordering of operations is different.
Is this a known bug? I just doesn't seem reasonable that this property wouldn't sync to Azure AD and be available via Graph.