Typically, you use a connector to route messages from your Office 365 mailboxes to your on-premises users. You might also use a connector to route messages from Office 365 to a partner organization. When Office 365 can't deliver these messages (for example, the connector is incorrectly configured, or there have been networking changes in your on-premises environment), the messages are queued in Office 365. After 48 hours, the messages expire, and are returned to the sender in a non-delivery report (also known as a NDR or bounce message).
Check the details below and follow the instructions to fix the issue.
Type the fully qualified domain name you received from the company that hosts your website, and click Check now . We'll check ...
Type the IP address you received from the company that hosts your website, and click Check now . We'll check that it's correct. ...
Type the user ID that you use to sign in to the account that needs a password reset (for example, [email protected]). ...
Typically, an email loop starts when Office 365 thinks a recipient doesn't exist in the service. If the MX record for the ...
Typically, you use a connector to route messages from your Office 365 mailboxes to your on-premises users. You might also ...
Unable to access the configuration system on the remote server. Make sure that the remote server allows remote configuration ...
Unable to communicate with Outlook application to get Add-ins information. Can you restart Outlook manually and retry? Exception:{0} ...
Unable to delete some security groups because they are synchronized with your local Active Directory or they are system security ...
Unable to federate your domain. It appears you do not have a federation trust. Please close and run the Hybrid Configuration ...