Month: July 2026

🔹 Feature: Containers Directly Inside WSL 2 — No Docker Desktop, No License 🔹 What It Does: Run Linux containers natively inside a WSL 2 distro by installing Docker Engine (or Podman) directly — bypassing Docker Desktop and its commercial subscription requirement. What Is It Giving You: ✅ No More Docker Desktop License: Docker Desktop is free for personal use and small businesses only. Organizations with 250+ employees or $10M+ annual revenue must buy a Pro/Team/Business subscription per user. Running Docker Engine inside WSL 2 avoids that cost entirely — it’s the same open-source engine that Docker Desktop wraps. ✅ Same docker CLI You Already Know: docker build, docker run, docker compose — identical commands, identical behavior. Existing Dockerfiles and docker-compose.yml files just work. ✅ Full Linux Kernel Performance: WSL 2 ships a real Linux kernel with full syscall support, so containers run natively — no Hyper-V wrapper VM, no Docker Desktop LinuxKit VM in the middle. Faster container startup, lower memory footprint, better I/O. ✅ Two Clean Alternatives: Install docker-ce from Docker’s official Ubuntu/Debian repo inside your WSL distro, OR install Podman (daemonless, rootless, drop-in alias docker=podman). Both are fully commercial-use-free. ✅ Works With VS Code Dev Containers: The … Containers Directly Inside WSL 2 — No Docker Desktop, No LicenseRead more

🔹 Feature: Windows Cloud New Features 🔹 What It Does: A wave of new Windows 365 and Azure Virtual Desktop capabilities that improve Cloud PC user experience, security, and manageability. What Is It Giving You: ✅ Teams RemoteApp / CloudApp Support (SlimCore / VDI 2.0): Native Teams optimization for RemoteApp scenarios — better audio/video quality inside published apps. ✅ Windows 365 Migration API: Programmatically migrate Cloud PCs between provisioning policies and configurations at scale. ✅ Windows 365 Cloud Apps: Deliver individual Windows apps to any device via Cloud PC — full desktop no longer required. ✅ Disaster Recovery Plus: Paid DR add-on with pre-reserved capacity in the alternate region — real cross-region failover for Cloud PCs. ✅ External Identities Support: Provision and assign Cloud PCs to external / guest identities via Microsoft Entra External ID. ✅ Token Protection for Windows App: Binds authentication tokens to the device — mitigates token theft attacks against the Windows App client. ✅ Multiple Personal Desktop Assignment (AVD): Assign more than one personal desktop to a single user for role-based scenarios. ✅ Health Checks in Sovereign Clouds: Built-in AVD/Cloud PC health-check telemetry available in Gov clouds. ✅ Windows App on the Web for GCC: Full … Windows Cloud New FeaturesRead more

🔹 Feature: Load Aware Routing in Application Gateway for Containers 🔹 What It Does: Routes traffic to the backend pod reporting the lowest current CPU, memory, GPU (or any custom) utilization. What Is It Giving You: ✅ Real Utilization, Not Just Request Count: Traditional least-request or round-robin don’t reflect what a request really costs. A GPU inference request can saturate a node while a small HTTP request costs almost nothing. Load-aware routing evaluates actual resource utilization and sends the next request to the endpoint with the most spare capacity. ✅ Standard-Based (ORCA): Backends emit an endpoint-load-metrics HTTP response header per the Open Request Cost Aggregation (ORCA) standard — in text or JSON. AGC consumes this header and strips it before responding to the client, so no internal metrics leak externally. ✅ Built-In Metrics: cpu_utilization, mem_utilization, application_utilization, rps_fractional, and eps are supported out-of-the-box. Include rps_fractional plus any utilization metric for a valid ORCA report. ✅ Custom Named Metrics for GPU / Queue / Anything: Use the named_metrics prefix to report any signal — GPU utilization, queue depth, VRAM pressure, model load state. Reference them in the namedMetrics list of the policy and AGC computes endpoint weight from the maximum of those … Load Aware Routing in Application Gateway for ContainersRead more

