Browse All Roundups (91)

Welcome to this week's Azure roundup, where the story centers on making AI agents and hybrid fleets operable, governable, and cost-aware. GPT-6 Astra reached general availability in Microsoft Foundry with production-ready deployment and governance options, while multiple guides dug into context engineering, egress lockdown, and secure agent infrastructure patterns for Kubernetes and edge. On the platform side, Azure Firewall explicit proxy went GA, Azure Arc shipped GA improvements for Arc-enabled Kubernetes certificates and Azure Virtual Desktop Hybrid, and API Management advanced GitOps workflows plus preview spend controls and OTLP telemetry for AI gateways.

This week in Security, the throughline is pushing enforcement into identity, networking, and auditable runtime controls as AI agents move from demos to deployable systems. GPT-6 Astra reached GA in Microsoft Foundry with enterprise deployment choices (throughput, region, residency) and governance hooks like Entra ID, RBAC, private networking, and monitoring that mirror how you secure other workloads. Guidance also sharpened around end-to-end agent hardening (egress containment, mediated tool use, Kubernetes policy layers, and OpenTelemetry-based evidence), while supply chain and CI/CD updates tightened provenance with key rotations, stronger OIDC-based publishing, and improved scanning and Actions permissions. Threat reports rounded out the week with practical detections for phishing evasion, helpdesk impersonation via Teams, and counterfeit installers, reinforcing the need for normalization, monitoring, and response-ready telemetry.

This week's AI roundup is about taking agentic systems from demos to production: GPT-6 Astra is now generally available in Microsoft Foundry and selectable in GitHub Copilot, while Copilot's roadmap shifts from choosing a single model to orchestrating multiple models at runtime. On the platform side, the focus is operational engineering (context control, durable memory, and observability) so agents stay predictable in cost and behavior as they run longer and use tools. Security guidance adds a reality check on egress control, attestation, and text normalization, and Copilot features like PR approvals and content exclusions raise the stakes for governance, identity, and auditability across IDE, CLI, and app workflows.

This week in the Weekly GitHub Copilot Roundup, the model lineup expanded (GPT-6 Astra GA, plus Gemini 3.8 Flash and Claude Fable 5.1) while deprecations and policy updates made it clear that model choice is now an admin and billing decision as much as a developer preference. At the same time, Project HydraFusion signaled a shift from picking one model to routing work across multiple models, with early experiments showing how orchestration can balance quality, latency, and spend. Governance also tightened across agent workflows, with content exclusions reaching the Copilot app and CLI, clearer identity constraints for cloud agents in Actions, and new budget expiration controls. On the workflow side, VS Code kept making agent sessions more reviewable, and Copilot code review entered a new phase with optional approvals that can satisfy branch protection rules if you choose to enable them.

This week's .NET roundup connects two practical threads: testing under real deployment constraints and building agent-style workflows you can run in production. MSTest 4.4 brings Native AOT test publishing so you can catch trimming and reflection issues earlier, while new .NET agent building blocks (Copilot SDK, lightweight harnesses, and MCP servers on Azure Functions) push tool calling and orchestration toward repeatable, auditable runs. On the day-to-day side, Visual Studio 2026 and VS Code updates focus on reducing context mistakes (scoped settings, worktrees, clearer Copilot context), and ecosystem updates like CodeQL 2.26.4 and Azure SDK releases highlight where CI and dependencies can shift under your feet.

This week in DevOps, the theme is clear: reduce friction while tightening control across collaboration, CI/CD, and governance. GitHub CLI takes a step toward fully terminal-first workflows (including inline media), while enterprise teams get practical tooling for live GHES-to-cloud migrations, runner lifecycle planning, and more precise token permissions. Supply-chain hardening continues with npm OIDC improvements, CodeQL updates for pipeline security, and concrete guidance for trusting third-party Actions, and on the ops side, agents and Azure governance move closer to production patterns with clearer boundaries, auditable workflows, and more "as code" outputs.

