Introduction
Copilot in Microsoft Dynamics 365 Business Central can draft text, summarize records, and now power AI agents that handle real finance and sales work. For companies operating in Japan, however, one question comes up before any rollout: where does our data go when Copilot processes it? The answer depends on how your environment is hosted, a single admin setting, and the Microsoft products involved. Understanding these rules early helps IT, finance, and compliance teams adopt Copilot confidently instead of discovering a surprise during an audit.
This blog will cover the following points
- Why Copilot needs data movement across regions
- How the “Allow data movement” toggle works
- What happens to data from Japan-hosted environments
- Privacy commitments and what the toggle does not control
- How Microsoft 365 Copilot residency differs
- A practical compliance checklist and how Sysamic can help
Why Copilot Moves Data
Copilot in Business Central relies on Azure OpenAI Service, which runs only in specific Azure regions. When your Business Central environment sits in one geography and the nearest AI endpoint sits in another, a prompt and its related data may need to travel across regions to be processed. Microsoft handles this through a clear consent step rather than doing it silently.
The Allow Data Movement Toggle
On the Copilot & agent capabilities page, administrators will find the “Allow data movement” toggle. According to Microsoft Learn, it is switched on by default, which lets Copilot work without extra setup. It applies only when a capability might process data in a different Azure geography. Turning it off blocks cross-region transfer, but it also makes the affected Copilot and agent features unavailable to your organization. Changing it requires SUPER permission or an administrator role such as Dynamics 365 Administrator.
What This Means for Japan
Environments hosted in Japan (East or West) are listed among the geographies that require this consent. Microsoft’s documentation states that for these environments Copilot processing takes place in the United States. In other words, if you leave the toggle on, data from your Japan-hosted environment can be processed outside Japan. If you turn it off, data stays in the geography, and so does the loss of Copilot features. There is no middle setting today, so the decision is a direct trade-off between AI capability and strict residency.
Privacy Commitments
Microsoft states that prompts and outputs are stored for up to 24 hours for abuse monitoring only, that data is not used to train Azure OpenAI models, and that review is automated unless content is flagged. These commitments matter, but they do not replace your own assessment. Companies handling personal data should also review obligations under Japan’s Act on the Protection of Personal Information (APPI) on cross-border transfers, ideally with legal counsel.
A Common Misunderstanding
The Business Central toggle governs only Business Central Copilot and agent capabilities that use Microsoft-managed AI resources. It does not configure tenant-level settings for Microsoft 365 Copilot. Microsoft 365 Copilot follows its own data residency commitments, and Japan appears among the countries and regions with in-country options for certain content, subject to conditions such as the tenant’s default geography. Teams should check each product separately.
A Practical Checklist
First, confirm your environment’s Azure region in the Business Central admin center. Second, classify the data Copilot is likely to touch, such as customer names, pricing, and payroll details. Third, decide with compliance and legal whether the toggle stays on. Fourth, document the decision and review it as Microsoft expands regional availability.
Conclusion
Copilot adoption in Japan is not blocked by data residency, but it does require an informed decision. Knowing that Japan-hosted environments rely on processing in the United States, and that the toggle is all or nothing, lets you plan governance properly.
Sysamic K.K. is a Tokyo-based Microsoft Dynamics 365 Business Central partner with more than 20 years of experience helping international companies run compliant, well-configured ERP operations in Japan. We help you review your environment region, assess Copilot’s data flows against your compliance requirements, configure capabilities and permissions, and roll out AI features in a controlled way. If you want clarity before switching Copilot on, we would be glad to help. Email us at info@sysamic.com or fill out our contact form here to get in touch.