Browse DevOps Community (194)

TomClaes explains how to govern Azure Log Analytics retention across many workspaces by keeping workspace defaults low, setting per-table interactive retention, and using long-term retention only where needed. The post includes an Azure Policy-based, DeployIfNotExists solution with auditing, drift detection, and automated remediation.

junjieli summarizes the July 2026 releases (1.6.3–1.6.6) of the Foundry Toolkit for VS Code, focusing on a flatter, tabbed workspace, inline tool wiring, deeper agent debugging via event-level inspection, and a new Agent Optimization preview that supports measured compare-and-deploy tuning for hosted agents.

HimanshuYadav explains how to transfer a live GitLab project to a new group without accidentally “resetting” Terraform state or breaking pipelines, focusing on what changes during a namespace move (variables, runners, identity mappings) and how to validate and roll back safely.

hetvip introduces a community template collection that lets teams keep their existing workflow orchestrator (like Airflow, Temporal, or Argo) while using Azure Container Apps Jobs as the execution layer for containerized tasks, including guidance on identity, RBAC, retries, and fan-out patterns.

stevenjma announces the general availability of Terraform AzureRM provider 5.0 and explains the key breaking changes, including new defaults for Resource Provider registration, opt-in Azure preflight validation during terraform plan, and removal of deprecated resources and properties.

Lee Stott walks through an end-to-end, production-minded approach for taking a multi-agent system from local development into Microsoft Foundry Agent Service, then distributing it to users in Microsoft Teams. The guide focuses on identity, governance, observability, and repeatable deployment using the FibreOps reference implementation.

Chris Noring explains how to investigate unexpected GitHub Copilot Enterprise AI-credit spend and then control it using GitHub Billing guardrails. The post walks through identifying the SKU driving costs, attributing usage to organizations and cost centers, and applying budgets, alerts, and per-user limits without breaking productive workflows.

tonimontez explains how to govern GitHub Copilot’s usage-based spend using GitHub’s native budget controls first, then adds an Azure API Management gateway in front of an Azure AI Foundry (Azure OpenAI) deployment for real-time, token-granular quotas and per-developer telemetry.

vladvino announces the public preview of the AI Gateway tier for Azure API Management, focused on publishing and governing AI models and MCP servers. The post explains the new portal experience, policy-card governance (rate limits, quotas, Content Safety, fallback), and OpenTelemetry token metrics to destinations like Application Insights.

Kumar Kaushal demonstrates a transitional Azure networking pattern for phased migrations where an application is hard-coded to a legacy private IP. The lab uses Private Link Service Direct Connect plus a Private Endpoint and a site-to-site VPN so Azure-hosted tiers can keep calling the same on-premises address during the interim phase.

Lee Stott explains why the Model Context Protocol (MCP) is becoming the standard way AI agents connect to tools and data, then shows minimal runnable MCP server examples in Python and TypeScript plus practical guidance for VS Code hosting, security, and production operations.

carlottacaste shares a short walkthrough of the Foundry Toolkit for Visual Studio Code and a companion VS Code Learn course, focused on keeping model selection, prompt iteration, and agent development inside VS Code, with links to a full video playlist and a featured setup episode.

AbodeSaafan explains how the Azure Logic Apps team migrated roughly 60,000 per-customer Azure Functions apps from the end-of-life v1/v2 runtime to Functions v4 (isolated worker) under live load, using shadow traffic, strict parity checks, and a progressive rollout with fast rollback and careful retirement of the old fleet.

stevenbucher explains how Azure Policy for Kubernetes can now enforce policies using Kubernetes Validating Admission Policy (VAP) with CEL, via Gatekeeper’s integration. The post contrasts the older webhook/Rego flow with in-process validation, then walks through packaging a CEL constraint template into an Azure Policy definition and rolling it out across AKS clusters.

junjieli introduces the Foundry Agent Canvas (public preview), a GitHub Copilot App extension that lets developers discover resources, scaffold and configure a Foundry hosted agent, test it locally with an embedded Agent Inspector, and deploy it to Foundry Agent Service using azd-driven workflows.

anandgmenon walks through running Azure Logic Apps Hybrid on a self-managed RKE2 Kubernetes cluster, including how to provide an ingress IP with MetalLB, connect the cluster to Azure Arc, install the Container Apps extension, and fix the RKE2-specific DNS and inotify issues that can break deployments.

brauerblogs shares a reminder to register for Microsoft’s “Path to Production for Agents” webinar series (July 27–28), focused on taking AI agent solutions from experimentation to secure, scalable production with guidance on governance, platform design, AgentOps, and multi-agent architecture patterns.

Ricardo Duncan describes how CDK Global migrated a business-critical automotive CRM platform to Azure SQL Managed Instance, including the architecture choices, migration approach, and operational practices used to move more than 1,000 databases with minimal downtime.

richpaw describes a reference architecture for running Microsoft Discovery on a Windows VM in Azure and connecting it to an Azure CycleCloud HPC cluster via Azure NetApp Files (NFS) and SSH, so agentic workflows can submit Slurm jobs, read/write POSIX files, and stay inside a private network boundary.

Ron Frenkel explains how the Azure Copilot Observability Agent (now generally available in Azure Monitor) helps teams investigate Azure AI Foundry and GenAI agent issues using Application Insights telemetry, including failures, latency, tool-call errors, token spikes, and dependency bottlenecks with evidence-backed root cause analysis.

