Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
151228 stories
·
33 followers

Microsoft Open-Sources Industry-Leading Embedding Model

1 Share

We’re excited to announce an industry leading open-source embeddings model built to support the agentic web.
 
As AI systems evolve from answering questions to acting, grounding is the foundational capability that drives user trust for any AI agent. The ability to provide the right level of information, at the right time, at the right context. At the heart of grounding is the embedding model: the layer that does the hard work of searching, retrieving, organizing, and connecting information across diverse sources into a coherent, meaningful response.

It’s for this reason, we’re excited to announce we’ve open-sourced our industry leading embeddings model built to support the agentic web. 

Grounding quality is determined long before a model produces its final answer. In production systems, stronger embeddings translate into higher factual accuracy through better first-pass retrieval, lower latency and cost through fewer retries and smaller contexts, and more stable agent behavior across multi-step tasks.

In the agent era, this capability matters even more. Agents must search across diverse sources, maintain memory over time, and update context across multiple steps. In these environments, embeddings are not just a retrieval primitive. They are a foundational layer for memory, ranking, and orchestration.

Enter Harrier.

Harrier is a new embedding model series designed for the demands of modern AI systems. It is our latest open-source text embedding model series, delivering state-of-the-art performance and ranking 1st on the multilingual MTEB-v2 benchmark (as of April 6, 2026). This result reflects Microsoft’s sustained commitment to improve grounding quality through advances in embedding models.


(Image source retrieved on April 6, 2026 - cropped for clarity)

Better embeddings lead to better retrieval, surfacing the right information more often and ranking it higher, which in turn can improve the final user experience: often with more accurate answers, fewer hallucinations, better citations, and stronger multilingual performance. In other words, Harrier’s benchmark gains translate into more reliable grounding in real-world systems.

Harrier is designed not only to improve embedding quality in isolation, but to strengthen the full grounding pipeline that modern AI systems depend on. It supports more than 100 languages, offers a 32k context window, and produces fixed-size embeddings for each input, enabling seamless integration with vector search systems.

Technical overview
We started by developing a scalable data pipeline that gathers multilingual text pairs from multiple sources and uses GPT-5 to generate a wide range of synthetic data. This process resulted in more than 2 billion weakly-supervised data examples for contrastive pre-training and over 10 million high-quality examples for fine-tuning. To ensure the highest standards, we applied thorough data filtering and rewrote the data using large language models, when necessary. After preparing the dataset, we trained our flagship model and then used it as a teacher for knowledge distillation, enhancing the performance of smaller embedding models.

Key technical ideas
Building upon our prior work in text embeddings, including E5, Multilingual E5, E5-mistral, and GritLM, we incorporated several approaches to advance the state of text embeddings:

  1. Large-scale contrastive pre-training and fine-tuning. By scaling the dataset size throughout both the contrastive pre-training and fine-tuning stages, we observed consistent improvements in performance.
  2. Synthetic data generation. Utilizing frontier models such as GPT-5, we generated multilingual text pairs at scale, employing a variety of synthesis strategies to enhance data diversity.
  3. Knowledge distillation. LLM-based re-rankers produced high-quality training signals and efficiently filter noisy data. Our smaller models benefit from knowledge distillation, receiving guidance from larger teacher models during training.

Evaluation
We evaluate on the multilingual MTEB v2 benchmark. For deployment on low-end devices, we trained two smaller models: Harrier-OSS-v1-0.6b and Harrier-OSS-v1-270m.

Model Avg Score over 131 tasks Borda Count Rank
MMTEB leaderboard SoTA 72.3 -
Harrier-OSS-v1-27B 74.3 (+2.0%) 1
multilingual-e5-large-inst 63.2 -
Qwen3-Embedding-0.6B 64.3 -
Harrier-OSS-v1-0.6b 69.0 (+4.7%) 10
Embeddinggemma-270m 61.2 -
Harrier-OSS-v1-270m 66.5 (+5.3%) 15

The table indicates that our model outperforms other open-source embedding models. The "Borda Count Rank" reflects the hypothetical ranking as of March 16 and may change with future submissions.

Compared with leading proprietary models, we are operating at the frontier of embedding quality and efficiency.

Model MTEB Multilingual, Mean(Task)
OpenAI text-embedding-3-large 58.92
Amazon.titan-embed-text-v2 60.37
Harrier-OSS-v1-270m 66.55
Gemini Embedding 1 68.33
Harrier-OSS-v1-0.6b 69.01
Gemini Embedding 2(Multi-modal) 69.9
Harrier-OSS-v1-27B 74.27

What comes next
The work behind Harrier is not just a model release. It is part of a broader effort to build the next generation of grounding systems for the agent era.

Drawing on the same core advances, we are developing a new grounding service designed to deliver better retrieval quality, stronger semantic understanding, and more robust context selection at scale. These innovations will also be coming to Bing, bringing the benefits of this new embedding foundation into real user experiences.

The future of capable agents will depend not only on reasoning and generation, but on how effectively they are grounded in the world. Harrier is a meaningful step toward making that possible — and we're just getting started.

