Case 05370016 Hybrid Exchange Issues

[PrecisionIT]

All,

Still struggling with this. Veeam support pointed to Microsoft. Microsoft sees no issue with the configuration. Here is the environment:

On-Prem Exchange 2016 Hybrid Configuration with Mailboxes in both locations.

If I set Veeam for M365 to point only to M365 and backup mailboxes in the cloud, that works. Setting it to on-prem and backing up on prem works. When I switch it to Hybrid the error I get is Exchange Account not found. The error code references the ExternalDirectoryObjectID.

5/10/2022 6:00:03 PM :: Processing mailbox %username% completed with warning: Exchange account was not found (ID: a13246ff-79ae-4570-a1f1-257dxxxxxxx).

The mailbox is licensed

[PrecisionIT]

From the logs of an onprem mailbox only user.

Resolving excluded objects...
[12.05.2022 10:21:59] 93 (5836) Building excluded objects set...
[12.05.2022 10:21:59] 93 (5836) Found 0 excluded objects
[12.05.2022 10:21:59] 93 (5836) Resolving objects...
[12.05.2022 10:21:59] 93 (5836) Resolving mailbox (ID: c18961ed-7ee0-4f85-af5a-d6f57xxxxxxxx:00000000-0000-0000-0000-000000000000)...
[12.05.2022 10:22:00] 112 (10996) Azure authorization token updated (client ID: 80104836-0f5b-42fb-a3bc-xxxxxxxx, resource: https://autodiscover-s.outlook.com/)
[12.05.2022 10:22:00] 93 (5836) Warning: Exchange account was not found (ID: c18961ed-7ee0-4f85-af5a-d6fxxxxxxxx

[Mike Resseler]

@PrecisionIT

I will review the case tomorrow and escalate in my weekly meeting with support if needed. In the meantime, please keep me updated about the progress you have with support.

[PrecisionIT]

I followed the instructions here to confirm there is no link to any cloud mailboxes. The Get-User %username% | select-object Name,*recipient* has "PreviousRecipientTypeDetails" set to none. https://www.alitajran.com/permanently-c ... lbox-info/

[Mike Resseler]

@PrecisionIT

The engineer should have contacted you again with new information. That should solve the issue hopefully. Let me knw if that works

[Switchie_Urs]

@PrecisionIT

Hope you could resolve your issue? if so, care to elaborate on what was causing the problem or how to mitigate it?

thanks,
Urs

[Mike Resseler]

I see that the case got closed with no response. I think it is best that you create a case yourself, and maybe (if you believe that it is the same problem) point to this specific case. I saw something was done, but we did not get a response whether it solved it or not.