Exchange Hybrid - On-Prem mailboxes can't send to Online mailboxes
We're now running Exchange Hybrid OnPrem: Exchange 2019 latest patch. On-Prem mailboxes are not able to communicate with mailboxes in Exchange Online in any way. The other way around is working fie though. Mailboxes on-prem: The communication to Exchange Online mailboxes isn't working > Can't send emails to Exchange Online mailboxes, or see free busy of Exchange online mailboxes and can't send calendar invites. Mailboxes in Exchange Online: Receive emails from external sent to: email address removed for privacy reasons - working. Receive emails from external sent to: email address removed for privacy reasons - working. Receive emails form external setn to: email address removed for privacy reasons - NOT working. Receive emails from internal on-prem mailbox - NOT working. No matter to which domain it is sent. Calendars: Users can fully see on-prem calendars and can also send invites. Send emails to external and internal - working. The Exchange on-prem queue shows: DeliveryType: DnsConnectorDeliver Status: Retry NextHopDomain: cadomain.mail.onmicrosoft.com The bounce back emails the on-prem mailbox receives when trying to send to a mailbx that is online: Server at cadomain.mail.onmicrosoft.com (104.47.75.164) returned '400 4.4.7 Message delayed' 3/24/2023 3:38:01 AM - Server at cadomain.mail.onmicrosoft.com (104.47.75.164) returned '450 4.4.316 Connection refused [Message=Socket error code 10061] [LastAttemptedServerName=cadomain.mail.onmicrosoft.com] [LastAttemptedIP=104.47.75.164:25](Socket error code 10061)' This is the on-prem Exchange delivery report: Delivery Report for usernametest2 (usernametest2(at)domain.ca) Submitted3/24/2023 9:25 AM EXCHANGE2019 The message was submitted to on-premExchange.domain.local. Pending 3/24/2023 9:25 AM on-premExchange.domain.local Message was received by on-premExchange.domain.local from on-premExchange.domain.local. 3/24/2023 9:25 AM on-premExchange.domain.local The e-mail address for recipient "usernametest2(at)domain.ca" was updated to the e-mail address "usernametest2(at)cadomain.mail.onmicrosoft.com". The message is in the process of being delivered. Submitted 3/24/2023 9:27 AM on-premExchange.domain.local The message was submitted to on-premExchange.domain.local. Pending 3/24/2023 9:28 AM on-premExchange.domain.local The e-mail address for recipient "usernametest2(at)cadomain.mail.onmicrosoft.com" was updated to the e-mail address "usernametest2(at)domain.ca". The message is in the process of being delivered. 3/24/2023 10:40 AM on-premExchange.domain.local Message delivery is taking longer than expected. There may be system delays. For more information, contact your email admin.
Internal mails get sent to primary smtp instead of alias
Hey there, in our company we have a service mailbox (user mailbox) with several aliases for different top level domains. Before they were all separate mail boxes with different mail rules, but for simplicity and management we merged they all on the main (.com) domain and combined the mail/forwarding rules. Now we have the issue that internal mails sent/forwarded to the alias domains, automatically get resolved and sent to the primary SMTP address and therefore the mail rules don't get triggered. Alias also won't show in the mail header. We have already deleted all offline address books(OAB), enforced the use of the GAL (via client and registry) and cleared all caches. Also, not all internal mail accounts are affected, since this usually happens with accounts which are in the delegation of the service mailbox (via security group) yet not all of them are affected. Any suggestions?
MS Teams and Exchange 2016 (Hybrid) calendar integration
Hi, We have setup Exchange hybrid (Classic full) with Exchange 2016. All mailboxes are currently hosted on-premises on Exchange 2016. AAD connect is setup to sync users. I noticed that new HCW doesn't configure federation anymore. I am looking to understand the requirements to have Microsoft Teams calendar working for on-prem mailbox users. Please advise on the requirements to achieve it and point me to any articles that can assist in setting this up. ThanksExchange archive mailbox migration license issue
Hi all, I have a situation where my environment is in a hybrid state with users ready to migrate. Some users are over 100GB but less 240GB, the Microsoft article on migrating large mailboxes says i have to provision the cloud archive first, but the documentation on this says i need a license. What's confusing me is if assign a license before they migrate this creates a whole new mailbox and all sorts of screwy thing happen and you have to clean up etc.. so, you instead assign the license after the migration.., but the cloud archive docu. is saying I need to assign a license for the cloud archive first. Has this changed where i can create the Cloud archive on-prem and migrate without needing a mailbox? am i missing something?Exchange Decommissioning Set-Remotemailbox command
Hi all, I have a situation where someone was with a hybrid Exchange Server configuration was using scripts to provision accounts with Set-RemoteMailbox. Testing was being done with the recipient management using the exchange management and noticed mailboxes are being provisioned and working as expected without even running their set-remotemailbox commands and are curious if this is even needed anymore. So I guess my question is, at this stage where .\CleanupActiveDirectoryEMT.ps1 is the last thing to do, would set-remotemailbox still be necessary, and what would it be used for. I know usually you can just create an on-prem mailbox, synced and license, so I'm not sure if set-remotemailbox is required for new mailboxes or but I'm thinking it's for managing mailboxes that were previously migrated. Thanks for any input.
Exchange Hybrid connector validation from o365 to on-prem
We recently setup Exchange Hybrid on Classic mode. Completed without errors. During setup we ensure that the Transport Certificate is valid and we assigned our 3rd party cert. We checked on IIS that "Default Front End" certificates are assigned with 3rd party cert. IIS 'Exchange Back End' is using the private "Exchange Server" certificate. When checking Exchange online connectors and validating the O365-Onprem connector, it errors with "450 4.4.317 Cannot connect to remote server [Message=SubjectMismatch Expected Subject: ...... Thumbprint:######" When troubleshooting and Checking the certificate thumbprint from the error message on the server. Determined that the thumbprint belonged to the private certificate used in the 'Exchange Back End' Not sure why it's presenting the wrong certificate and not the front-end certificate? Normal email flow is still working. Appreciate anyone's feedback.