🔹 Feature: Application Gateway for Containers Migration Utility 🔹 What It Does: Auto-converts existing AGIC and NGINX Ingress resources into Gateway API YAML for Application Gateway for Containers. What Is It Giving You: ✅ Read-Only, Non-Destructive: Scan files OR a live cluster. The utility never modifies your existing ingresses or workloads — it only generates Gateway API YAML for you to review and apply when ready. ✅ Two Input Modes: files mode reads YAML manifests from disk; cluster mode reads Ingress resources directly from your cluster using the current kubeconfig context. ✅ Two Provider Sources: agic (default) migrates AGIC annotations; nginx migrates NGINX Ingress Controller annotations. One tool, both migration paths. ✅ Detailed Migration Report: Per-annotation status — completed, warning, not-supported, error — plus actionable recommendations for anything that requires manual steps. ✅ Flexible Output: Print to stdout, single file, or a directory with one file per resource. Pipe straight into GitOps. ✅ BYO or ALB-Controller Managed: Point at an existing AGC via –byo-resource-id, or generate an ApplicationLoadBalancer custom resource with –managed-subnet-id so the ALB Controller provisions and manages AGC for you. ✅ Cross-Platform Binaries: Linux, macOS, Windows (amd64 + arm64) — build once with ./build.sh. 🌐 https://github.com/Azure/Application-Gateway-for-Containers-Migration-Utility

🔹 Feature: Kubernetes Gateway API on AKS 🔹 What It Does: The standardized, role-oriented replacement for Kubernetes Ingress — with native support for HTTP, TLS, TCP, UDP, gRPC Why Move Off Ingress 🔸 Ingress API = One Resource, One Owner: Every advanced feature lives in vendor-specific annotations; HTTP/HTTPS only. Behavior depends entirely on which controller is installed — configs written for NGINX don’t work with Traefik or Application Gateway. 🔸 Ingress Solves Basic HTTP Routing Only: Canary deployments, header-based routing, TLS passthrough, gRPC, and mTLS across control planes all become bespoke annotation dialects per implementation. What Gateway API Is Giving You ✅ Multi-Protocol Support: HTTPRoute, TLSRoute, TCPRoute, UDPRoute, GRPCRoute. Route gRPC with real semantics, handle TLS passthrough, and manage TCP/UDP load balancing consistently. ✅ Rich Traffic Matching Built In: Header, path (Exact / PathPrefix / Regex), query parameter, and method matching are first-class fields. Weighted backendRefs for canary/blue-green deployments natively. ively. ✅ Multi-Tenancy & Cross-Namespace: A single Gateway in a platform namespace can route to app team services via ReferenceGrant — clean infra/app separation. ✅ Portable Across Implementations: Same YAML works with Istio, NGINX, Application Gateway for Containers, Envoy Gateway, and Cilium Gateway. ✅ Extensibility Without Annotations: Use HTTPRouteFilter for … Kubernetes Gateway API on AKSRead more

🔹 Feature: Cross-Cluster Networking for Azure Kubernetes Fleet Manager 🔹 What It Does: Managed multi-cluster pod network for AKS — direct pod-to-pod communication across clusters What Is It Giving You: ✅ Direct Pod-to-Pod Across Clusters: A flat virtual network across all member clusters. Traffic routes at native performance — no east-west gateways, no proxies, no encapsulation tax. ✅ Powered by Cilium Cluster Mesh: Requires Azure CNI powered by Cilium as the data plane, plus Advanced Container Networking Services (ACNS). Fleet manages the mesh lifecycle via a ClusterMesh profile — no manual cilium clustermesh connect operations. ✅ Global Services — Transparent Service Discovery + Load Balancing: Annotate a standard Kubernetes service with io.cilium/global-service: “true” and Cilium automatically discovers endpoints for that service across every cluster and load-balances traffic to ClusterIP across all of them. No app-level changes, no external service registry. ✅ High Availability & Automatic Failover: Run replicas of the same service across regions or availability zones. When endpoints in one cluster become unhealthy, traffic automatically routes to healthy endpoints in another. Cross-region failover with zero application changes. ✅ Shared-Services Pattern: Run tenant clusters isolated from each other but connected to a shared “services” cluster for secrets management, logging, monitoring, … Cross-Cluster Networking for Azure Kubernetes Fleet ManagerRead more

🔹 Feature: Azure Kubernetes Application Network for AKS 🔹 What It Does: Managed zero-trust service mesh for AKS — with mTLS, no sidecars, and native multi-cluster support. What Is It Giving You: ✅ Automatic mTLS: Encrypts service-to-service traffic by default. Supports both encrypted and unencrypted flows during rollout, then switch to strict mode when ready. FIPS-compliant cryptography in transit. ✅ Managed Certificate Authority: Backed by Azure Key Vault. Issues SPIFFE-compliant workload certificates with 24-hour validity, rotated automatically every 12 hours. Root and intermediate CAs managed for you. ✅ Ambient Architecture — No Sidecars: Node-level L4 proxies (ztunnel) handle traffic instead of a proxy container in every pod. Lower CPU/memory overhead, simpler operations. ✅ Optional L7 Waypoint Proxies: Turn on when you need advanced HTTP routing, header-based policy, or service-level policy enforcement. Off by default — you don’t pay the L7 tax on every workload. ✅ Multi-Cluster Mesh — The Strongest Use Case: Connect multiple AKS clusters into a unified service mesh. Services in one member cluster communicate directly with services in another, with mTLS enforced end-to-end across cluster boundaries. Cross-cluster traffic flows through east-west gateways; you provide reachability between them (VNet peering, VPN, ExpressRoute). Enables cross-region failover, dev/test/prod inter-cluster communication, … Azure Kubernetes Application Network for AKSRead more

🔹 Feature: Azure Cloud Shell — Open in VS Code for the Web 🔹 What It Does: A toolbar button in Azure Cloud Shell that opens the same session in a full Visual Studio Code environment in the browser — file explorer, editor, integrated terminal, Copilot Chat, and Azure Resources sidebar — connected to the same Cloud Shell container and identity. What Is It Giving You: ✅ Real IDE Instead of a Basic Text Editor: The old Cloud Shell built-in editor was fine for a quick tweak. VS Code for the Web is a real IDE — multi-file editing, IntelliSense, syntax highlighting for every language, side-by-side diffs, extensions, source control. Finally usable for anything beyond a one-liner. ✅ Same Container, Same Identity: The web VS Code attaches to your existing Cloud Shell container and inherits your Azure authentication. No re-login, no extra provisioning — files, tools, azd/az/kubectl state all just work. ✅ Full Azure Resources Sidebar: Browse and manage App Services, Container Apps, Cosmos DB, Function App, Logic App, Managed Identities, Microsoft Foundry, PostgreSQL Flexible/Standard, Spring Apps, SQL databases/servers, Static Web Apps, Storage accounts, Virtual Machines, Web PubSub, Azure Arc-enabled machines, and more — right from the sidebar. ✅ GitHub … Azure Cloud Shell — Open in VS Code for the WebRead more

🔹 Feature: Azure App Service as a Model Context Protocol (MCP) Server 🔹 What It Does: Host your web app as an MCP server on Azure App Service and expose its REST APIs as AI-accessible tools that agents (GitHub Copilot Chat, Cursor, Windsurf, etc.) can discover and invoke. What Is It Giving You: ✅ Turn Existing APIs Into Agent Tools: No rewrite. Existing App Service REST endpoints become MCP tools with structured inputs and outputs. ✅ Discovery + Invocation Flow: The agent queries your MCP server for available tools, picks the right one for the user’s intent, your App Service processes the request, and the agent returns the result to the user. ✅ Built-In Authentication: Native Microsoft Entra ID integration and managed identity support for production-grade MCP servers. Full control over authN/authZ and data access. ✅ Multi-Language Tutorials: End-to-end tutorials for .NET, Java, Node.js, and Python — integrate an App Service app as an MCP server for GitHub Copilot Chat. ✅ Reuse Your Existing Deployment: The same App Service that serves your line-of-business app also serves as the MCP endpoint. One app, one infra, one identity model — used by both humans and agents. ✅ Use Cases That Actually Ship: … Azure App Service as a Model Context Protocol (MCP) ServerRead more

🔹 Feature: Sidecar Containers in Azure App Service 🔹 What It Does: App Service now supports running your main application container alongside up to 8 additional companion (sidecar) containers in the same instance. All containers share the same network namespace — they communicate over localhost — and start, stop, and scale together. The pattern: App Service ├── main container: your application ├── sidecar: Redis (in-instance cache) ├── sidecar: OpenTelemetry Collector (metrics/traces exporter) └── sidecar: local AI model (e.g. Phi-4) What Is It Giving You: ✅ Up to 9 Containers Per Instance: 1 main + up to 8 sidecars. Configure via Azure Portal, ARM, Bicep, Terraform, or Azure CLI. ✅ Shared Network Namespace — Localhost Between Containers: Sidecars are addressable from the main container over localhost: — no VNet config or service discovery needed. ✅ Real Use Cases Without Extra Infrastructure: • Local caching (Redis, Memcached) • Observability (OpenTelemetry Collector, Fluentd) • Local AI inference (Phi-4, small LLMs, embeddings) • Envoy / NGINX reverse proxy • Custom auth proxies or credential brokers ✅ Any Container Registry: Docker Hub, Azure Container Registry, or any OCI-compatible registry. Each sidecar has its own image, tag, environment vars, startup command, and port config. ✅ Managed … Sidecar Containers in Azure App ServiceRead more

🔹 Feature: GitHub Copilot Modernization for .NET 🔹 What It Does: A GitHub Copilot agent that runs across Visual Studio, VS Code, GitHub Copilot CLI, and GitHub.com to upgrade legacy .NET projects to modern .NET and migrate them to Azure. What Is It Giving You: ✅ Six Predefined Upgrade Scenarios: .NET version upgrade (to .NET 8/9/10+), SDK-style project conversion, Newtonsoft.Json → System.Text.Json, System.Data.SqlClient → Microsoft.Data.SqlClient, Azure Functions in-process → isolated worker, and Semantic Kernel Agents → Microsoft Agent Framework. Plus 30+ built-in upgrade skills. ✅ Real Cloud-Migration Tasks Out of the Box: Migrate to Azure SQL DB / SQL MI / PostgreSQL with Managed Identity, Azure Blob & File Storage, Microsoft Entra ID (from Windows AD), Azure Key Vault, Azure Service Bus (from MSMQ/RabbitMQ/SQS), Azure Cache for Redis with Managed Identity, OpenTelemetry on Azure, Event Hubs Kafka, Communication Services email — all with industry best practices applied automatically. ✅ Covers Every .NET Project Type That Matters: ASP.NET Core (MVC, Razor Pages, Web API), ASP.NET Web Forms, Blazor, Azure Functions, WPF, Windows Forms, WinUI, .NET MAUI / Xamarin, class libraries, console apps, MSTest / NUnit / xUnit. C# and Visual Basic. Source: .NET Framework, .NET Core 1.x–3.x, .NET 5+ → .NET … GitHub Copilot Modernization for .NETRead more

🔹 Feature: AKS Cost Analysis — Works With Free-Tier AKS 🔹 What It Does: Microsoft’s open-source example exports AKS cost data to Azure Blob Storage as a daily CSV — breaking down costs by both Kubernetes What Is It Giving You: ✅ Cost Visibility for Free-Tier AKS: The built-in AKS cost analysis add-on requires Standard or Premium tier. This open-source export provides the same namespace-level cost breakdown for Free-tier clusters — ideal for dev/test, learning environments, and small workloads. ✅ Daily CSV in Azure Blob: A results.csv file lands in your storage account every day. Plug it into Power BI, Excel, Looker, or your data lake — your FinOps tooling, your choice. ✅ Two Worlds Joined in One File: Traditional Azure Cost Management data (resource group, region, meter, tags) joined with Kubernetes constructs (namespace, deployment, app/team labels, service). The joined view you’ve always wanted. ✅ Multi-Cluster Aggregation: Configure per-cluster data paths but merge into a single result file — consolidate AKS clusters across subscriptions into one dashboard. Multi-tenant chargeback made simple. ✅ Microsoft Entra Workload Identity: Securely authenticate to Azure Storage without connection strings — Zero Trust-friendly out of the box. ✅ Run as a Kubernetes CronJob: Deploy natively in … AKS Cost Analysis — Works With Free-Tier AKSRead more

🔹 Feature: Azure Logic Apps Automation – https://auto.azure.com/ 🔹 What It Does: A managed SaaS experience for building workflows, AI agents, and integrations MWhat Is It Giving You: ✅ Zero-Friction SaaS Onboarding: Compute, model endpoints, knowledge services, execution sandboxes — already there when you log in. No resource groups, no Cosmos DB to deploy, no integrator needed to wire three APIs together. ✅ 1400+ Enterprise Connectors: Office 365, Dynamics, SAP, Salesforce, ServiceNow, on-prem databases through the on-premises data gateway. n8n’s community-built nodes aren’t even in the same league. ✅ Knowledge as a Service (Built-In RAG): Drop in your documents — the platform handles ingestion, chunking, embeddings, retrieval, and vector store. No Pinecone bill, no LangChain pipeline to maintain. Grounded answers, zero plumbing. ✅ Any Model, Anywhere: Plug in frontier (GPT-5, Claude Opus), open-source, fine-tuned, or local models. Never locked in. ✅ Agents as First-Class Workflow Actions: Three integration patterns — agent loop orchestration, Foundry agents, and managed sandbox execution. Agents run in isolated sandboxes on the same canvas as your triggers and connectors. ✅ Expose Workflows as MCP Tools: Turn any of the 1400+ connectors into an MCP tool, OR expose entire workflows as MCP servers callable by any compatible … Azure Logic Apps Automation – https://auto.azure.com/Read more

