Azure Counsel Podcast

If your Azure Functions are still using connection strings to access Service Bus, Event Hubs, or Cosmos DB, you’re carrying a hidden security risk into production.In this episode, Bhanu from Azure Counsel breaks down how to eliminate secrets entirely using User-Assigned Managed Identity and Azure RBAC, and why this shift is critical before the November 2026 Azure Functions deadline.This is not just a migration — it’s a fundamental move toward Zero Trust architecture, where identity replaces credentials as the core of your security model.🚀 What You’ll Learn• How to identify hardcoded connection strings across your Azure environment using Azure Resource Graph (KQL)• Why connection strings create “God Mode” access and increase your blast radius• The difference between System-Assigned vs User-Assigned Managed Identity — and why system-assigned fails at scale• How to implement RBAC roles like Service Bus Data Receiver instead of using shared access keys• The AZURE_CLIENT_ID gotcha — the #1 reason managed identity fails in production• How to modernize your code using DefaultAzureCredential and Azure.Identity SDKs• Why Azure Key Vault is not a complete solution for connection string security• How to delete connection strings completely — while keeping your system running• How Azure Functions securely authenticate using Entra ID tokens under the hood🔐 The Zero Trust ShiftConnection strings were convenient — but they gave your applications unrestricted access.If a single key leaked, your entire system was exposed.Managed Identity changes that model entirely:• No stored secrets• No credential rotation• No shared keysInstead, access is controlled through identity + RBAC, enforcing least privilege at every level.This isn’t just best practice — it’s becoming the standard for secure, production-grade Azure systems.📋 Migration ChecklistAudit apps using AccountKey or SharedAccessKeyProvision User-Assigned Managed Identities (Bicep/Terraform)Assign RBAC roles at the correct resource scopeRefactor code to use DefaultAzureCredentialRemove connection strings and validate accessMonitor for 403 errors and fix identity mapping🧠 Key Takeaways• Connection strings = high risk, high privilege• Managed Identity = secure, scalable, and secretless• RBAC enables fine-grained, least-privilege access• AZURE_CLIENT_ID is critical in multi-identity setups• Identity should be treated as infrastructure, not configuration👨‍💻 Who This Episode Is For• Cloud Architects designing Zero Trust environments• Security Engineers auditing credential exposure• .NET Developers modernizing Azure Functions to .NET 8/10• DevOps Engineers automating identity and RBAC• Teams migrating large-scale Azure workloads securely🔧 Technical Focus Areas• Microsoft Entra ID (Azure AD) authentication• Azure RBAC vs Shared Access Keys• User-Assigned Managed Identity patterns• DefaultAzureCredential usage• Secure Azure Functions architectureIf you’ve ever:• worried about leaked connection strings• struggled with RBAC complexity• hit 403 errors using Managed Identity• or delayed moving to Zero TrustThis episode gives you the exact blueprint to eliminate secrets and secure your Azure Functions for the future.🎥 Watch the full walkthrough with demo:https://youtu.be/q2ALmOXdFTA