VimalVerma outlines Hypervelocity Engineering (HVE) as an operating model for building and continuously evolving Azure AI Landing Zones, with a focus on platform engineering, Infrastructure as Code, Policy as Code, and security-by-design so enterprise AI platforms can scale without losing governance.

Suma SaganeGowda explains how Microsoft 365 built COSMIC, an internal platform layer on Azure Kubernetes Service (AKS), to standardize provisioning, deployments, security/compliance guardrails, and observability across globally distributed services so product teams can ship faster without taking on Kubernetes operational overhead.

alyssaschimm announces a public preview in Azure Monitor that adds advanced platform metrics for Azure Storage, giving container-level visibility into blob capacity and blob count so teams can investigate growth drivers, set better alerts, and improve cost and capacity planning without building custom reporting pipelines.

Krishna Roy shows how to load test Copilot Studio agents by simulating real multi-turn conversations over Direct Line (HTTP + WebSockets) with Locust, then running the same workload in Azure Load Testing. The post covers measuring TTFB vs full turn completion, handling turn.complete, file uploads, and secret handling with Key Vault.

hetvip explains how to use Apache Airflow as an orchestrator for Azure Container Apps (ACA) Jobs, enabling dependency ordering, parallel fan-out, and per-task retries. The post introduces two open-source templates and a shared Airflow operator that triggers ACA Job executions via the ACA Jobs API.

akhilkarmalkar announces Azure Front Door edge actions (public preview), a way to run lightweight JavaScript during request processing at Microsoft’s global edge. The post explains where edge actions run in the Front Door pipeline, what scenarios they enable (routing, headers, auth checks), and how Hyperlight micro-VM isolation is used to keep execution secure.

Lee Stott tours Microsoft’s open-source course on taking AI agents from prototype to production using Microsoft Agent Framework and Microsoft Foundry, covering agent design, multi-agent orchestration, evaluation, deployment, data sovereignty, and tool governance with concrete commands and code patterns.

jisunchoi explains how to replace “multi-model chaos” with a governed AI gateway on Azure using Azure API Management, covering cost controls (token quotas and budget-based model downgrades), security hardening (managed identity + private endpoints), observability with Application Insights, and a Terraform-based deployment you can integrate with GitHub Copilot.

supriyas lays out a practical, end-to-end lifecycle for building enterprise AI agents, using a banking “loan agent” example to show how to design guardrails, build with safety controls, test with evaluations and red teaming, deploy gradually, and continuously monitor and iterate using Microsoft Foundry and Azure services.

Arturo Quiroga shares major updates to the open-source Azure Architecture Diagram Builder, including a multi-turn Architecture Chat, a Blueprint (whiteboard-style) rendering mode, and a new MCP server interface so AI agents can generate, validate, cost, and render Azure architectures programmatically.

CollinBrian explains how to design cloud-sovereign applications by keeping both deployment and runtime dependencies portable, using Radius for an application model and Dapr for consistent distributed-systems APIs across environments like Kubernetes and Azure.

Nir Mashkowski shares customer examples of how Azure SRE Agent is being used to reduce incident triage and investigation time by having an AI-powered agent gather evidence, classify issues, and recommend next steps, with an emphasis on governance controls and operational “memory” for teams running production on Azure.

Efrat Ben Porat announces public preview support for autonomous operations in the Azure Copilot Observability Agent, which can listen to Azure Monitor alerts, correlate them into issues, and run deep investigations automatically. The post explains what’s new, how correlation is guided by custom instructions, and how this changes on-call triage workflows.

anandgmenon walks through deploying Azure Logic Apps (Standard) in Hybrid mode on Red Hat OpenShift using Azure Arc and the Container Apps extension, calling out the OpenShift-specific gotchas around SCC permissions and DNS, plus concrete CLI/Helm commands and troubleshooting tips.

KishoreKumarPattabiraman explains why “golden paths” in platform engineering need to be treated as long-lived products, not one-off projects. Using examples like an AKS migration and identity modernization, the post lays out an operating canvas for ownership, guardrails, adoption strategy, and measurable feedback loops that keep paved paths trusted over time.

Dustin Ellis outlines practical ways to keep GitHub Copilot usage predictable under usage-based billing, focusing on token drivers like model choice, context size, and tool/agent usage. The post includes concrete prompting patterns, team guardrails, and lightweight policy ideas to reduce waste without losing the benefits of AI-assisted development.

hcamposu introduces Logic Apps Standard Local Functions and explains when workflow-scoped .NET code belongs inside the same Logic Apps project instead of being split into a separate Azure Functions app, with practical guidance on scenarios, runtime behavior, and deployment implications.

WSilveira’s July 2026 Logic Apps Aviators newsletter rounds up key Azure Integration Services updates and community posts, including the Logic Apps Standard move toward Azure Functions out-of-proc hosting for .NET 10, dynamic connection names, MCP server management in API Management, and agentic Logic Apps patterns.

Arpit_MSFT shows how to route Azure Service Health alerts to the right team automatically by using Azure Monitor Action Groups to trigger an Autonomous Agent Logic App, backed by a simple service-to-owner mapping (for example, a CSV in Azure Blob Storage) with a default fallback recipient.

Jack Tracey announces that Azure landing zone (ALZ) has moved from a community-led open-source initiative to an officially owned Microsoft product under the Azure Migrate team, while keeping the existing repos and consumption model unchanged for users.