Microsoft Azure User Group Poland - Meetup - 2026-09-16

Today I had the pleasure to attend the [WAW] 83rd Microsoft Azure User Group Poland meeting in Warsaw, which opened the autumn season. There were 3 presentations, I stayed for the first two.

Gdzie postawić agenta w Azure? - Łukasz Kałużny

The starting point was a simple definition - agent = model + tools + context - and the loop it runs in (think → tools → observation → response), triggered by a human, a cron, an event or an API call.

The main takeaway: an agent is just a microservice - a regular application or an event-driven worker. Its state is a database, while tools and the LLM are simply APIs it calls. From that angle, “where to host an agent” is the same question we ask about any other service:

Logic Apps - agent loop
Microsoft Foundry - prompt agents and hosted agents
App Service
Durable Functions with Durable Task Scheduler and Durable Task for AI agents
Container Apps, including dynamic sessions for running LLM-generated code safely
AKS, with KEDA and Dapr Agents for event-driven scaling

An important note about frameworks such as Microsoft Agent Framework: they are building blocks, not a finished product.

Logic Apps got a lot of attention, as they can act as an A2A server, an MCP tool, a knowledge base, or a workflow calling other workflows.

A separate thread was web search. The Bing Search API is effectively frozen and the only way forward is Grounding with Bing Search, which is really just a billing object. Worth remembering: data leaves the Azure compliance boundary, the service works on a cached copy of the internet, and it is hard to debug because you cannot see what goes in and what comes out.

The closing punchline - the Death Star is back, this time with an LLM - about the risk of building one huge monolith around agents again.

Subscription Vending Machine: jak oddać Azure w ręce zespołów i nie stracić nad tym kontroli - Krzysztof Polewiak

The second talk was about automating Azure subscription creation, so that teams can get subscriptions in a self-service way while staying within organizational standards. It was demonstrated with ChrisPolewiak/AzureSubscriptionVending.

The solution is an Azure DevOps pipeline that validates inputs, bootstraps a resource group and a user-assigned managed identity with Bicep and Azure Verified Modules, configures RBAC, optionally creates a service connection with OIDC authentication, and finally moves the subscription into the target management group.