The intended benefit is straightforward: let managers explain an approval decision without moving from their phone to the web application. There is, however, an important wrinkle—Microsoft’s existing documentation already describes entering optional approval comments on mobile. That makes this a planned improvement to examine carefully, rather than a clean-cut “mobile comments arrive for the first time” announcement.
What Microsoft plans to improve
Microsoft’s roadmap description identifies a gap in the mobile approval experience: approvers have limited options for supplying the context behind a decision. The planned enhancement would let them both add and view approval or rejection comments directly in the Expense Management mobile app.
Those comments could explain why a report was approved, identify information needed before reimbursement, or provide feedback after rejection. Microsoft’s stated aim is greater consistency between mobile and web, reducing the need to switch applications to complete an approval decision.
These are intended benefits, not measured results. Nor does the roadmap description establish that every existing mobile deployment lacks comment entry—a distinction made necessary by Microsoft Learn’s current instructions.
Existing documentation already includes comment entry
Microsoft Learn’s guide to expense-report approvals, last updated January 31, 2026, explicitly documents optional Justification and Approval comments fields for approving or rejecting reports. It describes those fields for both individual reports and bulk decisions.
For an existing, configured deployment, Microsoft documents this report-level path:
- Open Power Apps on the mobile device, then open the Expense mobile app.
- Select Approvals and open a pending expense report.
- Choose Approve or Reject.
- Optionally complete Justification and Approval comments.
- Confirm the corresponding approval or rejection action.
This overlap is the most useful qualification to the announcement. The roadmap promises an improvement to adding and viewing comments, while the documentation already explains how to enter them. The available evidence does not establish precisely which interface behavior, deployment boundary, or comment-viewing capability accounts for the difference.
The defensible conclusion is that Microsoft plans to improve comment handling—not that mobile expense-report approvals currently have no comments at all.
Where this fits in a Dynamics deployment
Microsoft Learn describes the Expense Management mobile app as a Power Apps canvas app, accessed through the Power Apps mobile client. Its documented scope includes Project Operations Integrated with ERP and Project Operations for manufacturing-based scenarios. It requires Expense management to be fully implemented in the environment and uses Dynamics 365 Finance configurations for policies, workflows, and expense-report field visibility.
That matters for administrators: mobile is an interface to the configured expense process, not a replacement for the underlying approval workflow. Microsoft’s approval guide explains that submitting a report in Dynamics 365 Finance generates work items according to preset workflow configurations and assigns them to designated approvers.
The practical implication is to evaluate this enhancement against the organization’s actual report-approval process. A comment box is useful; a comment that reaches the right participant at the right stage is what makes the workflow useful.
What administrators should verify before rollout
The roadmap description leaves several implementation questions unanswered:
- Which app or solution version will deliver the enhancement?
- Will administrators need to update or configure anything?
- Where will existing approval and rejection comments appear?
- Who will be able to view those comments?
- Will comment requirements change, or remain optional?
- Will availability be staged across tenants?
These are validation questions, not announced product capabilities. A sensible acceptance test would use a nonproduction expense report, record the existing mobile behavior, and then compare comment entry and visibility after the enhancement becomes available. Testing both approval and rejection would help distinguish a genuine workflow improvement from a cosmetic interface change.
For now, December 2026 is an estimated availability window, not a deadline to build operational policy around. Microsoft’s roadmap disclaimer makes that uncertainty explicit.
The takeaway is modest but worthwhile: Microsoft is targeting a more consistent mobile expense-report approval experience. The strongest reason to watch item 573708 is not the promise of another text field—it is whether approvers can keep the decision and its explanation together without making a detour to the web.
References
- Dynamics 365 Project Operations: Support Approver Comments for Expense Reports in Expense Management Mobile app
- Manage expense report approvals by using the Dynamics 365 expense management mobile app | Microsoft Learn
- Manage expense line approvals by using the Dynamics 365 expense management mobile app | Microsoft Learn