Authors: Xiaolong Huang, Liang Wang, Furu Wei, Jingwen Lu, Knut Risvik, Jason Li 

Read the whole story
alvinashcraft
just a second ago
reply
Pennsylvania, USA
Share this story
Delete

Enabling agent-first process redesign

1 Share

Unlike static, rules-based systems, AI agents can learn, adapt, and optimize processes dynamically. As they interact with data, systems, people, and other agents in real time, AI agents can execute entire workflows autonomously.

But unlocking their potential requires redesigning processes around agents rather than bolting them onto fragmented legacy workflows using traditional optimization methods. Companies must become agent first.

In an agent-first enterprise, AI systems operate processes while humans set goals, define policy constraints, and handle exceptions.

“You need to shift the operating model to humans as governors and agents as operators,” says Scott Rodgers, global chief architect and U.S. CTO of the Deloitte Microsoft Technology Practice.

The agent-first imperative

With technology budgets for AI expected to increase more than 70% over the next two years, AI agents, powered by generative AI, are poised to fundamentally transform organizations and achieve results beyond traditional automation. These initiatives have the potential to produce significant performance gains, while shifting humans toward higher value work.

AI is advancing so quickly that static approaches to task automation will likely only produce incremental gains. Because legacy processes aren’t built for autonomous systems, AI agents require machine-readable process definitions, explicit policy constraints, and structured data flows, according to Rodgers.

Further complicating matters, many organizations don’t understand the full economic drivers of their business, such as cost to serve and per-transaction costs. As a result, they have trouble prioritizing agents that can create the most value and instead focus on flashy pilots. To achieve structural change, executives should think differently.

Companies must instead orchestrate outcomes faster than competitors. “The real risk isn’t that AI won’t work—it’s that competitors will redesign their operating models while you’re still piloting agents and copilots,” says Rodgers. “Nonlinear gains come when companies create agent-centric workflows with human governance and adaptive orchestration.”

Routine and repetitive tasks are increasingly handled automatically, freeing employees to focus on higher value, creative, and strategic work. This shift improves operational efficiency, fosters stronger collaboration, and generates faster decision-making—helping organizations modernize the workplace without sacrificing enterprise security.

Download the article.

This content was produced by Insights, the custom content arm of MIT Technology Review. It was not written by MIT Technology Review’s editorial staff. It was researched, designed, and written by human writers, editors, analysts, and illustrators. This includes the writing of surveys and collection of data for surveys. AI tools that may have been used were limited to secondary production processes that passed thorough human review.

Read the whole story
alvinashcraft
11 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

What senses do agents need to act?

1 Share

In this episode of The Shift, members of the Microsoft Foundry team, Ronak, Vinod and Linda explore a question from you, our community:

What senses do agents need to act?

The Shift, Agentic Edition connects the people building AI tools with those creating agents, so we can all level up together.

Get the eBook: AI Apps and Agents | Microsoft Azure

https://aka.ms/AIAppsAgents

Join our community: https://techcommunity.microsoft.com/

Get to know the team:

Ronak Chokshi, Director Product Marketing

https://www.linkedin.com/in/ronakchokshi/

Vinod Valloppillil, Partner Product Director

https://www.linkedin.com/in/vinodvalloppillil/

Linda Li, Product Manager II

https://www.linkedin.com/in/zhuoqun-linda-li/

The Shift podcast is a place for experts to share their insights and opinions. As students of the future of technology, Microsoft values inputs from a diverse set of voices. That said, the opinions and findings of our guests are their own and they may not necessarily reflect Microsoft's positions as a company.

This episode of The Shift was recorded in February 2026. All information about products and offers are relevant to the time of recording.





Download audio: https://content.rss.com/episodes/311843/2695220/leading-the-shift/2026_04_06_23_31_01_4844868d-0c2e-4353-8df2-ff000ea72f45.mp3
Read the whole story
alvinashcraft
4 hours ago
reply
Pennsylvania, USA
Share this story
Delete

Salary Negotiation, Executive Presence & Wealth Building for Working Moms (with Khiara Cureton)

1 Share

Send us Fan Mail

What is hesitation costing you in money, opportunity, and confidence? In this episode, executive career and money coach Khiara Cureton shares how ambitious mothers can negotiate stronger salaries, define non-negotiables, and build wealth without sacrificing family. This conversation blends career strategy and personal finance in a way every working mom needs to hear. 

Connect with Khiara:

 
 
#GettingBlackWomenPaid #GBWPPodcast #PayEquity #SalaryNegotiation #WorkingMoms #WomenAndWealth #BlackWomenInBusiness 


Did you know you can WATCH these episodes on YouTube? Check out the Getting Black Women Paid YouTube channel here.

Check out 'Tine's book here: Overcoming Imposter Syndrome at Work

Connect with 'Tine at tinezekis.com

Follow us on social media:

For more information about the podcast, visit our website: www.GettingBlackWomenPaid.com/podcast

Want to be a guest? Apply here!

