Roadmap dates are estimates. Microsoft says the AI at Work roadmap's dates and descriptions can change, and that items are removed once a feature ships, is canceled or is postponed.
What Microsoft says the feature does
According to the roadmap entry, an organization can designate an interim approver when someone submits an expense report. That person reviews and approves the report before the final approver sees it. The stated purpose is to confirm that the report is complete and compliant first.
In practice, this separates two jobs that often get lumped together:
- Preliminary check: someone confirms the report is complete and follows policy.
- Final authorization: the designated final approver makes the approval decision.
The baseline today
Microsoft's prerelease documentation shows what the flow looks like now:
- Submitting: After setup, employees can submit expenses through email or the Expense Agent web app, and the agent creates expense reports and applies configured rules automatically. The submitter reviews all expense lines, selects Submit and confirms. The report then becomes Submitted, the approver is notified, and the report is read-only. It moves from the Drafts tab to the Submitted tab.
- Approving: the approver opens the For My Approval tab and reviews amounts, categories and attached receipts. The approver can approve the report or send it back with comments. A report sent back returns to Draft, the employee is notified, and the employee can fix it and resubmit.
- Policy flags: Microsoft's documentation says these are advisory and don't block approval. Today an approver can approve a report that has flagged expenses.
An interim stage would add a checkpoint in front of that last step. That is my reading of the roadmap wording, not something Microsoft has demonstrated.
This isn't a brand-new idea
Interim approval has appeared in Microsoft's materials before, and the statements don't fully line up.
- Microsoft's 2026 release wave 1 plan describes the Expense Agent's approval workflow as supporting interim and final approvals, policy validation, and reminders.
- Microsoft's Responsible AI FAQ for the preview, however, lists a limitation: complex approval systems with interim or conditional approvals aren't yet supported.
The new roadmap item is best read as the first, simple version of that capability. Microsoft's own description calls it a "simple interim approval scenario." Anyone expecting multi-level or conditional routing should not assume it from this entry.
What Microsoft hasn't said
The roadmap record doesn't specify any of the following:
- How an interim approver is selected or assigned.
- Whether the interim reviewer can approve, reject, return or edit a report.
- Whether every report must pass through the interim stage.
- Whether multiple interim reviewers are possible.
- What happens if the interim reviewer is unavailable.
- How the stage interacts with AI-assisted policy evaluation, which is configurable separately.
- Licensing, prerequisites, or release version.
The current setup documentation covers submission channels, access, a default approver, rules, policy compliance, notifications, projects, mileage and per diem. It documents no interim-approver option. The setup page also notes that approval workflows are configured and managed in Business Central. Don't assume a setup procedure exists until Microsoft documents one.
Why it matters to finance and IT admins
The expected benefit is cleaner reports reaching senior approvers. A first reviewer such as a finance clerk or team lead could catch missing receipts or policy concerns before a manager signs off. That is an inference from the feature description. Microsoft hasn't quantified any gain in speed, rework or compliance.
There are also trade-offs to weigh:
- Added latency: each extra approval stage can slow reimbursement if the reviewer is a bottleneck.
- Accountability: if the interim reviewer vouches for compliance, the final approver may be tempted to rubber-stamp. Today's policy flags are advisory, so the human stages carry the compliance responsibility.
- Agent billing: Microsoft's setup documentation says the Expense Agent uses Copilot Studio messages once activated, and those are billed to the company. Any added workflow steps may affect usage, but Microsoft hasn't said so.
What to do now
- Treat November 2026 as a planning estimate, not a commitment.
- Document who in your organization would act as a first-line expense reviewer, and whether your policy requires one.
- Check the live roadmap and the Business Central Expense Agent documentation when the preview arrives. They should show the configuration steps and permissions.
- Don't change your existing approval workflows in anticipation of this feature.
If you're on-premises or in another cloud instance, the roadmap entry doesn't promise availability for you.