As I already had some experience in the past with hosting different agents, I took that news with great joy. As an engineer, I am definitely more fond of writing code that solves the problem, instead of relying on the prompts alone (even if I mostly work starting from prompt-engineering nowadays).

I picked the topic partly because of the calendar. Azure AD B2C is not vanishing overnight - Microsoft still supports existing tenants until at least May 2030 - but the product line has been in wind-down for a while. New customers could not buy B2C after May 2025. B2C Premium P2 went away on 15 March 2026, just days before the talk premiered. No new features land on B2C anymore; External ID gets those instead. If you are starting a B2B portal in 2026, that is worth knowing before you copy an old B2C sample repo.

The project was a file-aware chat: upload internal documents, ask questions, get answers grounded in those files. We built it twice - first as classic RAG on Azure OpenAI plus Azure AI Search, then as an Azure AI Foundry Agent. The second path was better for file handling; the first path was easier to reason about in Terraform. Platform engineers will recognize the pattern: the product story moves faster than the IaC provider story.

I had joined a Databricks engagement from the Azure infrastructure side - Terraform, identity, pipelines - rather than from notebooks. The meetup was a compressed version of that delivery work. I am expanding the same material into a longer whitepaper with diagrams; this post is the short form from right after the talk.

No sample repository to clone. The lecture walked through a real internal experiment: matching people to project requirements in a software house, using Azure OpenAI from an ASP.NET app, with Azure AI Search in the middle. At the end I also compared that path with Copilot Studio - mostly to show that Microsoft gives you more than one way to solve similar problems.

My employer sponsored the Big Data & ML/AI track, but the ticket came through a different door: Akademickie Stowarzyszenie Informatyczne at Wrocław University of Technology, where I chaired the board years ago. ASI was a community partner and had passes for alumni. Old student-association contacts still open doors — I am not complaining.

The GitHub repo is where I put the sample apps, reference workflows, and session notes while the material was still warm. Slide decks from the live event are not there — this post is the outline I wish I had written down before the first cohort showed up.