Be sure to follow us wherever you're listening now. And don't forget to share this podcast with the incredible Black women in your life, so we can continue Getting Black Women Paid!






Download audio: https://www.buzzsprout.com/2349171/episodes/18793552-salary-negotiation-executive-presence-wealth-building-for-working-moms-with-khiara-cureton.mp3
Read the whole story
alvinashcraft
4 hours ago
reply
Pennsylvania, USA
Share this story
Delete

Error CompileAppManifest Task Failed Unexpectedly

1 Share
Iris Classon - In Love with Code https://www.irisclasson.com/2026/04/07/error-compileappmanifest-task-failed-unexpectedly/ -

Hope you’ve had a lovely Easter! I caught the flu the week before, and am still recovering. Flu plus Easter = I was away for over a week. Which means by the time I came back and did a pull there had been quite a few changes in the work code base. After staring at the screen for two hours running various updates I finally got around to attempting a build, but got the following error:

Xamarin.Shared.targets(614,3): Error
MSB4018 : The "CompileAppManifest" task failed unexpectedly.
System.NullReferenceException: Object reference not set to an instance of an object.
 at Xamarin.MacDev.Tasks.CompileAppManifest.SetXcodeValues(PDictionary plist, IAppleSdk currentSDK) in /Users/builder/azdo/_work/1/s/macios/msbuild/Xamarin.MacDev.Tasks/Tasks/CompileAppManifest.cs:line 534
 at Xamarin.MacDev.Tasks.CompileAppManifest.Compile(PDictionary plist) in /Users/builder/azdo/_work/1/s/macios/msbuild/Xamarin.MacDev.Tasks/Tasks/CompileAppManifest.cs:line 338
 at Xamarin.MacDev.Tasks.CompileAppManifest.Execute() in /Users/builder/azdo/_work/1/s/macios/msbuild/Xamarin.MacDev.Tasks/Tasks/CompileAppManifest.cs:line 166
 at Microsoft.Build.BackEnd.TaskExecutionHost.Execute()
 at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(TaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask)

If you come across this, take a closer look at the error.

The null reference exception is in the SetXcodeValues method, which usually means you have a SDK mismatch. For me it was simply a missing workload update since I was updating my environment:

dotnet workload update

If you get this error, make sure you have the right Xcode version for the MAUI version you are using.

Hope this helps!

Comments

Leave a comment below, or by email. - https://www.irisclasson.com/2026/04/07/error-compileappmanifest-task-failed-unexpectedly/ -
Read the whole story
alvinashcraft
4 hours ago
reply
Pennsylvania, USA
Share this story
Delete

Take full control of your floating windows in Visual Studio

1 Share

If you work with multiple monitors like I do, you’ve probably grown to love floating tool windows and documents in Visual Studio. Being able to pull out Solution Explorer, the debugger, or your code files onto a second (or third) screen can be a huge productivity boost.

But there’s always been a bit of friction with how these floating windows behave.

VSFancyZones image

By default, floating windows are “owned” by the main Visual Studio window. That means they don’t show up as separate buttons in your Windows taskbar, they disappear when you minimize the main IDE, and they always stay on top of everything else — even when you don’t want them to.

For some workflows that’s exactly what you want. For others, it gets annoying fast.

Fortunately, there’s a little-known setting that lets you decide exactly how much control Visual Studio has over your floating windows.

The setting is here: Tools > Options > Environment > Windows > Floating Windows

You’ll see this dialog:

floating windows tools options image

The dropdown is labeled “These floating windows are owned by the main window” and gives you three choices:

  • None
  • Tool Windows (the default)
  • Documents and Tool Windows

Changing this one setting can completely transform how you work with floating windows.

My favorite scenario: PowerToys FancyZones

This setting really shines when you combine it with Microsoft and its excellent FancyZones feature.

I like to set it to None and then use FancyZones to create custom layouts across my monitors. Suddenly all my floating tool windows and documents behave like normal application windows — they appear in the taskbar, stay visible even if I minimize the main Visual Studio window, and I can snap them perfectly into my FancyZones layouts without them forcing themselves to the front all the time.

It feels much more natural and gives me the clean multi-monitor setup I’ve always wanted.

When to choose each option

  • None: Maximum independence. Everything gets its own taskbar entry and full window behavior. Perfect for heavy multi-monitor users with PowerToys.
  • Tool Windows: A nice middle ground — keep your documents floating freely while tool windows stay tied to the IDE.
  • Documents and Tool Windows: The classic Visual Studio behavior.

Pro tip: Combine this with the Ctrl + double-click trick on any tool window title bar (see our earlier post on easily docking and floating tool windows) for lightning-fast layout switching. No restart required.

Have you played with this setting before? What option do you prefer: None, Tool Windows, or the default? Let me know in the comments. I’m always curious how other developers set up multi-monitor workspaces.

Happy coding!

The post Take full control of your floating windows in Visual Studio appeared first on Visual Studio Blog.

Read the whole story
alvinashcraft
4 hours ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories