Onshore vs Offshore for Microsoft Power Platform in Regulated Industries

The onshore versus offshore conversation almost always starts with the rate card, and in a regulated industry that is the wrong place to start, because it skips the question that usually decides the matter. Before cost, there is eligibility: whether offshore delivery is even permitted for the work in question. Teams that start with cost discover the eligibility constraint late, after a vendor is chosen and a plan is built, which is an expensive place to learn it.

Three constraints commonly decide eligibility, and any one of them can settle it on its own.

Data residency. Regulated data is frequently subject to rules, legal or contractual, about where it can physically reside and from where it can be accessed. If the data your Power Platform solution touches cannot leave the country or be accessed from abroad, offshore delivery is not a cheaper option for that work, it is a prohibited one, and the rate is beside the point.

Clearance and personnel eligibility. Work that touches controlled or sensitive environments often requires personnel who meet specific eligibility standards, including US-person status or security clearances. Where that applies, the pool of who can do the work is defined by eligibility, not by cost, and offshore staff are simply not in it.

Specific compliance regimes. ITAR governs access to controlled technical data by nationality, which directly constrains who may work on affected systems. CMMC and comparable frameworks impose handling and access requirements that offshore access can violate. When the work falls under one of these, the framework is load-bearing in the decision, not a checkbox, because it defines the eligible delivery model.

When offshore is genuinely fine. None of this is an argument that offshore delivery is inferior. For work that is truly non-sensitive and unregulated, where no residency rule, clearance requirement, or compliance regime applies, the offshore cost advantage is real and worth taking, and insisting on onshore there is paying for a constraint you do not have.

The honest answer for many regulated organizations is a split rather than a side. A program often has a sensitive core that must stay onshore and a non-sensitive periphery that need not, and the right design routes each accordingly rather than forcing the whole program into one model. The discipline is to determine eligibility first, mark which parts of the work are constrained and which are free, and only then let cost decide among the options that remain. i3 delivers Power Platform with senior US-based teams specifically for the regulated cases where residency and clearance govern, and there the value is eligibility itself, the ability to do the work at all, not a marginal quality claim. Decide eligibility first. Cost is the second question, not the first.

Key Takeaways

• In regulated work, eligibility usually settles the onshore/offshore decision before cost does.
• Three constraints decide it: data residency, clearance and personnel eligibility, and compliance regimes like ITAR and CMMC.
• Where any of those apply, offshore is not a cheaper option for that work, it is a prohibited one, and the rate is irrelevant.
• Where work is genuinely non-sensitive and unregulated, offshore’s cost advantage is real and worth taking.
• The honest answer is often a split: a sensitive core onshore, a non-sensitive periphery wherever cost favors. Determine eligibility first, then let cost decide what remains.

Frequently Asked Questions

Is offshore Power Platform delivery cheaper?

On the rate, often yes. In a regulated industry the prior question is eligibility, because data residency, clearance, or compliance rules frequently prohibit offshore delivery for the sensitive work regardless of rate.

What makes work ineligible for offshore delivery?

Any of three constraints: data that cannot legally or contractually leave the country or be accessed from abroad, work requiring cleared or US-person personnel, and compliance regimes like ITAR or CMMC that restrict who may access the systems.

When is offshore the right choice?

For work that is genuinely non-sensitive and unregulated, where no residency, clearance, or compliance constraint applies. There the cost advantage is real and insisting on onshore is paying for a constraint you do not have.

Do we have to choose one model for the whole program?

Usually not. Many programs have a sensitive core that must stay onshore and a non-sensitive periphery that need not. The right design routes each part accordingly rather than forcing the whole program into one model.

How should we make the decision?

Determine eligibility first. Mark which parts of the work are constrained by residency, clearance, or compliance, and only then let cost decide among the delivery options that remain eligible.

If you are weighing offshore delivery to control cost, the first thing worth establishing is which parts of your work are even eligible for it under your residency, clearance, and compliance obligations. Bring us the program and we will mark the constrained core and the unconstrained periphery, so the cost decision happens only where it is actually allowed to.

About the Author

Michael Branson, Founder and COO, i3solutions.