This week in Machine Learning, the focus shifts from prototypes to production guardrails, with Fabric data agents now generally available in Copilot Studio and new preview work on advanced DAX generation for semantic models. Fabric governance tightened with workspace outbound access controls, tenant-wide networking policy auditing, and connection recency signals that help reduce stale and single-owner risk. On data movement and interoperability, teams get clearer paths for private connectivity (Snowflake, Eventstream) and a GA transition from ODBC to ADBC that is worth validating early, while platform operations mature through capacity telemetry in Real-Time Hub and new CI/CD guidance to standardize deployments.

This week's Weekly AI Roundup focuses on turning AI assistants into systems you can govern, budget, and operate. GitHub Copilot moves toward clearer org guardrails with explicit billing behavior, a unified policy for chat and cloud agents, and expanded code review support for bot and agent-authored pull requests. On the tooling side, VS Code's Agent Host and Visual Studio's BYOM preview push multi-model, portable agent workflows closer to everyday development, while Microsoft Agent Framework and Foundry guidance emphasize tracing, evaluation, and constrained tool execution. Security and operations round out the picture with real-world attacks on AI gateways, stronger secret-handling patterns, and new cost-aware tooling that brings FinOps into the agent loop.

Welcome to this week's DevOps roundup, where GitHub sharpened the knobs teams use to manage CI/CD evidence and policy enforcement. Actions retention is expanding beyond artifacts and logs to include checks, workflow runs, and statuses starting October 1, 2026, so teams that depend on long-lived history for audits, incident timelines, or DORA-style reporting should review retention and export plans now. On the governance side, rule insights is now generally available at repo and org scopes with filters, bypass reporting, and CSV export, while push rules added path exceptions in preview to help you enforce strict controls where they matter without blocking low-risk paths.

This week in ML and data engineering, Microsoft Fabric pushed further on standardization and operability with Runtime 2.0 (Spark 4.1 and Delta Lake 4.2), a GPU query acceleration preview, and more policy-driven OneLake governance, including a preview mirror of Google Lakehouse Runtime Catalog metadata for Iceberg tables. On the workflow side, Fabric Warehouse CI/CD moved closer to familiar database project patterns with DacFx and a VS Code Schema Compare path, while agent updates (including GPT-5.1 references and MCP-based connections) continued the shift from assisted authoring to tool-connected automation that still needs validation and logging. Rounding out the week, new guidance focused on practical cost loops in Azure Databricks and on building AI-ready apps with vector search and RAG in Azure SQL Database, plus a broader view of how Work IQ, Foundry IQ, and Fabric IQ frame RAG as the grounding layer for enterprise agents.

This week's GitHub Copilot updates center on governance that admins can actually operate: unified policies across chat and cloud agents, clearer seat and usage billing behavior, and GA model controls that affect compliance and cost attribution. On the workflow side, the Copilot app's Customize tab is now the place to standardize MCP servers, plugins, and shared tools, while shared agent sessions in Slack and Microsoft Teams push Copilot work into auditable team spaces. Code review expands eligibility (including bot and cloud agent PRs) and adds better lifecycle tracking, and the IDE story keeps evolving with Visual Studio and VS Code adding practical model selection, effort controls, BYOM options, and even persistent agent sessions via Agent Host and AHP.

This week in Azure, the focus shifted from agent prototypes to the concrete work of shipping and operating agents in production using Azure AI Foundry, Microsoft Agent Framework, and MCP-based tool calling. Updates covered deployment and governance patterns (evaluation, tracing, and secret handling), plus real-world operational upgrades like Foundry Hosted Agents via azd and Azure SRE Agent VNet integration and Live Reports. Security guidance added urgency by calling out AI gateways and orchestrators as high-value targets, while networking and platform news (BGP route summarization, DNS plus Traffic Manager linked records, and zonal APIM Standard v2) rounded out the reliability story.

This week in .NET, the tooling story centered on agentic workflows becoming a first-class part of everyday development, with Visual Studio 2026 expanding Copilot into configurable, team-managed agents and adding practical Git upgrades like worktrees and deeper submodule support. Model choice and tool connectivity also tightened up as Bring Your Own Model (BYOM), Model Context Protocol (MCP), and the Microsoft Agent Framework converged into a clearer path from prototype agents to production hosts with observability and governance. On the platform side, C# 15 preview discussions focused on union types (plus closed hierarchies and safety-related changes), while debugging and testing workflows in both Visual Studio and VS Code moved toward tighter loops for reproducing, fixing, and validating failures.

