Microsoft Fabric IQ Region Availability - Why It Matters Before You Build

There's a particular kind of project meeting I've sat in more than once. The team has spent weeks designing a clever data and AI solution, the architecture diagram is beautiful, everyone's keen, and then someone from legal or risk asks one question that stops the room: "where does the data actually live?" If the answer is "we're not sure" or "somewhere overseas," the next hour is spent unpicking a design that might not be allowed to ship. Region availability is the boring infrastructure detail that quietly decides whether a project is viable at all, and for a newer service like Microsoft Fabric IQ, it's the first thing I check, not the last.

This isn't a glamorous topic. Nobody puts "we checked which Azure regions the feature supports" on a highlight reel. But for Australian businesses, especially in government, financial services, healthcare, and anyone handling personal information under the Privacy Act, region availability isn't a footnote. It's a gate. So let me walk through why it matters, what to look for, and how to avoid building something you then have to unbuild.

What Fabric IQ is, briefly

Fabric IQ is the layer in Microsoft Fabric that holds the meaning of your business. It's where you define an ontology, the concepts and relationships that describe what your organisation actually means by "customer," "order," "active account," and so on, in a way that both people and AI agents can read. The point of it is to give AI a reliable, shared definition of your business so that when a Copilot or a data agent answers a question, it's working from your real definitions rather than guessing.

It's a relatively new part of the Fabric stack, and like most new cloud capabilities, it doesn't light up in every Azure region on day one. Microsoft rolls these things out region by region, and that rollout schedule is the thing you need to understand before you design around it.

Why region availability is the first question, not the last

Here's the order most teams do it in, and it's the wrong order. They design the solution, build a prototype, get excited, and then check whether the service is available in the region they need. By then they're emotionally and financially committed, and if the region isn't supported, they've got an awkward problem.

Do it the other way around. Before you commit to building on Fabric IQ, confirm three things.

First, is the feature available in an Australian region at all? Microsoft operates several Australian regions, and not every service or preview feature is available in all of them at the same time. A capability that's generally available in Australia East might still be rolling out, or absent, in Australia Southeast. For a newer feature, this gap is wider than people expect. Don't assume "it's in Australia" means "it's in the Australian region we use."

Second, where does the data that powers it physically reside? This is the one that matters for compliance. If your ontology and the data it references must stay within Australia for legal or contractual reasons, you need the service running in an Australian region, full stop. A service that's "available to Australian customers" but processes data in another country is not the same as a service that keeps your data onshore. Those are very different answers to the question your risk team is going to ask.

Third, does the AI processing happen in the same region as the data? This is the subtle one that trips people up with AI features specifically. The data might sit in an Australian region while the AI model that processes it runs somewhere else. For some organisations that's fine. For others, particularly in government and regulated industries, the processing location matters as much as the storage location. Check both, because they aren't always the same.

We've had clients where the answer to one of these three was "no," and the entire approach had to change. Far better to find that out in a planning session than after you've built three months of work on a foundation that legal won't sign off.

The data residency reality for Australian businesses

Data residency in Australia is not a vague preference. For a lot of our clients it's a hard requirement written into contracts, procurement rules, or regulation. Government agencies often have explicit data sovereignty obligations. Financial services firms have APRA's expectations to consider. Health providers have their own constraints under privacy and health records legislation. "The data must stay in Australia" is a sentence I hear in the first meeting on a lot of engagements, and it's non-negotiable when it comes up.

This is exactly why region availability for a feature like Fabric IQ matters so much. The whole value of the ontology is that your real business data and definitions flow through it. If that processing happens offshore, you may have created a compliance problem that's far more expensive than any benefit the feature delivers. The technology being capable is necessary but not sufficient. It also has to be capable in a region you're allowed to use.

The good news is Microsoft has invested heavily in Australian regions and generally brings significant services onshore. The caveat is timing. New features and preview capabilities often land in the larger US and European regions first, and Australian availability can follow by weeks or months. So the question is rarely "will it ever be available here" and more often "is it available here yet, today, for the region we need."

How to actually check

Don't rely on a blog post, including this one, for the current state of region availability. These things change constantly. A feature that's preview-only in an Australian region this month might be generally available next month. What I do on every engagement is go to Microsoft's own region availability documentation for the specific feature, confirm the current state for the exact Australian region the client uses, and screenshot it with the date for the project record. That last bit sounds fussy, but when a compliance reviewer asks "how do you know the data stays onshore," having a dated reference from Microsoft's own documentation is a much stronger answer than "someone told us."

I'd also recommend confirming directly rather than inferring. If region availability is genuinely make-or-break for your project, and for regulated clients it usually is, get it confirmed in writing through your Microsoft account team or partner rather than reading it off a page and hoping you interpreted it correctly. Preview features in particular can have caveats about data handling that aren't obvious from a one-line availability table.

What this means for how you plan

The practical upshot is to make region availability a checkpoint right at the start of your planning, before the architecture is locked. We build it into the early scoping of any Fabric or AI project as a deliberate gate. If the feature isn't available in the region you need, you've got three honest options: wait for the rollout if your timeline allows, redesign around a capability that is available onshore today, or escalate through your Microsoft relationship to understand the rollout timeline before you commit.

None of those are bad outcomes. The bad outcome is discovering the constraint after you've built. We've helped clients sequence Fabric and AI rollouts specifically around what's available onshore now versus what's coming, so the early work happens on solid ground and the newer capabilities get added as they land in the right region. That sequencing is a big part of what good Microsoft Fabric consulting looks like in practice, and it's why we treat region availability as a planning input rather than an afterthought.

It also shapes the broader AI strategy conversation. There's no point designing an ambitious agent or Copilot programme on top of a feature that can't legally run where your data has to live. Getting the residency and region picture clear early means the strategy is grounded in what you can actually deploy, not just what's technically possible somewhere in the world.

For the current, authoritative state of which regions support Fabric IQ, go straight to the source: the Fabric IQ region availability documentation. Check it for the exact region you intend to use, and check it close to when you're actually building, because the rollout moves.

If you're an Australian business weighing up Fabric IQ and you need to be sure the data residency story holds up before you invest, that's exactly the kind of thing we sort out early so it doesn't derail the project later. Get in touch and we'll help you check the ground before you build on it.