I can't manage a mail-enabled SG through EAC

Graham Freeman 21 Reputation points
2020-11-06T16:14:15.443+00:00

Our onprem Exchange 2010 server has a MESG, "Board". It contains a mix of users and contacts.
After migration the MESG shows in EAC but only with the users as members.
The contacts were then exported from Exchange 2010 to a csv, and imported into EXO as Mail Contacts.

When I attempt to manage the group to add the contacts through EAC I cannot because "You can only manage this group in your on-premises environment. Use 'Active directory users & groups' or 'Exchange Admin Center' tools to edit or delete this group."

The onprem server HAS the contacts in the group.

Any idea of the best way to get the group sending messages to all desired members, rather than just the list of users that were migrated over? We need the list of external contacts in there too.

Microsoft Exchange Online Management
Microsoft Exchange Online Management
Microsoft Exchange Online: A Microsoft email and calendaring hosted service.Management: The act or process of organizing, handling, directing or controlling something.
4,175 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,349 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,886 questions
{count} votes

Accepted answer
  1. Vasil Michev 95,341 Reputation points MVP
    2020-11-06T18:05:23.807+00:00

    Do the contacts still exists on-premises, as this can result in "duplicate attribute" type of conflicts, causing them not to sync and explaining why you are not seeing them as members. Might be a good idea to recreate the MESG directly in O365 and add the users there.
    As for the error message, that's the expected behavior for any synced object, they need to be managed on-premises.


0 additional answers

Sort by: Most helpful