This week's Security roundup focuses on how attackers and defenders are converging on the same idea: the control points between users, automation, and your internal network matter as much as endpoints. Microsoft Threat Intelligence detailed ClickFix (TerminalFix) tradecraft and a second wave of intrusions aimed at exposed AI gateways and orchestration layers, reinforcing priorities like tightening script execution, monitoring egress, and treating AI infrastructure like production identity and networking. On the defensive side, guidance and platform updates emphasized repeatable guardrails for agentic AI (verification, governed tool access, tracing, and secret boundaries), plus practical improvements in tenant governance and managed response coverage. We close with supply chain and collaboration controls, including GitHub moderation updates and evaluation patterns for LLM-based security workflows that help teams scale trust signals without losing auditability.

This week's AI roundup focuses on what it takes to run agents in production: move safety from prompt rules into enforceable environment controls, and make every tool call and permission boundary auditable. GitHub Copilot expanded shared agent sessions into Microsoft Teams and Slack while adding canvases and session management so collaborative work stays visible, reviewable, and tied to spend. MCP continued to solidify as the tooling layer for agents with connectors, hosted servers, and portable packaging, and Foundry updates added structured outputs and clearer guidance on when to choose prompt agents versus hosted orchestration. Across it all, the theme is practical governance - budgets, managed settings, approvals, and observability that keep agent-driven work predictable.

This week's GitHub Copilot updates focus on making agent work more collaborative, tool-aware, and governable. Shared agent sessions are now in public preview for Microsoft Teams and Slack, keeping conversations tied to secure sandboxes and pull requests so teams can review what changed and why. MCP momentum continued with hosted connector setup, practical tool servers (Playwright and SQL), and a portable Agent Plugins 1.0 packaging story that supports repeatable workflows across clients. Alongside new managed settings for JetBrains and more hands-on guidance for tokens and budgets, the thread running through the week is clear: scale Copilot usage by pairing better workflows with stronger controls.

This week's Security roundup focuses on tightening access and making security decisions easier to audit. GitHub shipped OAuth refresh tokens with stricter redirect hygiene and added incident response controls to revoke credentials by token type, while CodeQL and code scanning updates improved detection coverage and clarified governance with new audit signals and a "Mitigated" dismissal reason. On the platform side, Azure and Fabric continued the shift toward keyless patterns (managed identity), programmable encryption governance (CMK APIs), and stronger recovery posture with immutable SQL backups, alongside practical guidance for securing agentic systems by constraining tools, data access, and runtime.

This week in .NET is about making upgrades and AI features easier to run in real systems. Azure App Service Managed Instance reached GA, giving .NET Framework and Windows-dependent apps a more production-ready landing zone while you plan longer-term modernization. On the tooling side, Visual Studio and Copilot content focused on turning migration into a repeatable workflow (assessment, planning, checkpoints) that scales to large solutions and dependency graphs. In parallel, the AI story moved from single features to agentic architectures, with routing and failover in Microsoft.Extensions.AI, local-first Agent Framework patterns, and quality control loops that put reliability into application logic.

This week's Azure roundup centers on making production systems easier to run: agent runtimes get stronger isolation and safer tool access, while platform updates improve how you modernize apps and review infrastructure changes. Azure Web PubSub adds a chat-native layer in preview, App Service Managed Instance reaches GA for minimal-change migrations, and Deployment Stacks What-If now supports durable, reviewable diffs. On the reliability side, GitHub's outage write-up is a timely reminder to design for capacity and retries, and core platform updates (DNS, VM CPU controls, and Foundry model tooling) round out a week focused on practical ops and governance.

This week's ML roundup focuses on making agent experiences more governed and repeatable in Microsoft Fabric, from the new Fabric Data Warehouse MCP Server preview to tighter routing controls for Fabric data agents. On the data platform side, Fabric Data Warehouse added new tuning and cost tools, including GPU-powered Query Acceleration and Custom SQL Pools, plus practical guidance for Bronze-Silver-Gold layering. Security and operations also moved forward with CMK REST APIs, identity-based Event Hubs connections for Eventstream, and more production-friendly monitoring and dashboard KPIs to help teams run streaming workloads with clearer controls.

