Microsoft Herzliya Cut: 25 Copilot Studio Engineers Hit a 59-Person Market

On October 12, 2026, Microsoft summoned roughly 50 Copilot Studio employees at its Herzliya R&D center to pre-dismissal hearings. CTech expects about half to exit. That means ~25 engineers who have shipped production agent orchestration, tool-calling, and enterprise connectors are about to hit the Tel Aviv market in a 72-hour window, and the recruiters who wait for "Open to Work" badges will be bidding against Zenity, monday.com, and Frontegg a week too late.

The pool is 25 engineers, and Israel's senior tier is only 59

The headline number is small. The supply shock is not. In Refolk's index of professional profiles, 1,303 people in Israel reference "AI agent" in their current role, but only 59 of them are senior-level or above and actually building LLM agent systems. The Microsoft Copilot Studio cohort could expand that senior pool by roughly 42% in one week.

The gap between those two numbers is the whole story. Most "AI agent" headlines in Israel belong to founders, EIRs, and CEOs, not shipping engineers. The top titles in the Israeli slice of the index skew heavily toward Co-Founder and CEO, which is why the raw 1,303 is misleading as a supply figure. Hiring managers who have been told "there is plenty of AI agent talent in Tel Aviv" are reading the founder count, not the builder count.

59

Here is the full market as it stood the morning of the hearings:

A single competitor hiring 5 to 10 engineers out of this cohort materially moves the senior-agent market in Israel for the next twelve months. That is the frame.

Pre-dismissal hearing is the sourcing window, not the layoff

A pre-dismissal hearing is the Israeli employment-law step where an employer formally notifies an employee their role is at risk and gives them a chance to respond before any dismissal is finalized. It is not a layoff. It is the week before the layoff, which is exactly why it matters for sourcing.

Microsoft has said publicly it will try to place affected engineers into other internal roles. Some will take those offers. The ones who do not are the pool, and they are reachable right now, before severance paperwork is signed and before anyone flips a LinkedIn status. Israel Hayom reports the process could take effect as early as Monday evening, with a one or two day delay possible depending on reporting requirements from Microsoft's US HQ.

The mechanical implication for recruiters:

• Outreach timed to the hearing week catches engineers while they are actively evaluating options, not after they have accepted a weaker internal transfer out of risk aversion.
• "Laid off from Microsoft" posts on LinkedIn will not appear for 2 to 6 weeks. By the time they do, Zenity and monday.com will have made offers.
• Severance terms in Israel typically include a notice period during which engineers can interview. Starting conversations now puts you inside that notice period rather than racing to catch it.

This is the exact gap Refolk closes. You describe the person you want ("Herzliya-based engineers who worked on Copilot Studio tool-calling or enterprise connectors in the last 24 months") in plain English and get a ranked shortlist across GitHub, LinkedIn, and the open web, rather than waiting for public layoff signals.

The leadership vacuum will push exits past 50%

Expect the actual exit rate to run higher than CTech's roughly 50% estimate, probably 60 to 70%, because the internal transfer sponsors are not in their seats. Michal Braverman-Blumenstyk, who led Microsoft Israel R&D for six and a half years, is stepping down. Her successor Ohad Jassin does not take over until November.

That matters because internal transfers at a company Microsoft's size depend on senior sponsorship: a VP who vouches for an engineer landing softly in an adjacent org. During a leadership handover, those sponsorships are weaker. Fewer transfers get championed. More engineers get told "we are looking but nothing clean yet" and start taking recruiter calls.

If you are modeling the pool, use ~30 exits as your working number, not 25. And weight it toward the engineers who were working on the parts of Copilot Studio that are furthest from Microsoft's remaining Israeli priorities, because those are the ones with the fewest obvious internal landing spots.

A hearing is not a layoff. It is the two weeks you get before every other recruiter notices.

What these engineers actually built

Copilot Studio is Microsoft's platform for enterprises to build and operate AI agents that carry out business functions automatically. The engineering surface area that distinguishes it from a thousand GPT wrappers is tool invocation at enterprise scale: auth into existing enterprise systems, policy-constrained action, multi-step orchestration with audit trails.

That is a scarcer skill than fine-tuning or prompt engineering, and it does not map to generic "AI engineer" job descriptions written by companies that have never shipped an agent into a Fortune 500 tenant. The teams this cohort fits are:

• Agentic workflow platforms selling into regulated enterprise buyers.
• Security and governance layers for agent builders (Zenity's entire thesis).
• Vertical AI products that need to call into existing enterprise systems rather than replace them.
• Internal platform teams at large enterprises building their own agent orchestration.

It is the wrong pool for a frontier model lab. It is the right pool for anyone who has lost a deal because their agent could not reliably update a record in a customer's CRM.

Where they will land if you do not call first

Five Israeli employers show up repeatedly in Refolk's index as the current home of senior AI-agent engineers, and they are the natural bidders for this cohort. In order of strategic fit:

1. Zenity (Tel Aviv). Its entire product is security and governance for Copilot Studio and other agent builders. Hiring the engineers who built the thing you secure is both strategically obvious and defensively critical. Assume outreach is already underway.
2. monday.com. Shipping AI agent features inside its work OS. Can pay, has brand, and will absorb 3 to 5 of this cohort without blinking.
3. Frontegg. Enterprise auth and user management, which is adjacent to the enterprise-connector problem Copilot Studio engineers already solved.
4. Coralogix. Observability for AI systems; a reasonable landing spot for the ops-leaning engineers in the cohort.
5. Aurora Labs, Aleph, Beamup, Check Point. The long tail. Each will take one or two.

If your target hire count is more than two engineers from this pool and you are not already on calls, you are competing for seconds. The pool skews to the Tel Aviv, Ramat Gan, Ramat HaSharon, Petah Tikva corridor, which maps cleanly to a Herzliya commute. Remote offers from US companies will play, but local offers from Zenity and monday.com will play faster because they can start Monday without a visa conversation.

The outreach that works this week

The message that gets a reply from a Copilot Studio engineer in hearing week is specific about the work, not the company. "I saw your name on the Copilot Studio connector framework" beats "we are a well-funded Series B building the future of AI agents" by an order of magnitude.

A working template, in rough order of what matters:

1. One sentence naming the specific Copilot Studio surface they worked on (connector SDK, agent runtime, tool invocation, enterprise auth integration).
2. One sentence on the equivalent problem your team is solving, with the enterprise customer or vertical named.
3. One sentence on comp band and location flexibility, because Israeli engineers at Microsoft know the market rate and will not play guess-the-salary.
4. A specific 20-minute slot this week, not "when works for you."

The hard part is step one, because it requires knowing which part of Copilot Studio each engineer owned. GitHub commit history on Microsoft's public repos helps for a subset. The rest requires inferring from conference talks, patents, and internal titles that leak into recruiter LinkedIn.

The macro context, briefly

193,698

Against 193,698 tech layoffs in 2026, 25 engineers is nothing. HoneyBook cut roughly 35 in Israel the same week, reorganizing for the AI era, per Haaretz. The reason this cohort matters is not headcount; it is concentration. The entire Israeli senior AI-agent engineering pool is 59 people. One restructuring just dropped 25 of their peers into the hiring market in a city with eight serious competing employers.

That is not a layoff story. It is a sourcing story with a two-week clock.

FAQ

How many Microsoft Copilot Studio engineers are actually leaving in Israel?

CTech reports approximately 50 employees were summoned to pre-dismissal hearings on October 12, 2026, with estimates that about half will exit, implying ~25 engineers. Expect the real number to run slightly higher, closer to 30, because Microsoft Israel R&D is between leaders (Michal Braverman-Blumenstyk out, Ohad Jassin in November), which weakens internal transfer sponsorship during exactly the window these engineers are deciding whether to accept an alternative role.

Why does a 25-person cut matter when 2026 tech layoffs are near 194,000?

Because the pool it feeds is 59 people. In Refolk's index, only 59 Israel-based professionals are senior-level or above and actually shipping LLM agent systems. 25 ex-Copilot Studio engineers represent roughly a 42% expansion of that senior supply. Measured against the Israeli agent-engineering market specifically, this is one of the largest single-week supply shocks of the year.

Who are the most likely competing employers for this cohort?

Based on Refolk's index of top current employers of Israel-based AI-agent engineers: Zenity, monday.com, Frontegg, Coralogix, Aurora Labs, Aleph, Beamup, and Check Point. Zenity is the most strategically obvious bidder because its product is security and governance for Copilot Studio itself. monday.com and Frontegg will move on volume and brand. US remote offers can compete but will lose to local offers that can start without visa paperwork.

When does the sourcing window actually close?

Practically, you have through the end of October to reach engineers while they are still inside Microsoft's notice period and actively evaluating. After that, the ones who accepted internal transfers are off the market, the ones who exited are already in Zenity's and monday.com's pipelines, and the public "ex-Microsoft" LinkedIn signal appears 2 to 6 weeks after the hearing, which is far too late to be first in the inbox.