What the roadmap says
The item is in development, and its details are sparse:
- Product and platform: Dynamics 365 Business Central, on the Web platform.
- Cloud: Worldwide (Standard Multi-Tenant).
- Release ring: Preview.
- Estimated preview: February 2027.
- Estimated general availability: April 2027.
Microsoft says roadmap dates and descriptions are estimates that can change. Entries are removed once a feature ships, is cancelled or is postponed. As of early November 2026, nothing here has shipped.
The entry does not say several things:
- Whether the tag applies to a message, a conversation or some other Outlook item.
- What happens to the tag when processing fails or only partly succeeds.
- Whether admins can rename, remove or customize the tag.
- Which licensing, build or version requirements apply.
I won't guess at any of these.
Why a label matters
Microsoft's documentation says the Expense Agent handles receipt intake, data extraction, categorization, itemization and expense line creation, then groups expenses into reports for review and approval. Employees can submit expenses through a dedicated web app or by forwarding receipts to a shared mailbox.
That makes the mailbox a working queue. Several people may watch the same inbox, and without a visible marker they have to cross-check Business Central or the expense app to see whether a forwarded receipt was handled. A tag in Outlook would let people filter or sort on the processed status.
A precedent: Payables Agent
Business Central already has something similar elsewhere. Microsoft's 2026 release wave 1 plan says Payables Agent assigns the Processed by Payables Agent category to the emails it picks up, so people working in the same Outlook mailboxes can identify the messages the agent has handled.
The roadmap calls the new Expense Agent marker a "tag," while the Payables Agent feature uses the word "category." I can't confirm from the roadmap text that the two work the same way. The Payables Agent feature is a reasonable guide to what the Expense Agent version might look like, but it is only an inference.
What the tag will not tell you
"Processed" is a status cue. It is not an approval. Microsoft's documentation says the agent suggests expense details based on the email content. It adds: "Always review automatically created expenses to make sure the information is accurate before submitting the report."
Treat a tagged email as a sign that the agent picked it up. Don't treat it as a sign that:
- The expense is correct.
- The expense is policy-compliant.
- The report has been submitted or approved.
- The employee has been reimbursed.
The roadmap makes none of those claims. It also doesn't say the tag prevents duplicate submissions.
Who this affects
The tag is relevant only to organizations that have set up the email workflow. Microsoft's setup documentation lists these requirements:
- A supported country or region version, and the Expense Agent capability enabled on the Copilot & Agent Capabilities page.
- A Microsoft 365 user mailbox or shared mailbox, with Full Access permission on that mailbox.
- The Enable agent setting on, with a configured Mailbox Account.
- The Process incoming emails with receipts setting on. The setup page says this setting controls whether the agent reads its mailbox and processes incoming emails containing receipts, and receipts are only processed when a mailbox is configured.
Microsoft also states that the web app is always on, so employees who never email receipts won't see any tagging. The setup guide notes that the agent consumes Copilot Studio messages, which are billed.
Language support is limited too. The setup page says Expense Agent is validated and supported in English (EN-US) only, and that other languages might not work as intended.
What admins can do now
You can prepare before the preview arrives:
- Confirm that mailbox delegation and the email-processing settings are correct. The tag can only appear on mail the agent actually reads.
- Tell shared-mailbox users that a future tag will mean "picked up," not "approved." Setting that expectation now avoids confusion later.
- Wait for Microsoft's release plan or a Learn page before building mailbox rules or views around the tag. Its exact behavior is still undefined.
Bottom line
This is a modest quality-of-life addition rather than a new capability. It still addresses a real gap in shared-mailbox workflows. If it follows the Payables Agent model, it could save finance teams a lot of repetitive checking. The preview is estimated for February 2027 and general availability for April 2027, but both dates may change, and several implementation details remain unconfirmed.