This week's DevOps roundup focuses on practical hardening work in GitHub that reduces auth friction while improving incident response. OAuth apps now support refresh tokens and up to 10 callback URLs, making it easier to run clean dev/staging/prod setups without risky wildcard redirects. On the operations side, GitHub Enterprise adds token-type-specific credential revocation with audit logs and user notifications, so security teams can contain incidents without forcing disruptive, broad resets.

This week's ML roundup spans practical platform work and model-facing guidance, from Fabric Runtime 2.0 reaching GA for Spark workloads to new Lakehouse targets for dbt jobs and better near real-time capacity monitoring in Real-Time Hub. On the application side, the RAG guidance makes a clear point: vector search is only candidate generation, and rank fusion plus reranking determine what your system actually uses. We also look at production-focused inference improvements on AKS with NVIDIA Dynamo and Blob Storage integrations, and a research update on CARE-X that combines vision-language modeling with calibration, grounding, and tool-augmented measurement for radiology workflows.

This week's DevOps roundup centers on two pressures colliding in real workflows: supply chain attacks that arrive through everyday repo automation, and a push to run AI agents with controls you can actually audit. We cover the ChainDrop (Shai-Hulud) npm worm and what it means for repository configs, tokens, and automated dependency updates, then dig into GitHub's tightening governance layer with OAuth hardening, ruleset migration, and new org-level Rule insights. We also look at agent-ready platform patterns (hardware-isolated sandboxes, APIM as a policy gateway, and OpenTelemetry-based run traces) plus practical reliability tooling that turns telemetry into SLI/SLO signals and ITSM-synced incidents.

This week's GitHub Copilot roundup is about operational reality: more models in the picker, more places Copilot runs, and better tools to understand what it costs. New options like Gemini 3.7 Flash, Grok 4.6, Kimi K3, and MAI-Code-1.1-Flash push model selection into normal platform governance, while improved token visibility and per-model usage reporting make spend easier to attribute. On the agent side, Agent Plugins 1.0 GA and smoother MCP setup make portable, tool-driven workflows more practical, with clearer patterns for guardrails like allowlists, least privilege, and PR-based review. Across IDEs and enterprise environments (including GHES 3.22 RC), the message is consistent: treat Copilot like part of your toolchain, with policies, instructions, and review paths that keep outputs safe and repeatable.

This week's AI roundup centers on shipping agents safely and paying for them predictably, from GitHub Copilot's expanding model lineup (and upcoming deprecations) to richer per-model token reporting for chargeback. MCP continued its shift into everyday tooling with faster VS Code setup, clearer enterprise guidance on auth and governance, and more concrete patterns for packaging and distributing tool access via Agent Plugins. On Azure and Foundry, the focus stayed operational: hosted agents as containers with tracing, sandboxed execution for risky workloads, and routing model and tool traffic through an AI gateway for consistent policy and telemetry. We also saw practical improvements in content extraction (Azure Content Understanding), RAG relevance discipline (reranking plus better vector indexing), and reliability and cost controls that treat agents like any other production service.

This week in Security focuses on how real-world attacks and platform changes are reshaping day-to-day defensive work. The ChainDrop (Shai-Hulud) npm worm is a reminder that supply chain incidents can spread through repo automation and developer tooling, so playbooks need to cover hooks, configs, and token scope - not just dependency diffs. On the platform side, GitHub shipped OAuth improvements (multiple redirect URIs and refresh tokens), GHES 3.22 RC tightened repository controls, and license detection updates will change some SBOM and compliance outputs. We also cover time-sensitive patch and version deadlines across Windows, .NET, and Defender for Endpoint on Android, plus practical guardrails for agentic workflows (sandboxes, gateways, MCP safety, and runtime tool-call policy).

This week in Azure, the story is how teams turn agent prototypes into production systems with repeatable runtimes, safer execution, and enforceable tool governance. Updates across Foundry Agent Service, Azure Functions Serverless Agents, and Container Apps Sandboxes show practical patterns for observability, isolation, and policy-driven control over tool calls and MCP-based integrations. On the operations side, Azure Monitor expands lower-cost logging options, Application Insights improves tracing in API Management policies, and the Reliability Starter Kit provides a runnable path from SLIs/SLOs to automated response. Rounding things out are workflow improvements in azd and App Service deployment, plus concrete guidance on cost control, retrieval quality (vector indexing and reranking), and the infrastructure work that supports faster, cheaper AI serving.

