Somewhere in your organization there is an inbox called support@ and a person whose unofficial job is turning its contents into case records. Copy the subject, create a case, paste, set the customer, go back for the next one. Dynamics 365 has been able to do this job by itself for years, through automatic record creation and update rules — ARC rules to their friends — and the modern experience makes them close to a fill-in-the-blanks exercise.
The moving parts
An ARC rule watches a queue for incoming activities and turns them into records. That means the prerequisite is a queue with a mailbox behind it: an email-enabled queue whose address is your support inbox. Once inbound mail lands in the queue as email activities, the rule takes over. You will find the rules in the service admin center under Case settings, and a rule has exactly three steps.
Step one is the “what am I watching” part: which activity type (email, but also custom activities and other channels) and which queue.
Conditions and actions
Step two is a list of condition rows, evaluated in order — the first one whose condition passes wins. Open a condition and you get a name, an optional condition (blank means “always”), and the action: which record to create.
This ordered-list design is more powerful than it looks. A common production setup is three rows: if the sender is unknown, create a case flagged for triage; if the email subject contains an existing case number, append to that case instead of creating a new one (the platform’s tracking token handles most of this automatically); otherwise, create a standard case. First match wins, so you put the specific rules on top and the catch-all at the bottom.
Notice the link at the bottom of the condition: Save and open Power Automate. Under the hood, each condition’s action is a real Power Automate flow that the rule generates for you. Ninety percent of the time you never need to open it — but the door is there, and stepping through it lets you enrich the created case with anything a flow can do: look up the customer’s entitlement, set priority from the account’s tier, call a connector. You get the simplicity of a rule with the escape hatch of a flow.
The full picture
Step three handles the courtesy: automatic replies. Switch it on, pick an email template — Case Auto Response ships in the box for exactly this — and every customer whose email became a case gets an acknowledgement with the case number in the subject line, seconds after they hit send. That closes the loop that matters most to the customer: did anyone get my message?
Notes from the field
Three things worth doing on day one. Un-track internal chatter — condition your rule so emails from your own domain do not become cases, or your queue fills with reply-all noise. Watch the Activity monitor tab on the rule for the first week; it shows every inbound activity and what the rule did with it, which is where you catch the edge cases (auto-replies, out-of-office loops, newsletters). And resist creating cases from every address: a condition that requires the sender to resolve to a known contact keeps cold outreach and spam from polluting your service metrics — pair it with a triage view for the unknowns instead.
Set up once, this is one of those automations that quietly deletes a job nobody wanted: the mailbox never queues up unprocessed, cases are born with the email attached, and the acknowledgement goes out before a human has even seen the request.
