420 4.2.0 Transient Failure during recipients lookup AmbiguousRecipientTransientException

Anonymous
2024-12-17T21:59:18+00:00

Exchange Online

Sending email to certain external email recipients expires. The email recipients are also a Guest Mail User invited to use/access SharePoint or Teams. Could the external email address and guest email be conflicting and causing our sending server to not resolve the external address? If yes, how can this be fixed without disrupting their SharePoint and Teams collaboration?

Had a ticket open with MS support. Had me run an extended trace report. MS support read the report and said the recipient server was not able to resolve the recipient email address. However, the IT team of the recipient server said it's our server that cannot determine the correct email address.

Ran another extended report but still running after many hours.

Reason: [{LED=420 4.2.0 Transient Failure during recipients lookup AmbiguousRecipientTransientException, Exception of type 'Microsoft.Exchange.Transport.Categorizer.AmbiguousRecipientTransientException' was thrown.} Reason: [{LED=550 4.4.7 QUEUE.Expired; message expired}

Any ideas?

Thanks,

Vince

Microsoft 365 and Office | Install, redeem, activate | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

60 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2025-02-17T11:50:56+00:00

    Yes, I opened it through the Administrator portal, I sent these links together. I had already made all the queries via Powershell, the responsible engineer requested the PSR twice, with the same steps. The feeling is that he has a lot of tickets and cannot respond, and he is buying time.

    They have already changed engineers twice

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-02-14T21:36:35+00:00

    I had the same issue. They fixed my issue in a couple days (I did this through the 365 partner portal however) - did you make a ticket within the admin portal for this?

    I linked them this post itself & they thanked me for it!

    They told me they've contacted the 365 developer team about this as it has been happening more and more often. Who knows how long a full fix will take though

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-02-14T17:49:15+00:00

    Thanks for sharing the bug number. I've been with MS for 3 weeks, and no support
    This is very frustrating

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-02-08T17:51:54+00:00

    Thanks for the bug#, Matt!

    Much appreciated!

    Cheers, Alex

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-02-07T18:25:26+00:00

    "Yes, we do have an internal bug number. If the issue reoccurs, please open a case citing bug number BUG- 5204442, which is currently being worked on by the Exchange Online Provisioning team."

    Cite that bug number and see if you can get some traction under your case.

    Was this answer helpful?

    10 people found this answer helpful.
    0 comments