This week in .NET centers on staying current and testing early: Microsoft shipped August 2026 servicing updates for .NET 10, 9, 8, and .NET Framework, while .NET 11 Preview 7 continued to advance runtime, SDK, and the major app stacks. On the AI side, Microsoft.Extensions.AI added routing and failover primitives that help teams run multi-model and multi-endpoint setups more safely, and Copilot workflows picked up practical improvements from instruction hygiene guidance to local Ollama-based integrations. Rounding things out, Visual Studio 18.9 improved Git submodule management inside the IDE, and agent governance guidance focused on reducing Teams noise and enforcing runtime allow/deny tool-call policy with auditing.

This week in Security, the focus shifted from building agent guardrails to operating them safely in real enterprise environments, with clear patterns around least privilege, approval gates, and centrally enforced allowlists. On the developer platform side, identity-first CI/CD continued to replace long-lived secrets, from Azure DevOps workload identity authentication to NuGet.org moving API keys to a 30-day lifetime and pushing OIDC trusted publishing. Supply chain defenses broadened with expanded Dependabot malware advisories and fresh threat intel on an npm worm that abuses preinstall hooks to steal credentials. Hybrid and SOC operations rounded out the week with Azure Local confidential compute and SIEM integrations, plus case studies on macOS evasion tactics and Defender-driven ransomware containment.

This week's DevOps roundup focuses on keeping pull request review scalable as teams ship larger, AI-assisted changes. GitHub's stacked pull requests (public preview) introduce a practical way to split big diffs into reviewable layers across the UI, mobile, and the GitHub CLI, while new organization-level PR limits give maintainers a simpler way to manage contributor backlog. GitHub also adjusted Code Quality so it no longer auto-requests Copilot review, pushing teams to make automation and approval gates an explicit policy choice.

This week's Azure roundup focuses on what it takes to run AI agents reliably in production: durable execution, clear guardrails, and better day-2 visibility. Highlights include a durable pattern for MCP Tasks on App Service, built-in OpenTelemetry tracing for Functions Agents, and an approval-gated operations assistant architecture that keeps humans in control of write actions. We also cover Kubernetes isolation with Kars, broader model choice through Azure AI Foundry (including Fireworks AI GA), and practical guidance on evaluation and red teaming with Foundry and PyRIT.

This week's .NET roundup centers on making agent and MCP workloads reliable in the real world, from durable long-running tasks on Azure App Service to the stateless-first direction in MCP C# SDK 2.0. On the security and supply chain front, NuGet.org is capping API key lifetimes (pushing teams toward OIDC-based Trusted Publishing), while ASP.NET Core in .NET 11 preview expands automatic CSRF defenses using Fetch Metadata headers. We also cover practical developer experience updates, including richer CI test reporting in Microsoft.Testing.Platform, Blazor performance and lifecycle tweaks in .NET 11 Preview 7, and a concrete local AI sample for live speech-to-text with Foundry Local.

This week's GitHub Copilot updates were about making agent workflows portable, governable, and easier to operate. MCP and the Agent Plugins 1.0 spec continued to solidify a shared integration layer, while Azure DevOps added a hosted, Entra ID-authenticated Remote MCP Server that reduces local setup. On the operations side, Kimi K3 reached GA, September model deprecations got a clear timeline, and billing and ROI reporting moved further into first-party GitHub dashboards. Rounding it out, enterprise controls (MCP allow/deny lists, team-specialized managed settings, and third-party agent usage reporting) and day-to-day UX tweaks (review effort levels, comment-triggered automations, and better session visibility in VS Code) made Copilot feel more predictable in real team workflows.

