What Microsoft says is coming
The roadmap entry (ID 573608) covers the web platform only. It lists the Worldwide (Standard Multi-Tenant) cloud instance and both Preview and General Availability rings.
The stated behavior is narrow. Within one session, a user can switch among the Business Central companies and environments they are already authorized to use. The listed benefits are:
- Access to multiple authorized Business Central environments from the Expense Agent web app.
- Direct switching between companies while managing expenses.
- Less context switching for people working across organizations, business units or legal entities.
The roadmap does not describe the interface. It doesn't say whether unsaved work survives a switch, whether the app asks for confirmation, or whether several contexts can be open at once. It also names no affected Business Central versions or licensing conditions.
What this is not
This is a navigation and session change. It is not a permissions change.
- It does not grant access to any additional company or environment.
- It does not consolidate expense records across companies.
- It does not move data between environments.
- It does not change how receipts are extracted, categorized or approved.
The word "authorized" carries the weight here. Microsoft's setup documentation says the Expense Agent permission sets must be assigned to the company being configured, or to all companies. It also says equivalent object permissions don't satisfy that prerequisite. Switching will presumably only help where the groundwork is already in place.
Why multi-company users should care
Microsoft Learn describes the Expense Agent as an AI-powered feature for Business Central online. It includes a dedicated web app for people who don't use Business Central, so employees can submit expenses without a Business Central license. The web app needs only a registered Expense User with a Microsoft Entra ID, according to the Learn documentation.
That audience matters here. Business Central's own company switcher serves licensed ERP users. Companies in Business Central online exist in environments, and someone with access to companies in different environments must specify the environment when signing in. The roadmap item suggests the Expense Agent web app is getting similar flexibility. That is my inference from the two descriptions, not something Microsoft states. The people who benefit most are likely to be:
- Employees who work for several subsidiaries.
- Shared-service finance staff.
- Consultants or controllers who review expenses across entities.
Microsoft doesn't quantify any time savings or error reduction.
Product context
The Expense Agent is still a young feature. Microsoft's documentation labels it a production-ready preview and says the article is prerelease and subject to change. The workflow runs in these steps:
- Receipt intake through the web app, the mobile app or a monitored shared mailbox.
- Data extraction.
- Categorization and itemization.
- Expense creation.
- Monthly expense report creation.
- Submission for approval.
- Approval policy validation.
- Posting of approved reports.
Users must review the agent's extracted data before submitting a report. Business Central still handles audit trails and posting logic, and existing rules, permissions and workflows continue to apply.
On cost, Microsoft's documentation says the agent consumes Copilot Credits, roughly 50 per processed receipt. The Learn page states 50 credits per receipt, regardless of complexity. That is the existing billing model, and the switching roadmap item doesn't mention any change to it.
Practical guidance for administrators
Nothing needs doing before this ships. Administrators who expect to use it can prepare now:
- Audit company access. Check which users hold the Expense Agent permission sets in which companies, or in all companies.
- Review agent configuration per company. Assisted setup covers submission channels, accounting defaults, rules and policy settings. Check these in each company users will switch between.
- Check billing setup. Microsoft says billing must be set up for the Business Central environment before the agent is used.
- Plan testing for preview. If you join the January 2027 preview, test one thing first: confirm that switching shows the right company's categories, defaults and policies, and that nothing carries over from the previous context.
- Keep expectations scoped. The entry covers the web app only. Don't assume the same behavior in the mobile app, email intake or Outlook.
Bottom line
The change is modest, but it targets a real annoyance for organizations with several legal entities. It also leaves open the questions that matter most in finance, such as draft handling and which company is active when a receipt is submitted. Those answers should come with the January 2027 preview, if the schedule holds.