Hybrid Exchange Distribution Group ?

FarazI995 200 Reputation points
2024-07-29T16:11:37.78+00:00

Therefore, the company I worked with encountered some confusion in their hybrid MS365/on premises deployment.

There is a distribution list (which we call) that exists locally in the management console and on the MS365 end. However, although the local Exchange control panel displays as accepting emails from both internal and external sources of the organization, MS365 has decided to ignore this content and only accept emails from "internal" to the company. distlist1@example.comdistlist1

Therefore, emails used to receive invoices from a specific team were rejected and their emails were not received. distlist1

This cannot be changed in terms of MS365 and appears to be some kind of disconnection or unsynchronization between Exchagne local and MS365.

I'm not sure where to start looking for the possible cause of this issue with MS365, but if anyone has any instructions on where to look next and fix this problem on MS365, which actually accepts the local setting of 'allow everyone to send to list', that would be great.

Microsoft Exchange Online
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
2,136 questions
{count} votes

Accepted answer
  1. Vasil Michev 108.2K Reputation points MVP
    2024-07-30T07:06:57.6433333+00:00

    The easiest thing to do here is to recreate the DG as cloud only (i.e. remove it in AD and create it directly in O365). If that's not an option, you will have to verify the corresponding attributes in AD and make sure there are no sync issues (usually a duplicate address or similar) that prevent the changes to replicate to Exchange Online.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.