This week's AI roundup focuses on agents becoming easier to package, safer to run, and simpler to govern across tools and teams. MCP took a practical step forward with a standardized plugin format, a stateless-first MCP C# SDK 2.0, and a hosted Azure DevOps Remote MCP Server that reduces self-managed plumbing. On Azure, the conversation shifted from demos to production patterns: durable task orchestration, approval gates, built-in OpenTelemetry traces, and Kubernetes trust boundaries for multi-agent safety. GitHub Copilot updates leaned into the operations layer with model lifecycle changes, MCP allowlists, automation triggers, and cost and usage reporting that admins can actually act on.

This week in machine learning, Microsoft Fabric focused on making data and events easier to reuse across analytics and ML pipelines, from OneLake mirroring previews (Azure Monitor Log Analytics and AWS Glue-cataloged Iceberg) to more end-to-end streaming options with Change Event Streaming, Eventhouse, and clearer event architecture guidance. On the operations side, Fabric added practical safeguards and runbook improvements with Item Recovery becoming the default, a new VNet gateway evaluation engine preview, and scheduled User Data Functions for managed recurring logic. We also got concrete agent-building guidance with Microsoft IQ MCP endpoints across web, work, Fabric, and Foundry, and Microsoft Research released PRISM2 pathology foundation model weights on Hugging Face for research and benchmarking.

This week's GitHub Copilot roundup focuses on model churn and tighter governance: Gemini deprecations forced admin action, while new default enablement and team-targeted model policies changed how access evolves over time. GitHub Models retired, pushing model operations toward Microsoft Foundry while Copilot stays the developer-facing layer for chat, agents, and review. On the product side, Grok 4.5 and MAI-Code-1-Flash add new tradeoffs around context, latency, and token efficiency, and client updates across VS Code, Visual Studio, JetBrains, and the Copilot app make agent workflows easier to run at scale. We also cover the practical side of adoption, including expanded usage rollups, budget enforcement that can actually stop overages, and managed settings that extend to the Copilot app, cloud agent, and remote control.

This week's AI roundup centers on turning fast-moving model and agent ecosystems into something you can run in production: governed, observable, and cost-controlled. GitHub retired GitHub Models while Copilot continued rotating available models, pushing enterprises to tighten policy management, managed settings, and usage reporting. At the same time, MCP gained more standardized building blocks (including the MCP C# SDK v2.0 and broader IDE integrations), and Azure added more runtime control points through API Management's AI Gateway tier and new cost-management toolsets for agents.

This week's DevOps roundup is anchored in supply chain hardening, with npm adding publish-time malware scanning, dual-use metadata requirements, and tighter 2FA enforcement that will change how automated releases behave. GitHub followed up with new guardrails in Actions and Dependabot, including approvals for suspicious workflow runs and broader malware advisory coverage to slow down common abuse paths. On the delivery side, stacked pull requests moved into public preview (and into the Copilot app), while Copilot governance expanded with MCP connections, enterprise managed settings, and clearer cost controls. We also cover practical platform work: Terraform AzureRM 5.0 GA, policy-driven Log Analytics retention, Azure APIM AI Gateway preview, and tooling updates that make agents easier to debug and safer to operate.

This week's Security roundup links attacker tradecraft with platform-side guardrails, starting with Microsoft's CaptiveCrunch reporting on Midnight Blizzard targeting travelers through captive portals and device code authentication abuse. On the supply chain front, npm and GitHub tightened automation paths with restrictions on bypass-2FA tokens, publish-time malware scanning, expanded malware advisories for Dependabot, and workflow runs that can be held for approval in public repos. Microsoft and Azure updates rounded out the week with identity and AI protections (including agentic SecOps and expanded external AI red teaming), plus concrete governance controls across Azure Policy, Fabric encryption, and data egress boundaries.

This week's .NET roundup centers on MCP becoming a practical foundation for agent tooling, with the MCP C# SDK v2.0 and new Agent Framework hooks that let agents discover skills at runtime with clearer safety boundaries. Visual Studio and VS Code also pushed further into agent-driven workflows, from a Copilot Chat Agent preview to an MCP-backed MSBuild binlog analyzer that can explain failures and performance bottlenecks. On the engineering side, the focus shifted to reliable automation (a unit-test agent that validates tests end-to-end and traced multi-agent orchestration with OpenTelemetry) plus a solid web security refresher on Fetch Metadata headers for defense-in-depth CSRF protection.