Building AI-Powered Applications with Azure Serverless Functions and C# .NET
summary
A concrete build: a Next.js front end calls C# .NET Azure Functions (HTTP trigger) which forwards prompts to Azure AI Foundry / Azure OpenAI and returns a streamed document and email attachment, claiming it saves 8–10 hours for documentation. Implementation notes: consumption plan shows cold start pain so premium/flex recommended, blob/event-grid triggers and fan‑out for scaling, keyvaults for secrets, 1M free executions. Demo generates a test‑case doc successfully. Costs and token rates are given for deployed models.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:05Why serverless with Azure Functions
- 2:53Azure Serverless benefits
- 5:05AI documentation demo
- 8:58Documentation tool demo
- 11:07Azure Functions 101
- 13:55Hosting plans and costs
- 14:37Cold starts and premium plans
- 15:39Event-driven architecture
- 17:44Blob triggers and streaming
- 19:09Performance and cost best practices
- 20:32AI security practices
- 21:14Triggers in VS and Azure
- 22:39Azure AI Foundry deployment
- 23:44When to use serverless
- 24:26Q&A
related talks
01h 01mServerless Architecture With Azure
54mDeveloper Fundamentals of Serverless NET Development with Azure Durable Functions
42mServer-less compute with .NET based Azure Functions
43mServerless Application Development using
39mIntroducing Azure Functions for serverless .NET
59mAzure Serverless for JavaScript TypeScript Folks
54mUnderstanding the Serverless platform in Microsoft Azure
59mServerless Compute with Azure Functions