Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We are trying to setup CRM 4.0 on-premise to work with Exchange online (365) but are having issues. We have an email router setup with incoming/outgoing profiles that connect to Exchange online. We are running rollup 21 which is supposed to make the email router compatible with Exchange Online 365. The CRM users are setup to use a "forwarding mailbox" for incoming and email router for outgoing. Our users are experiencing email flow issues, they cannot send emails from withing the CRM application. Below errors I see in the Email router event log. I'm hoping that if we resolve the errors...it will fix our email flow issues:
#26234 - The E-mail Router service could not process a provider work item using assembly: Microsoft.Crm.Tools.EmailProviders.dll and class: Microsoft.Crm.Tools.Email.Providers.ExchangeOnlinePollingSendEmailProvider. System.NullReferenceException: Object reference not set to an instance of an object.at Microsoft.Crm.Tools.Email.Providers.CrmPollingSendEmailProvider.HandleProcessMessageError(Exception exception, email emailMessage)at Microsoft.Crm.Tools.Email.Providers.CrmPollingSendEmailProvider.Run()at Microsoft.Crm.Tools.Email.Agent.ServiceCore.ExecuteProviderWork(Object providerQueueRequestObject)
#61042 - An error occurred while processing the outgoing e-mail message with subject "New Account Setup Information CRM:0010539" for ExchangeOnline: http://crm.sample-domain.com/company/ for delivery through https://outlook.office365.com/EWS/Exchange.asmx. Microsoft.Crm.Tools.Email.Providers.EmailException: Error: The user account which was used to submit this request does not have the right to send mail on behalf of the specified sending account.at Microsoft.Crm.Tools.Email.Providers.ExchangeOnlinePollingSendEmailProvider.LogEwsResponseErrorWarning(String message, ResponseClassType responseClassType)at Microsoft.Crm.Tools.Email.Providers.ExchangeOnlinePollingSendEmailProvider.ProcessMessageInternal(email emailMessage)at Microsoft.Crm.Tools.Email.Providers.CrmPollingSendEmailProvider.Run()
FYI, this is the article I followed....
If anyone out there is curious, I had to give the CRM service account "full access" and "send as" permission to each Exchange user (account) that used CRM. It works now.
Full Access and Send As are indeed the cause of the problem. We had the same too.
From the Microsoft Kb you mention, the Publishing Editor permissions over the user mailbox (that in the From field of the emails) granted to the service account (that specified in the Outgoing Profile of Email Router) is the key.
“Important The credentials that are specified in the outgoing profile must have "PublishingEditor" permissions (Delegate Access) or Send As permissions on the Exchange Online mailboxes that have to be accessed. Exchange Online administrators and users do not have these permissions by default. To add delegate permissions, Full Access permissions must be granted to the user in the outgoing profile. Send As permissions must be granted to the user in the Outgoing Profile.”
Business Applications communities