Get the newsletter
Microsoft · Software · Filed Mar 28, 2025 · USPTO published Oct 1, 2026 · Oct 1 release

Microsoft Patents a System That Runs a Secret Copy of Your Job to Test New Software

Every time Microsoft wants to update a cloud service, it risks breaking something for real customers. This patent describes a way to run a duplicate of your actual job against the new version, without you ever knowing, and without putting your real results at risk.

A server infrastructure runs a customer's job and a secret copy of the job to test new software, with customer consent. Drawing from patent filing US 2026/0300143 A1.
A server infrastructure runs a customer's job and a secret copy of the job to test new software, with customer consent.All 6 drawings ↓
Publication number
US 2026/0300143 A1(US20260300143A1)
Applicant
Microsoft Technology Licensing, LLC
Filed · Published
Mar 28, 2025 · Oct 1, 2026
Inventors
Akshat BORDIA, Arijit TARAFDAR, Xiaoqiao LI, Sumeet KHUSHALANI, Kishore Raghavan CHALIPARAMBIL
Status when we published
Waiting for an examiner
Document
20 claims
US classification
717/124

What Microsoft's shadow-job testing system actually does

Cloud services get updated constantly, and every update is a gamble. Before this kind of system, engineers had to test changes on fake or synthetic workloads that never quite matched what real customers actually sent in.

Microsoft's patent describes a process where, when you submit a job to one of its cloud services, the system secretly makes a copy of that request. Your original job runs normally on the current, stable version of the service. The copy, called a shadow job, gets routed to a second version of the service that's running experimental or updated software. Both jobs use your real data, but only your original job's results are ever delivered to you.

Afterward, Microsoft collects performance and output data from both runs and compares them. That comparison tells engineers whether the new version behaves correctly and performs better, all without exposing you to any risk from the experiment.

From the filing · CLAIM 1
… create a copy of the customer job request as a shadow job request for a shadow job; provide the customer job request to a first service having a first configuration to enable the first service to execute the customer job based on first data of the customer to generate first results …

Translation: The system duplicates a user task so it can run a hidden twin version alongside the real one.

How the flighting service picks jobs and compares outcomes

When a job request arrives (think: a batch data processing task, a model inference call, or any scheduled compute workload), the system immediately creates an exact copy of that request before routing it anywhere.

The original request goes to a first service running the current production configuration. The copy goes to a flighting service, which is a routing layer that checks whether this particular job meets certain criteria before deciding what to do with it. Flighting is an industry term for gradually rolling out a change to a subset of traffic, the way airlines test new boarding procedures on select flights.

If the shadow job passes the flighting criteria (which could be based on job type, size, customer tier, or other factors), it gets forwarded to a second service running a different configuration, such as a newer software version or a different hardware setup. Both jobs run using the customer's actual input data.

  • The customer receives results only from the first, stable service.
  • The second service produces its own results independently.
  • Execution data from both runs is collected and stored for comparison and analysis.

The key design point is that the shadow job is invisible to the customer: it runs in parallel, costs the customer nothing extra, and never overwrites the customer's real output.

From the filing · THE ABSTRACT
A received customer job request for a customer job is copied to create a shadow job request for a shadow job. The customer job request is provided to a first service having a first configuration, and the shadow job request is provided to a flighting service.

Translation: Incoming work tasks are automatically cloned and routed to a testing environment behind the scenes.

What this means for Microsoft cloud customers and reliability

For Microsoft, this is a way to gather real-world performance data on new software configurations without staging risky public rollouts. Instead of relying on synthetic benchmarks that may not reflect actual usage, engineers get a direct, apples-to-apples comparison using genuine customer workloads.

For cloud customers, the practical effect is safer, more reliable updates over time. If the shadow results consistently match or beat the production results, Microsoft can roll out the new configuration with much higher confidence. If they diverge, engineers catch the problem before anyone's actual workflow is affected. The tradeoff is that Microsoft is running your job twice, which has a real infrastructure cost that customers don't pay but Microsoft absorbs.

Microsoft's 495th filing in our Microsoft coverage since May adds to a run that includes compressing AI math tables and camera-based AI answers.

Source: US 2026/0300143 A1 at the USPTO (PDF). Full patent text and figures are in the official publication.

Get our take in your Top Stories

Liked this breakdown? Add Patentlyze as a preferred source on Google, and our plain-English take shows up more often in your Top Stories the next time Microsoft patent news breaks.

There are more where this came from

We read every patent application Big Tech publishes and send you the ones worth knowing. Plain English, free, every week.

The drawings · 6 sheets

6 drawing sheets from US 2026/0300143 A1 · click any drawing to enlarge

Server infrastructure for job processing., drawing sheet 1 from US 2026/0300143 A1
Sheet 1 Server infrastructure for job processing.
Server infrastructure with customer consent., drawing sheet 2 from US 2026/0300143 A1
Sheet 2 Server infrastructure with customer consent.
Steps for running a shadow job., drawing sheet 3 from US 2026/0300143 A1
Sheet 3 Steps for running a shadow job.
Validating a second service configuration., drawing sheet 4 from US 2026/0300143 A1
Sheet 4 Validating a second service configuration.
Determining shadow job flighting criteria., drawing sheet 5 from US 2026/0300143 A1
Sheet 5 Determining shadow job flighting criteria.
Computing device and network architecture., drawing sheet 6 from US 2026/0300143 A1
Sheet 6 Computing device and network architecture.
Patent filing page

Reader comments

No comments yet

Start the discussion

Real name or a handle, either is fine. Comments are read by a person before they appear, so allow a little time. Keep it about the filing.