Please turn JavaScript on
baeke.info icon

baeke.info

Want to stay in touch with the latest updates from Baeke.info? That's easy! Just subscribe clicking the Follow button below, choose topics or keywords for filtering if you want to, and we send the news to your inbox, to your phone via push notifications or we put them on your personal page here on follow.it.

Reading your RSS feed has never been easier!

Website title: Baeke.info – Focus on cloud-native and Azure

Is this your feed? Claim it!

Publisher:  Unclaimed!
Message frequency:  0.81 / day

Message History

Many teams extract data from documents in two steps. They convert the document to Markdown with a service like Azure Document Intelligence, then prompt an LLM to pull the fields they need out of that Markdown. It works, but you run two services and write the prompt yourself. You also get no indication of how sure the answer is or where on the page a value came from.

Az...


Read full story

A few days ago I wrote about using Azure API Management as an AI gateway for your agents. API Management is a good fit when your agents run on Azure and you already use it for your other APIs. But plenty of teams run their agents on ...


Read full story

Two things stood out in this week’s Notes. Microsoft now runs the agent loop for you in Foundry, with a managed harness, skills and recovery from interruptions. And it keeps widening model choice in two directions at once: its own frontier models from Microsoft AI, and Anthropic’s Claude model...


Read full story

I wasn’t keen on Microsoft retiring the Bing Search APIs. We used them to ground our agents in current information from the web, and they worked from any code you liked. What replaced them in Foundry, Grounding with Bing and the web search tool in Foundry Agent Service, never felt right to me. Both are tied to Foundry agents, and that leaves little room when your agent runs s...


Read full story

Lots of the work I see in projects is a chain of steps: fetch a document, convert it, call a model, write the result somewhere. You write it as a background job that reads from a queue, and it works fine until the process restarts halfway through a 300-page PDF or a model call times out. Before long you’re writing status tables, retry loops and checks for “did I already do th...


Read full story