🔹 Feature: Azure Kubernetes Service (AKS) Cost Analysis — Per-Namespace, Per-Workload Cost Visibility 🔹 What It Does: Built-in AKS add-on (powered by OpenCost) that breaks down cluster spend by namespace, workload, and underlying Azure resources — directly in Azure Cost Management. Available on AKS Standard or Premium tier (not Free). 💰📊 What Is It Giving You: ✅ Per-Namespace Cost Allocation: Show each namespace’s share of VM, disk, load balancer, and public IP spend — reconciled against your real Azure invoice. Chargeback / showback becomes a portal click instead of a spreadsheet exercise. ✅ Idle, Service, System & Unallocated Breakdown: Idle = available but unused capacity. Service = AKS service charges (Uptime SLA, Defender for Containers, etc.). System = capacity reserved for kubelet and container runtime. Unallocated = resources that couldn’t be tied to a namespace. Stop arguing about where the money went. ✅ Powered by OpenCost: CNCF Incubating project — open methodology, vendor-neutral attribution model. Microsoft just operationalized it inside Azure. ✅ Native Azure Cost Management Integration: Cost data lands in the same Cost Management views (Kubernetes namespaces and Kubernetes assets) as the rest of your Azure spend. One pane of glass for FinOps. ✅ One Flag to Enable: –enable-cost-analysis … Azure Kubernetes Service (AKS) Cost AnalysisRead more

🔹 Feature: AKS on Bare Metal — Run Real Kubernetes Directly on Edge Hardware, No Virtualization 🔹 What It Does: Azure Kubernetes Service on Azure Local (even old devices): no hypervisor, quick setup, ideal for edge hardware. What Is It Giving You: ✅ No Virtualization, No Hypervisor: Kubernetes runs directly on the hardware. Every CPU cycle and byte of memory goes to your workloads — not to a virtualization layer. ✅ Plug & Go Install: Plug a USB drive with an OS image from the Azure portal into the device, power on, wait a couple of minutes, remove the drive. That’s the entire on-site step. ✅ Built for Edge — Retail Back Rooms, Factory Floors, QSRs, Branch Offices: Small-form-factor hardware, low power, often ruggedized. Great fit for existing devices already deployed at the edge. ✅ Survives Intermittent Connectivity: The Kubernetes control plane runs locally on the device. When the link to Azure drops, workloads keep running normally. ✅ Same Azure Management Plane: Azure portal, ARM templates, Bicep, Azure Policy, Azure Monitor, GitOps — same tools you use for AKS in the cloud. Auto Arc-connected from day one. ✅ One Consistent Kubernetes: Same APIs, same lifecycle, same tooling across cloud, hybrid, … AKS on Bare Metal — Run Real Kubernetes Directly on Edge Hardware, No VirtualizationRead more

🔹 Feature: winapp CLI 🔹 What It Does: A CLI tool for Windows app packaging, identity, and platform integration. Works with any framework — .NET, Electron, C++, Rust, Flutter, Tauri. What Is It Giving You: ✅ One CLI, Any Framework: winapp init, pack, sign, cert, manifest, run, create-debug-identity — same commands whether you’re building with .NET, WPF, Win32 C++, Electron, Rust, Tauri, or Flutter. ✅ 12 Manual Steps → 4 Commands: SDK downloads, header generation, manifests, certificates, MSIX packaging — collapsed into a handful of commands. The README literally shows the before/after. ✅ Unlocks Windows-Native Features for Cross-Platform Apps: With package identity, your app gets interactive native notifications, Explorer / Taskbar / Share-sheet integration, protocol handlers (yourapp://), web-to-app linking, on-device AI APIs (local LLM, text/image AI), file type associations, background tasks, startup tasks, app services, and clean install/uninstall + auto-updates. ✅ Install Where You Already Are: WinGet (winget install Microsoft.winappcli), NPM (npm install @microsoft/winappcli –save-dev) for Electron, NuGet, or GitHub Actions / Azure DevOps via setup-WinAppCli for CI/CD pipelines. ✅ VS Code Extension: Press F5 to launch your app with package identity and auto-attach a debugger. No more leaving the editor to test Windows-only features. ✅ AI-Agent Ready: GitHub Copilot … winapp CLI — Single Command-Line Tool for Windows App Packaging, Identity, and Platform IntegrationRead more