Check out the latest Customer Service updates!Learn about the key capabilities and features of Dynamics 365 Customer Service and experience some of the new features.
Download overview guide | Watch Customer Service video
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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 have our Support Queue that has the address firstname.lastname@example.org, which creates Tickets IF that address is in the To.. line of and Email.
Now, the powers that be are looking to add some Alias email addresses for certain client's, so they can send emails to our Support email, but not create Tickets. Eg. Alias emali address created for first client is email@example.com, which we don't want to create a Ticket if anyone sends to that address.
However, on testing in Dev environment, since this is an Alias email address, it looks like Dynamics is reading it as the firstname.lastname@example.org email address. I did update the ARCUR rule to say Email To recipients does not contain email@example.com, but it still creates a Ticket due to the statement above.
Does anyone have a workaround or know how to solve this issue?
Business Applications communities