Talk by Pablo Castro (Distinguished Engineer & CVP, Microsoft AI Knowledge team) on AI and knowledge systems for building applications and agents. Covers a taxonomy of knowledge for AI systems—Intrinsic (parametric model memory), Extrinsic (grounding agents in corporate/private data via retrieval), and Learned (agent learning loops and self-optimization)—including demos of building a knowledge base with Foundry IQ and Foundry agent optimization, plus the evolution of retrieval systems (Foundry IQ, Azure AI Search, Azure Content Understanding). # Channel Identity Observations: AI and Knowledge — Pablo Castro (Microsoft) ## Video Context - **Format**: Conference talk delivered at the **AI Engineer World's Fair** (stated in transcript: *"It's great to be back here at the AI Engineer World's Fair"*). - **Speaker role**: Pablo Castro, **Distinguished Engineer & CVP for AI Knowledge, Microsoft** (per title; reinforced by transcript: *"my job at Microsoft is to connect the dots between AI and knowledge"*). - **Note**: This appears to be a **guest/keynote presentation at an event**, not a standard channel-produced video. The channel's identity here is that of an **event content publisher** rather than the speaker's own channel — no explicit channel self-description is present in the material. ## Observable Presentation Evidence ### Intended Audience - **Practicing AI/software engineers and agent builders** — demonstrated by: - References to developer workflow specifics: *"we all go and build"* on GitHub, VS Code demos, MCP servers, externalizing agent configuration. - Assumed familiarity with technical concepts used without definition: RAG, cosine similarity, vector indexes, quantization, chunking, hill climbing. - Direct calls to action aimed at builders: *"If you want to try anything of what I talked about or showed today, you can head to ai.azure.com and get going."* ### Claimed Scope / Subject Matter - **AI knowledge systems and enterprise agent grounding**, covering: - A taxonomy of knowledge: **intrinsic** (parametric model memory), **extrinsic** (grounding/retrieval), **learned** (optimization loops). - Microsoft product surface: **Microsoft Foundry, Microsoft IQ (Work IQ, Fabric IQ, Foundry IQ, Web IQ), agent optimizer**. - Evidence: talk structure explicitly states, *"spend a little bit of time talking about the nature of knowledge and split it into these three categories of intrinsic, extrinsic, and learned."* ### Demonstrated Presentation Patterns - **Product-integrated technical demo talks**: - Live laptop demos: creating a knowledge base in Foundry, inspecting indexes in Azure, running agent optimization in VS Code. - **Historical framing to build narrative**: - Timeline from IntelliSense ('96) → ML ranking → GitHub Copilot → Cursor → Opus 4.5 → Open Claw: *"So, this is the shape of the exponential we're in."* - **Vendor perspective with explicit product positioning**: - *"In the context of Microsoft, we want to make available all these models and make it easy for you to integrate them"*; announcement that *"Claude in Microsoft Foundry is generally available."* - **Evidence-based claims style**: cites internal evaluation results, e.g., *"if you combine methods, you just get better results"* with a described evaluation from AI search behind Foundry IQ; agentic retrieval metrics (*"evidence recall or answer completeness"*). ## Explicit Self-Description Claims - **By the speaker (not the channel)**: - *"My job at Microsoft is to connect the dots between AI and knowledge."* - *"As an information retrieval nerd... I spend a lot of time on looking at knowledge representation, extraction, search."* - **By the channel**: none present in the supplied material — no channel-level description, subscribe pitches, or branding statements appear in the transcript or title. ## Distinguishing Claims from Demonstrations | Type | Evidence | |---|---| | **Speaker claim** | Microsoft's layered Foundry IQ design goal: *"let you opt into it when you need control"* | | **Speaker claim** | Agentic retrieval *"continuously does better"* per internal evaluations | | **Demonstrated** | Live product walkthrough of knowledge base creation, index inspection, and optimizer runs | | **Demonstrated** | Audience is technical (event format, unexplained jargon, developer tooling focus) | ## Open Questions for Channel-Level Synthesis - No curated metadata was supplied, so channel identity (event organizer vs. re-uploader vs. media outlet) **cannot be determined from this video alone**. - Whether the channel consistently publishes AI conference keynotes is unverified by this single source. # Delivery Observations — Pablo Castro, "On AI and Knowledge" ## Overall Tone and Register - **Conversational and affable**: The talk is delivered in a casual conference register, marked by frequent interjections of "you know," "like," "and whatnot." > "As an information retrieval nerd, like that's great for me." - **Self-deprecating lightness**: He labels himself a "nerd" and uses informal asides ("for a hot second"). - **Audience-aware framing**: He assumes technical fluency ("we all go and build" in GitHub) but still scaffolds concepts from scratch. ## Recurring Verbal Habits - **"You know"** is by far the most frequent filler — appears dozens of times, e.g., "It's what we uh train the models on, the training data, and what um uh stored in the models' kind of parametric memory." - **"And whatnot"** as a recurring list-closing device: > "documents, your emails, your chat threads, or the information in your data warehouse and whatnot." > "chunking, vectorization, deal with relevance and ranking, deal with agentic retrieval and whatnot." - **"Kind of"** as a hedge/softener: "kind of parametric memory," "kind of late last year," "a kind of a quick flavor." - **Doubled/fragmented words under pace**: "the the the nature," "we we saw," "for for difficult cases" — suggesting faster delivery than speech at those points. - **Hedged claims**: "I would argue" appears at least twice ("I would argue this is the knowledge that actually threw us into the exponential"; "I would argue that GitHub Copilot, ChatGPT…"). ## Structural / Teaching Patterns - **Explicit three-part taxonomy**: He announces a framework up front — "intrinsic, extrinsic, and learned" — and walks through each in turn, with slide transitions ("Next slide," "We go back to slides"). - **Signposting transitions**: "So let's start with company grounding," "The last category of knowledge I wanted to talk about is learned knowledge." - **Personal anecdote as illustration**: Uses his own 25-years-apart code example — "I wrote these two pieces of code about 25 years apart" — to make a conceptual point concrete. - **Timeline narrative for the "exponential"**: Anchors the story in dated milestones (IntelliSense '96, "22 years," "Just 3 years after that," Copilot, Cursor, Opus 4.5, Open Claw). - **Trade-off framing**: Repeatedly presents capability as balancing simplicity vs. control: > "let you opt into it when you need control, but when you have a scenario that is clear, then you can have an easy system." > "a highly productive environment when you… don't need the sophistication, and when you need it to make sure you have it." - **Evidence-driven persuasion**: Cites evaluations to support claims — "what evaluations show over and over again is how… if you combine methods, you just get better results." ## Demo Delivery Habits - **Pre-recorded/pre-run results to save time**: "In this case I run this a little bit earlier," "I run this earlier and so let me show you the output." - **Directing the AV operator aloud**: "Can we switch to the laptop? There you go." / "We go back to slides." - **Minimizing setup details in demos**: "it doesn't matter how you write your agent as long as you externalize configuration." - **Concrete hypothetical phrasing while demoing**: > "you can go to Foundry and say, 'Hey, I have a bunch of, I don't know, PDFs or pictures over there. Just deal with them.'" ## Persuasion and Framing Choices - **Named-product evangelism**: Consistently attaches capabilities to product names (Microsoft Foundry, Microsoft IQ, Work IQ, Fabric IQ, Foundry IQ, Web IQ, agent optimizer), with a news-drop moment: "just yesterday we announced that Claude in Microsoft Foundry is generally available." - **Appeal to authority**: References Satya (Nadella) — "Satya wrote about this recently." - **Closing call to action**: "you can head to ai.azure.com and get going." ## Uncertainty Notes - Filler-word frequency ("you know," "and whatnot") is clearly a stable pattern given repetition; the doubled-word fragments are frequent enough to be habitual but may partly reflect transcript transcription. - No video of body language is observable here; all observations are linguistic only. # Position Record: Pablo Castro on AI and Knowledge **Speaker:** Pablo Castro, Distinguished Engineer & CVP for AI Knowledge, Microsoft **Venue:** AI Engineer World's Fair ## Core Thesis Castro frames his role as "connecting the dots between AI and knowledge," and organizes the talk around a **three-part taxonomy of knowledge**: - **Intrinsic** — knowledge in the model's parametric memory from training - **Extrinsic** — grounded/retrieved knowledge outside the model - **Learned** — knowledge produced by observing and improving work processes --- ## Positions on Intrinsic Knowledge - Castro argues intrinsic knowledge "actually threw us into the exponential we are in today" and seeded agent scenarios. - **Evidence pattern (coding timeline):** IntelliSense (1996) → ML-ranked suggestions 22 years later → GitHub Copilot 3 years after that (a key inflection, pre-ChatGPT) → Cursor/Copilot X → Opus 4.5 late last year → Open Claw with "not a single line of code written by hand" — illustrating the exponential's shape. - Personal anecdote: two codebases written 25 years apart required a "surprisingly similar" process, showing pre-AI stasis in knowledge work. ## Positions on Extrinsic Knowledge - **Company-wide grounding:** Agents need "ambient data" (documents, email, chats, data warehouses) beyond their curated knowledge. Microsoft IQ addresses this as a *set of capabilities*: Work IQ, Fabric IQ, Foundry IQ, and Web IQ (public web grounding). - **Retrieval evolution:** Vector databases initially "unblocked" RAG, but Castro criticizes the industry view that cosine similarity alone sufficed — "things never are that easy." - **Claim:** Evaluations (including from "I search," the search tech behind Foundry IQ) show **combined retrieval methods outperform individual methods**, especially in real-world customer scenarios. - **Agentic retrieval:** For easy cases, single-shot retrieval suffices; for difficult cases, Castro claims agentic retrieval improves metrics like **evidence recall and answer completeness** — phrased tentatively: "can [make] a difference." - **Design philosophy:** Layered system — simplicity by default, expert control (quantization, lexical retrieval, indexing algorithms) available in the same stack. - **Token efficiency** cited as a design goal: "most information dense answer that has the fewest tokens." ## Positions on Learned Knowledge - Agents enable **learning loops** capturing what is "unique about the company," referencing Satya Nadella's recent writing on people and agents compounding. - **Agent optimizer (demoed):** evaluate baseline → generate candidates → evaluate → deploy if improved. Uses hill-climbing over an evaluation rubric; optimized instructions are "not handwritten but emerged out of the hill climbing process." ## Product Announcements / Claims - Claude in Microsoft Foundry is **generally available** ("announced just yesterday"). - Every Foundry knowledge base is an **MCP server**, connectable "without any glue code." - Instructions to try tools: ai.azure.com. ## Qualifications & Caveats Preserved - Retrieval benefit claims are grounded in Microsoft's **own evaluations**, not independent benchmarks. - "For a hot second, as an industry, we thought…" — Castro explicitly notes industry overconfidence in a single technique, a self-critical framing. - Agentic retrieval claims are limited to "difficult cases"; no claim of universal improvement. - No private motivations inferred; all positions are Castro's stated views in a promotional product context. # Speaker Attribution Record ## Video **Title:** On AI and Knowledge — Pablo Castro, Distinguished Engineer & CVP for AI Knowledge, Microsoft **Video ID:** `01a15ca8-a1a1-7593-8a77-07b349099f87` **Event:** AI Engineer World's Fair (stated by speaker: "It's great to be back here at the AI Engineer World's Fair") ## Speakers | Speaker | Role | Evidence | |---|---|---| | **Pablo Castro** | **Creator / Keynote speaker** — CVP and Distinguished Engineer, AI Knowledge, Microsoft | Introduced by unnamed stage announcer; delivers the entire presentation | | **Unnamed announcer** | **Other — introducer** | Opening line: "Now taking the stage is CVP and distinguished engineer at Microsoft, Pablo Castro." | No guests, narrators, or additional speakers appear. ## Referenced Third-Party Sources and Claims - **Satya Nadella** — cited (not quoted) for a recent piece of writing on people and agents compounding and creating learning loops. - **Microsoft products mentioned** (first-party, by speaker): IntelliSense ('96), GitHub, GitHub Copilot, GitHub Copilot X, Microsoft Foundry, Microsoft IQ (Work IQ, Fabric IQ, Foundry IQ, Web IQ), Azure, VS Code, SharePoint, Power BI, agent optimizer, AI Search ("I search", the search technology behind Foundry IQ). - **Third-party products cited as industry milestones**: Cursor, ChatGPT, Claude (in Foundry — "generally available" as of "just yesterday"), Opus 4.5, GPT, "Open Claw" (as spoken; possibly a transcription of another product name). - **Evaluations**: speaker references "an evaluation from actually I search" showing combined retrieval methods outperform individual methods, and internal Foundry evaluations on agentic retrieval and token efficiency. No external published sources cited by title or link. ## Promotional Segments ⚠️ - **Microsoft product walkthroughs** constitute a substantial promotional portion: - Microsoft Foundry demo (knowledge base creation, MCP server, agent connection) - Azure knowledge-base/index configuration demo - VS Code Foundry toolkit / agent optimizer demo - Announcement of Claude general availability in Foundry - **Call to action**: "you can head to **ai.azure.com** and get going." ## Provenance Notes - Timeline claims (IntelliSense 1996, "22 years" to ML ranking, Copilot "3 years after that", Cursor/Copilot X "a couple of years later", Opus 4.5 "late last year") are speaker assertions, uncorroborated in-transcript. - Comment availability: **not specified** in source material. - Speaker self-identifies as speaking on behalf of Microsoft ("in the context of Microsoft, we want to make available..."). \>\> Now taking the stage is CVP and distinguished engineer at Microsoft, Pablo Castro. \>\> Hello everyone. Hello everyone. Good morning. It's great to be back here at the AI Engineer World's Fair. Now, my job at Microsoft is to connect the dots between AI and knowledge. As an information retrieval nerd, like that's great for me. Like I spend a lot of time on looking at knowledge representation, extraction, search, and whatnot. And thinking about agents and knowledge really invites to reflect on, you know, what it means to know something. And uh, you know, the the the nature of how do we get things done based on what we know. Next slide. All right. There. So, this morning what I thought we would do is spend a little bit of time talking about the nature of knowledge and split it into these three categories of intrinsic, extrinsic, and learned. Intrinsic knowledge is just the knowledge that comes with the models. You know, it's what we uh train the models on, the training data, and what um uh stored in the models' kind of parametric memory. And while it's kind of the obvious thing, I would argue this is the knowledge that actually threw us into the exponential we are in today. It's what started many of the scenarios that then grew on all the things we're doing with agents today. Let me give you an example with code. So, I wrote these two pieces of code about 25 years apart. And yet, the process to put this thing together was surprisingly similar. Like I had to sit down with what I knew or what I had to go look up and then just write it up. And while, you know, I'm illustrating this with knowledge, you could say the same thing about, you know, writing an email or creating a summary of a document. Now, you can see this exponential at play in tasks like these where, you know, I'm sure you can go further back. But an interesting point in time to start looking at this would be when Microsoft introduced IntelliSense. That was in '96. And, you know, it was great. You didn't have to remember function signatures anymore and whatnot. It takes 22 years from there to go for the next step where machine learning helps us actually rank the options we give you in IntelliSense, so it's quicker to pick the right choice. Just 3 years after that, GitHub Copilot launches. And that was one key inflection point. This was even before ChatGPT was announced. And, you know, I would argue that GitHub Copilot, ChatGPT, that sort of experiences were heavily grounded on this intrinsic memory, what the models already knew. From there, of course, things shifted. You know, a couple of years later, Cursor launches, GitHub Copilot X launches, and how we do things kind of evolved really quick, which takes us to kind of late last year. Opus 4.5 ships. And then rapid succession, you know, GPT, Opus, and other models keep getting better and better at coding. Which takes us to early this year, where incredibly successful software like like Open Claw comes out to existence with not a single line of code written by hand. So, this is the shape of the exponential we're in. And a lot of this was powered by the by the intrinsic knowledge in models and of course their ability to reason. Now, in the context of Microsoft, we want to make available all these models and make it easy for you to integrate them into the agents you're building. We do this from our agent platform that starts in GitHub where we all go and build. It has a contextualization system so you can ground your agents. And when it comes to agent hosting, observability, and management, we all do all of these in Foundry. Microsoft Foundry is also where we offer thousands of models in our model catalog so you can pick whatever is the right model for the right task. And we keep adding more every day. In fact, just yesterday we announced that Claude in Microsoft Foundry is generally available so you can use all the capabilities of Claude in the context of the unified experience in Foundry. So you get best of both worlds. Now, an interesting model got us here, but it only gets you so far if you're building a system that or an agent that needs to participate in what's happening in an organization or a company. And you know, as an industry we realized this early and we, you know, we saw the the rag pattern emerge. That started as a pretty low-tech technique, but quickly evolved and what we do today with context engineering and you know, it became a pretty sophisticated system for connecting agents and the knowledge they need to get their job done. Of the many dimensions of of which this got kind of complicated, I'm going to pick on two. One is kind of the evolution from simple and isolated data sets to whole company-wide grounding. And the other one is how we started with simple vector search and whatnot and we really saw this evolve into fairly complicated retrieval systems. So let's start with company grounding. Like at Microsoft, you know, spending time with customers, one of the things we saw early was that whenever you build an agent, you you always have the knowledge you care about for that agent and you'll manage that yourself, but you also need to ground the agent often on the kind of ambient data of your organization, you know, whenever the agent leaves. This includes maybe your documents, your emails, your chat threads, or the information in your data warehouse and whatnot. So, we built Microsoft IQ as a way to give you a single entry point into all these kind of ambient data that agents need to get the job done in addition to the specific information that you build into the agent. Microsoft IQ is not one feature, it's more like a set of capabilities that goes from work IQ that connects your agents to all the documents in say SharePoint, all the emails, calendar, your chats, and the connections between people to fabric IQ that gives you access to all the all your analytics assets, you know, from data warehouses and data lakes to Power BI reports, and foundry IQ, which is what you use for your all agents where you can push your own data and then use it for grounding. And of course, sometimes you have your agents need to go out to the web to ground on data maybe not yours, it's public information, but but you need to use it to complete the picture of what the agent world's view is, and for that we have web IQ. Now, this first part allows agents to ground on the kind of these ambient data. Now, the second dimension I mentioned before is the evolution of the actual retrieval systems. You know, when drive first emerged, I think, you know, what we saw is like an initial adoption for vector databases that really unblocked us from getting a lot of these systems off the ground, and that was great. Um, I think, you know, for a hot second as an industry, we thought that if we could get really, really good at computing cosine similarity between vectors, we were all set for retrieval. It turns out, you know, things never are are never that easy. Uh, so, you know, what evaluations show over and over again is how, you know, if you combine methods, you just get better results. Like in this case, this is an evaluation from actually I search, the search technology behind Foundry IQ. And you can see how individual methods don't do as well as combined methods, particularly when you apply them to real-world customer scenarios. Now, the trick is how you build a platform that allows you to combine all these building blocks without putting the complexity right in front of you. You like let you opt into it when you need control, but when you have a scenario that is clear, then you can have an easy system. So, in Foundry IQ, that was one of our core design goals. And the way we do this is we actually layer the system. So, you can start at the top, you can go to Foundry and say, "Hey, I have a bunch of, I don't know, PDFs or pictures over there. Just deal with them." And then we'll do everything under the covers, do like, I don't know, chunking, vectorization, deal with relevance and ranking, deal with agentic retrieval and whatnot. Now, if you're an expert and you want control, you can also do that. You can go to the bottom of the stack, you want to build vector indexes and tell us how to quantize the vectors or control lexical retrieval and whatnot. You can do all of that and you can do it in the same stack, which means you can go up and down as you as your needs change. Now, on on top of the core retrieval system, we also introduced an agentic retrieval stack because we see that for easy cases, like, you know, quick single-shot retrieval is great, but for more sophisticated cases, you do want a system that can reflect on on what's in the data set and decide whether or not we've satisfied the information need as stated in the input before we come back with results. Of course, we see a lot of patterns like this emerge and they always the question is, is this actually useful? Like, are the results better? Our experience in our own evaluations is for for difficult cases, agentic retrieval can a difference. You across the many metrics that we we track, you know, things like um the actual actual evidence recall or answer completeness, we see like the agentic retrieval approach continuously does better than than simple that's uh individual simple parts. Now, let me show you some of these in action if you can go to laptop. Can we switch to the laptop? There you go. So, here I'm in I'm in Foundry, and uh Foundry is where you you manage your agents, manage models, but also the place where you can manage all the knowledge that you give your agents in order to uh do their jobs. Um when here, you can you can create knowledge bases as the kind of the entry point of energy agents into the knowledge you care about. In this case, I'll create a knowledge base. I have a data set about movies. These are agentic retrieval systems, so I'll give it a model to power the retrieval workflow. And I can say how much effort you want the model to uh to make or the system to make. And this is effectively a trade-off between latency and quality. I can configure a number of other things, but critically, I want to say where the data I want to ground is coming from. And uh I can start from scratch, or in this case, I have a bunch of unstructured data like PDFs and whatnot in in blob storage. I have structured, you know, parquet tables with statistics, and I also want to ground on the web. So, if I take these three steps, and then I save this knowledge base, now I have this asset, this knowledge base that I can connect to an uh Foundry agent right here, and it'll take a second. Uh but also it's a standalone asset that if I have already a harness that I'm using in other in other places, every knowledge base is an MCP server, so you can just connect to it uh without having to write any glue code in the middle. Now, a knowledge base like this has uh you know, has a bunch of parts. Some of them, like uh for example, this uh storage uh content, you usually build indexes uh and you you know, vectorize these things and whatnot. Uh and if you want control over that, like if I if you don't, you can just use it here. But, if you do, let me just switch to Azure and show you the service behind that particular instance. Where if I go to knowledge bases, this is the knowledge base we just created a second ago. And I can go peek inside. For example, I can go fish out the indexes that back this particular uh piece of content. And in that index, I can see what is the structure of the index. Uh if I'm opinionated about, I don't know, maybe the quantization uh approach I want to use or which indexing algorithm I want for my vectors, I can say all of that. And of course, I can actually go and explore the data. And you know, see what's inside, how chunks were organized, and and whatnot. So, the goal of this is to again give you high product a highly productive environment when you need uh when you don't need uh the sophistication, and when you need it to make sure you have it to get your job done. We go back to slides. And of course, the other aspect of this is, you know, top of mind these days for all of us is token uh is token efficiency. And uh so, uh we carefully evaluate this system to make sure that we give you the most information dense answer that has the fewest tokens uh so that you you know, the the your consumption of tokens has a high value when it comes to all retrieval tasks. The last category of knowledge I wanted to talk about is learned knowledge. Now, learned knowledge is the result of us doing the work we do as individuals and as organizations every day. And the the idea that we can actually observe the processes and get better at them by reflecting and improving every step of it is something that is really uh changed now that we have agents doing the work and we can go tune the agents automatically. Satya wrote about this recently and reflected on the fact that people and agents can really compound in in how they do the work and how they can create this learning loop that effectively captures what's unique about the company or or the organization you're working on and inputs that to work to differentiate the work that you do. Now in Foundry we wanted to offer like a material a materialized version of this that you can use today. So we built a component called the agent optimizer that effectively goes through this process and allows you to evaluate a baseline, generate candidates, and then you know, evaluate the new candidates and we have a strong result, then deploy that to production. Let me give you a kind of a quick flavor of what this looks like if we can switch back to the laptop. All right. So here I'm I mean VS Code, I have the Foundry toolkit installed. And I have a simple agent, it doesn't matter how you write your agent as long as you externalize configuration like you know, your instructions, tool definitions, skills, and whatnot. So once you have one of those, it takes two key steps to do this. So first oops. Um I can actually so usually you have an evaluation already, but if you don't, you can actually say eval generate and what we'll do is we'll look at what we know about the agent like traces and instructions and whatnot and we'll produce a task adherence focused evaluation for you. In this case I run this a little bit earlier. So just to give you a flavor of what this looks like, you you have a bunch of tasks and then you know, the questions and the criteria and whatnot. Once you have a dataset you can evaluate then next step is you can say uh optimize. And uh I could just run optimize on its own and that will run In this case, this run for maybe 45 minutes or so and you get an optimized version by effectively hill climbing the metric that's established from by evaluation. Um so I run this earlier and so let me show you the output for this particular one. Where you can see that, you know, we established the baseline first and then we kept iterating on candidates uh using different combinations using a J power style kind of loop uh and uh looking for options that perform better given uh the rubric that we have. And uh the interesting thing is that once you found one that is that is better, then you can simply just say optimize apply and what this does is since you externalize the configuration, it allows you to swap one configuration for the other. Um if I if if we look here, you can see that for example, I have baseline and the one we just applied. And just to pick on instructions, these are just the uh trivial instructions for this example agent. But if I look at the optimized one, then you can see like a bunch of instructions that are not handwritten but that that they emerged out of the hill climbing process to get to make this particular um agent better given what we have in terms of instructions and skills and tools, but also based on reflecting on the actual uh traces from the agent as users are using it. So this is a real learning loop materialized in practice. You can go back to slides. So this was like a very quick overview about how do we think about knowledge in the context of AI and how do how we think we can enable these learning loops that will capture, you know, these differentiated capability that lives in each one of the companies and organizations we work on. If you want to try anything of what I talked about or showed today, you can head to ai.azure.com and get going. And with that, thank you all for listening this morning. I hope you have a great rest of the event. Thanks.