Azure Malaysia West Region: Data Residency for Fabric and Copilot

Malaysia West is Microsoft's first Azure cloud region in Malaysia, announced on 28 May 2025 in Greater Kuala Lumpur with three availability zones. Regional Azure services you deploy there keep their data in Malaysia. Microsoft Fabric, Microsoft 365 and the Copilot features each follow their own residency rules, though, so "we use the Malaysia region" rarely covers your whole estate.

At a glance (checked October 2026)

What Malaysia West is

Microsoft announced Malaysia West as an AI-ready hyperscale region with three availability zones and in-country data residency. The official Azure regions list shows it with the programmatic name malaysiawest, physical location Kuala Lumpur, geography Malaysia, three zones and no paired region.

That last detail matters more than most teams expect. Older regions such as Southeast Asia (Singapore) have a pair that some services use for geo-redundant copies. Malaysia West is a nonpaired region, so resilience inside the country comes from spreading resources across its three availability zones. If you add a second region for disaster recovery, that region will be outside Malaysia, and your residency position changes with it.

An upcoming region in Johor Bahru, called Southeast Asia 3, was announced in November 2025. In October 2026 it does not appear in the Azure regions list, so treat it as a future option and check the list before you plan around it.

What data residency actually means

Data residency is about where your data is stored and processed. It is not the same as compliance, and it is not the same as sovereignty. Three distinctions help.

• Data at rest versus data in processing. A database can sit in Kuala Lumpur while a feature that reads it, such as an AI assistant, sends prompts to another country.
• Customer data versus metadata. Many services keep names, permissions or telemetry in a different place from the content itself.
• Regional versus non-regional services. Microsoft's data residency page for Azure explains that most Azure services let you choose the region, and that customer data then stays in the selected geography. Non-regional services and preview services are the exceptions: previews typically store data in the United States.

Malaysian law adds its own layer. The Personal Data Protection Act 2010 has rules on transferring personal data outside Malaysia, and regulated sectors have more. Banks and insurers, for example, work under Bank Negara Malaysia's Risk Management in Technology (RMiT) policy, and Azure Policy includes an RMIT Malaysia built-in initiative that maps some controls, although that mapping is only a partial view of compliance. This article is general information, not legal advice. For the PDPA basics, see our guide to PDPA and AI tools at work.

Which Azure services run in Malaysia West

Not every Azure service launches in every region at once. Before you design anything, open Microsoft's products by region page and confirm each service you need, including the supporting ones people forget: Key Vault, Log Analytics, Backup, Private Link and your chosen virtual machine sizes. Where the page is unclear, ask your Microsoft account team or partner in writing.

Two practical controls help once you decide:

1. Restrict where people can deploy. The built-in Azure Policy "Allowed locations" lets you limit resource creation to malaysiawest, so nobody spins up a test database in another country by accident.
2. Check the AI deployment type, not just the region. For generative AI models in Microsoft Foundry, the model region availability page explains three options. Global deployments may process prompts in any Azure region where the model runs. Data Zone deployments process within a zone such as Asia Pacific. Standard (regional) deployments process in the region you deploy to. Check whether the model you want is offered in Malaysia West at all before promising in-country AI processing.

Microsoft Fabric and Power BI in Malaysia West

The Fabric region availability page lists Malaysia West with Power BI and all Fabric workloads. The one exception noted in October 2026 is Fabric App, which is in preview.

Know your home region first

Every Fabric tenant has a home region, set when the tenant was created. Many Malaysian tenants were created long before Malaysia West existed. To check yours, sign in to Fabric, open Help, select About, and read the value next to "Your data is stored in".

Use a Malaysia West capacity for the workspaces that matter

You do not have to move the whole tenant. With Multi-Geo for Fabric, you create a Fabric capacity in Malaysia West and assign workspaces to it. Compute and storage for those workspaces, including OneLake, then sit in that region.

Read the limitations before you commit:

• Some tenant metadata stays in the home region, including dashboard and report metadata, permissions, semantic model credentials and the service buses used for gateway queries and scheduled refresh.
• Workspaces that contain non-Power BI Fabric items, such as lakehouses and warehouses, cannot be moved between regions. You must delete those items first.
• Large semantic model storage format models should not be moved out of the region where they were created.
• Some features, such as data alerts and screenshots, process data in the home region.

The practical lesson: pick the region before you build lakehouses, not after.

Copilot in Fabric: where your prompts go

This is the point most residency plans miss. According to Microsoft's Copilot in Fabric overview, the Azure OpenAI service behind Copilot in Fabric runs in US datacentres and in the EU Data Boundary. For a capacity in Asia, including Southeast Asia, prompts and results are processed outside the capacity's geography.

For that reason Copilot is off by default for these capacities. A Fabric admin must turn on the tenant setting that allows data sent to Azure OpenAI to be processed outside your capacity's geographic region. What is sent includes your prompts, system prompts, schema information and conversation history. Table content is not sent unless you direct Copilot to use it. For Copilot in notebooks and Fabric data agents, conversation history is kept for 28 days unless a user clears it.

Decide this deliberately. Ask your data protection officer whether schema and prompt text count as personal or confidential data in your context, record the decision, and limit Copilot to the workspaces and groups that need it.

Microsoft 365 and Microsoft 365 Copilot

Microsoft 365 has its own datacentres in Kuala Lumpur, and Malaysia is one of its Local Region Geographies. That does not mean your tenant's data is committed to stay there.

The comparison of Microsoft 365 data residency offerings shows that for Malaysia, a durable in-country commitment is available only through Multi-Geo or Advanced Data Residency (ADR). Malaysia is not one of the countries covered by the standard Product Terms commitment. Both options are paid add-ons: ADR must cover all eligible paid seats, and Multi-Geo requires licences for at least 5% of eligible users. Without either, Microsoft stores the data where it can deliver the service, and that location can change.

To see where your data is today, a global admin can open the Microsoft 365 admin center and go to Settings, Org settings, Organization profile, Data location.

For Microsoft 365 Copilot, ADR covers the content of interactions, meaning prompts and responses stored at rest. Processing is a separate question. In November 2025 Microsoft announced in-country processing for Copilot and listed Malaysia among the countries planned for 2026. An editor's note added in April 2026 revised the plan: it names Australia, India, the United Arab Emirates, the United Kingdom and the United States for the end of 2026, Canada for 2027 and Japan for 2028, and does not mention Malaysia. So do not assume Copilot prompts are processed in Malaysia today. Anthropic models used in Copilot are also currently excluded from in-country processing commitments, according to the enterprise data protection page.

If you are still choosing Copilot licences, our comparison of Copilot Chat and Microsoft 365 Copilot for Malaysian SMEs covers the licensing side.

Questions to ask before moving workloads

Work through these with IT, legal and the business owner of each system:

1. What data is in scope? List personal data, financial records and anything a regulator or client contract restricts.
2. Which services make up the solution? Include monitoring, backup, identity and AI components, then confirm each one is regional and offered in Malaysia West.
3. Where is your Fabric home region and your Microsoft 365 data location? Write both down; they are often different.
4. Which features process data elsewhere? Copilot in Fabric, Microsoft 365 Copilot and global AI deployments are the usual candidates. Get each one approved or switched off.
5. What is your disaster recovery plan? Zone redundancy keeps copies in Malaysia. A second region does not.
6. Where do logs and backups go? Diagnostic settings, exports and backup vaults can send copies out of the region without anyone noticing.
7. Are you relying on previews? Preview services carry weaker residency terms.
8. What does the contract say? Keep the Product Terms, Data Protection Addendum and any add-on terms on file with your decision.

How CertTulen Academy can help

If your team is planning a move to Malaysia West, start with the fundamentals of regions, availability zones and Azure Policy in Azure Fundamentals (AZ-900). Analytics teams building Fabric capacities, workspaces and semantic models should look at Microsoft Fabric Analytics Engineer (DP-600). CertTulen Academy runs both as live, MCT-led classes with hands-on labs, or as private cohorts for your team. CertTulen is an HRD Corp accredited training provider, and many of its professional courses can be claimed by HRD Corp registered employers, so ask us which courses are claimable. Contact us or WhatsApp +60 16-241 8686.