You deployed your Azure Function…But now your logs are missing, out of order, or so vague they’re useless.Worse — your Application Insights bill is exploding while you’re still debugging blind in production.Sound familiar? 😅In this episode, Bhanu from Azure Counsel breaks down the exact logging architecture used to build traceable, distributed Azure Functions systems — without burning money on telemetry.This is not about Console.WriteLine.It’s about structured logging, correlation IDs, and cost-aware telemetry design for real production workloads.⚠️ Critical for 2026 and BeyondWith the November 10, 2026 retirement of the Azure Functions In-Process model, your logging strategy must change.This episode focuses on ILogger<T> + dependency injection for the Isolated Worker model and how logging behavior differs from the old runtime.🎯 What You’ll Learn:How to correctly configure APPLICATIONINSIGHTS_CONNECTION_STRING for local and productionWhy most logs disappear or arrive out of orderHow to tune log levels globally and per function to suppress noiseHow Azure drops telemetry when sampling is misconfiguredHow maxTelemetryItemsPerSecond can cut 90% of your ingestion costWhen to use LogInformation, LogWarning, and LogCriticalHow to centralize logging using a helper classHow to inject Correlation IDs for distributed tracingWhy your error logging strategy defines production stability🧠 Key Takeaways:Pay for insight, not noisePreserve statistical accuracy while reducing costPrevent silent outages caused by sampling misconfigurationBuild traceable request flows across microservicesStop debugging blind in production👨‍💻 Who This Episode Is For:Cloud Architects designing high-volume telemetry systemsSenior Developers building Azure Functions with C#DevOps Engineers managing Log Analytics cost and alertsTeams migrating to .NET 8/10 Isolated WorkerEngineers tired of runaway Application Insights bills🔧 Technical Focus Areas:Azure Functions v4 & Isolated Worker modelApplication Insights & Log Analyticshost.json sampling and aggregator settingsStructured logging with ILogger<T>Distributed tracing & Correlation IDsIf your Azure Functions have ever:• lost logs• flooded Application Insights• missed exceptions• or cost more to monitor than to runThis episode gives you the logging blueprint to fix it permanently.🎥 Watch the full walkthrough on YouTube:https://youtu.be/nDR_LwzS3U8

Are you confused about how your Azure Function runs or where the data comes from? In this episode, Bhanu from Azure Counsel takes you from zero to hero by breaking down the core pillars of Azure Functions — Triggers, Input Bindings, Output Bindings, and the runtime — through real-world examples, production pitfalls, and architectural insights.If you’ve ever wondered:“Why did my Function run when I didn’t call it?”“Where did this data suddenly come from?”“Why didn’t my output reach Blob Storage or Cosmos DB?”This episode is your end-to-end blueprint for mastering Azure Functions development.🎯 What You’ll Learn:How Azure Functions execute behind the scenesThe 4 core pillars: Triggers, Runtime, Input Bindings, Output BindingsDeep dives into Timer, HTTP, Blob, Event Grid, Cosmos DB, Service Bus, Event Hub, and SignalR triggersHow triggers connect to event sources like Event Hub, Service Bus, and Cosmos DBHow bindings simplify integration while revealing critical production risksCommon mistakes developers make assuming binding durabilityPractical fixes: retries, monitoring, and correlation best practices💡 For Azure Developers & Architects:Whether you’re preparing for Microsoft AZ-204, building serverless APIs, or deploying event-driven architectures, this session covers everything you need to understand triggers and bindings in production environments.👨‍💻 Who This Episode Is For:Azure Developers building event-driven or API-based solutions.NET, Python, Node.js, and C# developers deploying to Azure FunctionsCloud Architects designing serverless, event-based microservicesDevOps professionals optimizing monitoring, retries, and scaling in productionAnyone learning Azure Cloud Application Development or Serverless Computing🧭 Key Takeaways:Understand Trigger–Binding orchestration inside Azure FunctionsAvoid silent failures from transient issues or misconfigured bindingsImplement retry policies, correlation IDs, and diagnostics for production observabilityLearn scaling behaviors of each trigger type in Azure Functions v4Discover integration with Event Grid, Service Bus, and Event Hub🔧 Technical Focus Areas:Azure Functions in C#, Python, and Node.jsFunction App deployment, monitoring, and logging best practicesIntegration with Azure Service Bus, Event Hub, and Cosmos DBAzure serverless development & cloud-native architectureDurable Function design patterns for enterprise-grade systems🎥 Watch the full visual tutorial on YouTube: https://www.youtube.com/@azurecounsel

Stop paying for idle servers—go serverless with Azure Functions. In this episode, discover how Azure Functions can cut cloud costs, simplify scaling, and remove DevOps overhead by shifting from VMs and containers to serverless computing.Perfect for developers, cloud architects, and DevOps engineers, this episode covers Azure Function Apps, Durable Functions, event-driven workflows, Function App pricing plans, and monitoring with Application Insights. Whether you build in Python, C#, or Node.js, you’ll learn why serverless is the future of cloud computing on Microsoft Azure.🎥 Watch the full video of this episode on YouTube: https://youtu.be/GR4NUAr3BnA