# Azure Microsoft Azure is a cloud computing platform providing infrastructure, developer tools, databases, and managed services. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Lenovo ThinkAgile VX850 V4 Takes On In-Memory Virtualization With New Deploy Tiers and Four-Hypervisor Express Bundles DevFeed: [Lenovo ThinkAgile VX850 V4 Takes On In-Memory Virtualization With New Deploy Tiers and Four-Hypervisor Express Bundles]() Original publisher: [Read original article]() Author: Harold Fritts Published: 2026-09-17T16:43:22Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [virtualization](), [Hardware](), [Deployment](), [hyper-v](), [Windows](), [Microsoft](), [Azure](), [nutanix](), [intel]() Tags: [azure](), [capacity](), [deployment](), [enterprise](), [hardware](), [hyper-v](), [intel](), [microsoft](), [nutanix](), [nvme](), [pcie](), [server](), [virtualization]() ### AI overview Lenovo added the four-socket ThinkAgile VX850 V4 to its virtualization lineup for demanding in-memory workloads. The launch also introduces three Infrastructure Deployment Services tiers and pre-validated Top Choice Express bundles covering Microsoft, Red Hat, SUSE, and Nutanix. Lenovo has not yet published the VX850 V4's own product specifications. ### Source excerpt Lenovo has added the ThinkAgile VX850 V4 to its virtualization lineup, a four-socket node it describes as purpose-built for highly virtualized and demanding in-memory workloads, and paired the launch with a three-tier deployment service framework and a set of pre-validated Top Choice Express bundles spanning Microsoft, Red Hat, SUSE, and Nutanix. The announcement follows Lenovo's The post Lenovo ThinkAgile VX850 V4 Takes On In-Memory Virtualization With New Deploy Tiers and Four-Hypervisor Express Bundles appeared first on StorageReview.com. ## Agents operate, humans govern: Scale your operations and reduce toil with Azure SRE Agent DevFeed: [Agents operate, humans govern: Scale your operations and reduce toil with Azure SRE Agent]() Original publisher: [Read original article]() Author: TNS Staff Published: 2026-09-15T16:21:45Z Content type: article Language: en Sources: [The New Stack]() Topics: [SRE](), [incident](), [Azure](), [observability](), [DevOps](), [Redis]() Tags: [agent](), [ai-agents](), [ai-operations](), [azure](), [code-review](), [deployment](), [devops](), [incident](), [microsoft-azure](), [monitoring](), [observability](), [post](), [redis](), [sponsor-microsoft-azure](), [sponsored](), [sponsored-post](), [sre](), [telemetry]() ### AI overview The article describes Azure SRE Agent as a system that analyzes telemetry, correlates deployment and monitoring data, investigates incidents, identifies root causes, recommends or prepares fixes, and supports mitigation and other operational tasks under human approval. It cites examples involving Microsoft service teams and InEight, including a recommendation to scale Redis. ### Source excerpt What if engineers could spend their time building and optimizing systems rather than maintaining them? It's 3 a.m., and the The post Agents operate, humans govern: Scale your operations and reduce toil with Azure SRE Agent appeared first on The New Stack. ## New in Symfony 8.2: KeyManagement Component DevFeed: [New in Symfony 8.2: KeyManagement Component]() Original publisher: [Read original article]() Author: Javier Eguiluz Published: 2026-09-15T07:11:00Z Content type: release Language: en Sources: [Symfony Blog]() Topics: [Symfony](), [Encryption](), [Amazon Web Services](), [Azure](), [Google]() Tags: [2026](), [api](), [article](), [aws](), [azure](), [backend](), [encryption](), [features](), [google](), [hashicorp-vault](), [kms](), [new-features](), [openssl](), [sdk](), [symfony]() ### AI overview Symfony 8.2 introduces an experimental KeyManagement component that provides one API for AWS KMS, Azure Key Vault, Google Cloud KMS, and HashiCorp Vault. It supports direct and envelope encryption, local development backends, provider bridges, console commands, debug-toolbar integration, and Doctrine support. ### Source excerpt This is the first article in a series showcasing the most important new features introduced by Symfony 8.2, which will be released at the end of November 2026. Contributed... ## Speeding Up Azure Durable Functions with Fan-Out/Fan-In and a Higher Concurrency Limit DevFeed: [Speeding Up Azure Durable Functions with Fan-Out/Fan-In and a Higher Concurrency Limit]() Original publisher: [Read original article]() Author: Michael Li Published: 2026-09-14T12:00:32Z Content type: tutorial Language: en Sources: [Atomic Object]() Topics: [Azure](), [Concurrent Programming](), [Code]() Tags: [apis](), [azure](), [azure-functions](), [batch](), [concurrency](), [development-practices](), [file](), [storage]() ### AI overview An Azure Durable Functions batch job was accelerated by combining fan-out/fan-in orchestration with a higher function-host concurrency limit. Together, the changes reduced a representative run from about 710 seconds to about 240 seconds. ### Source excerpt For one of our projects, we run a nightly job that generates a batch of files. It's a long process: pulling records from an upstream system, calling several APIs to gather info about each one, generating a file per record, and writing the results back to storage. For a small batch, this works fine, but [...] The post 2 Changes Made Our Azure Durable Functions 3X Faster appeared first on Atomic Spin. ## Security updates for Friday DevFeed: [Security updates for Friday]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-11T13:14:32Z Content type: news Language: en Sources: [LWN.net]() Topics: [Debian](), [cURL](), [Azure]() Tags: [azure](), [debian](), [ggml](), [kernel](), [linux](), [nvidia](), [oracle](), [python](), [ruby](), [security](), [updates]() ### AI overview Security updates have been issued across AlmaLinux, Debian, Fedora, Oracle, Red Hat, SUSE, and Ubuntu for a broad set of system libraries, tools, runtimes, and applications. ### Source excerpt Security updates have been issued by AlmaLinux (apr-util and qt6-qt5compat), Debian (libevent and ruby-rack), Fedora (bluez, corosync, curl, dokuwiki, grpcurl, libevent, and rest), Oracle (gstreamer1-plugins-bad-free, perl-DBI, python-urllib3, qt5-qtbase, qt6-qt5compat, and thunderbird), Red Hat (osbuild-composer), SUSE (azure-storage-azcopy, chromedriver, corosync, ggml-devel, helm, kernel, libmariadb-devel, libzypp, zypper, opensc, php7, tomcat10, and waylyrics), and Ubuntu (apache2, beets, glibc, kissfft, libebml, linux-nvidia-6.17, php8.1, php8.3, php8.5, and python2.7, python3.4, python3.5, python3.6, python3.7, python3.8, python3.9, python3.10, python3.11, python3.12, python3.14). ## Set Up Cloud OIDC From the Pulumi CLI DevFeed: [Set Up Cloud OIDC From the Pulumi CLI]() Original publisher: [Read original article]() Author: Sean Yeh Published: 2026-09-11T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [OpenID connect (OIDC)](), [Command-line interface](), [AWS IAM](), [Cloud](), [AWS Identity and Access Management (IAM)](), [Azure](), [Google Cloud Platform (GCP)]() Tags: [automated](), [aws](), [azure](), [cli](), [cloud](), [configuration](), [docs](), [esc](), [google-cloud](), [how-to](), [iam](), [identity](), [oidc](), [openid-connect](), [product](), [pulumi](), [pulumi-cli](), [security](), [terminal](), [workflow]() ### AI overview This tutorial explains how to use the Pulumi CLI command pulumi env setup to configure Pulumi ESC as an OIDC provider for AWS, Azure, and Google Cloud. It covers interactive onboarding, non-interactive flags for scripts and agents, cloud credentials, account selection, access policies, and automatic creation of identity providers, IAM roles, policy attachments, and ESC environments. ### Source excerpt Pulumi ESC can act as an OpenID Connect (OIDC) provider for AWS, Azure, and Google Cloud, issuing short-lived, signed tokens that these clouds exchange for temporary credentials. This eliminates hard-coded credentials and improves your security posture. Last year, we introduced an onboarding flow in the Pulumi Cloud console that makes it super easy to configure OIDC for your cloud provider in a few guided steps. We're bringing Pulumi Cloud into the CLI so agents can use its capabilities directly from the terminal, without requiring a human to complete steps in the console. The new pulumi env setup command brings OIDC onboarding to that workflow, with interactive prompts for guided setup and non-interactive flags for scripts and agents. pulumi env setup - how it works Run the command with your desired cloud provider (aws, azure, gcp). For example: pulumi env setup aws The command then asks what it needs to configure your cloud, including your credentials, the accounts to configure, and the level of access. The questions differ per cloud. For AWS, it asks: How to authenticate to AWS. It uses the credentials you already have, or it signs you in with AWS SSO. Which accounts to configure. Which policy to attach to the OIDC role. Choose AdministratorAccess for Pulumi Deployments, ReadOnlyAccess for Pulumi Insights, or any other policy ARN. Then, it will print out the plan: About to configure OIDC for organization my-org: account 111111111111: create role pulumi-esc-oidc-622e86ea-319ba4c675bb3c00-role attach arn:aws:iam::aws:policy/AdministratorAccess create ESC environment my-org/aws-login/sandbox-account-env Proceed? [yes/no] After you confirm, the command creates the identity provider, the IAM role, and the policy attachment in each account. It then creates one ESC Environment per account, with the aws-login provider already configured. Non-interactive setup You can also run the command without interactive prompts by passing in the necessary flags. Each cloud has its ow ## Leaving VMware Just Got Harder After Broadcom Pulled VDDK Downloads DevFeed: [Leaving VMware Just Got Harder After Broadcom Pulled VDDK Downloads]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-07T12:07:37Z Content type: news Language: en Sources: [Virtualization Howto]() Topics: [virtualization](), [migration](), [Azure](), [SDKs](), [Microsoft]() Tags: [azure](), [developer](), [home-lab](), [home-server](), [microsoft](), [migration](), [proxmox](), [tool](), [virtualization](), [vmware]() ### AI overview Broadcom has removed public download access to VMware's Virtual Disk Development Kit (VDDK), creating a potential obstacle for customers migrating away from VMware. The library is used by migration tools including Microsoft Azure Migrate, Red Hat's Migration Toolkit, Nutanix Move, VMware-to-KVM products, virt-v2v, and nbdkit. The article notes that affected links return errors and that no formal transition notice, deprecation announcement, or replacement has been identified. ### Source excerpt Just when we thought that Broadcom wouldn't be able to slow down customers moving off of vSphere to another platform. They may just now have done something that will have... The post Leaving VMware Just Got Harder After Broadcom Pulled VDDK Downloads appeared first on Virtualization Howto. ## OpenAI GPT-6 Astra Hits GA in Microsoft Foundry: Computer Use, Agentic Execution, and $10 to $75 per Million Tokens DevFeed: [OpenAI GPT-6 Astra Hits GA in Microsoft Foundry: Computer Use, Agentic Execution, and $10 to $75 per Million Tokens]() Original publisher: [Read original article]() Author: Harold Fritts Published: 2026-09-05T17:09:34Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [Microsoft](), [OpenAI](), [computer-use](), [Azure](), [Generative AI](), [Frontier Model](), [Security](), [Authorization](), [cloud-infrastructure](), [Software Engineering](), [pull-requests](), [dashboards]() Tags: [access-control](), [agentic](), [ai](), [apis](), [azure](), [computer-use](), [enterprise](), [frontier-model](), [generative-ai](), [governance](), [microsoft](), [openai](), [pull-requests](), [security]() ### AI overview Microsoft announced the general availability of OpenAI GPT-6 Astra in Microsoft Foundry on Azure. The frontier model is intended to support autonomous agentic workflows through multi-step planning, decision support, cross-application tool execution, and computer use. It can operate approved software interfaces, generate structured business artifacts, and assist with software engineering, dashboard creation, record updates, form processing, and interface testing. Microsoft Foundry provides scoped credentials, role-based access control, human-approval checkpoints, and identity controls for containment. ### Source excerpt Microsoft announced the general availability of GPT-6 Astra within Microsoft Foundry on Azure. The frontier model is engineered to transition enterprise generative AI from interactive chat interfaces toward autonomous agentic workflows, providing multi-step planning, deliberate decision support, and cross-application tool execution. OpenAI calls Astra its most aligned model to date, and Microsoft says it is The post OpenAI GPT-6 Astra Hits GA in Microsoft Foundry: Computer Use, Agentic Execution, and $10 to $75 per Million Tokens appeared first on StorageReview.com. ## How to verify your Azure Application Gateway is zone-redundant DevFeed: [How to verify your Azure Application Gateway is zone-redundant]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-09-04T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Azure](), [Availability](), [Cloud](), [web applications](), [Command-line interface](), [Shared Responsibility Model]() Tags: [availability](), [azure](), [cli](), [cloud](), [features](), [high-availability](), [how-to](), [infrastructure](), [post](), [shared-responsibility](), [web-applications]() ### AI overview This how-to article explains availability-zone redundancy for Azure Application Gateway. It describes the redundancy model, the shared responsibility boundary, and how to verify whether a gateway is zone-redundant or zonal using Azure CLI and Resource Graph. It also cautions that a redundant gateway does not by itself make the services behind it redundant. ### Source excerpt This post explains what zone redundancy means for Application Gateway, how to confirm whether a given gateway is zone-redundant or zonal using the Azure CLI and Resource Graph, and why a gateway surviving a zone failure doesn't mean the services calling through it will. ## Try Azure SRE Agent with no always-on charges DevFeed: [Try Azure SRE Agent with no always-on charges]() Original publisher: [Read original article]() Author: Nir Mashkowski Published: 2026-08-25T15:00:00Z Content type: release Language: en Sources: [Developer Blogs]() Topics: [Azure](), [site-reliability-engineering](), [telemetry](), [incident management](), [Cloud]() Tags: [announcement](), [azure](), [cloud](), [incident-management](), [microsoft](), [microsoft-for-developers](), [sre](), [telemetry]() ### AI overview Microsoft announces a 30-day trial for Azure SRE Agent with no charges for setup time or keeping agents ready. The announcement also covers general availability of VNet integration and public preview of Live Reports. Active Azure Agent Unit charges apply when agents perform work. ### Source excerpt We are happy to announce a 30-day trial experience for Azure SRE Agent. New customers can create and configure the SRE Agent at their own pace, with no charges for setup time or keeping agents ready. During the trial, you can connect your agents to telemetry, source code, incident management platforms, and other operational tools, [...] The post Try Azure SRE Agent with no always-on charges appeared first on Microsoft for Developers. ## From dotnet run to Foundry Hosted Agent in 3 lines of C# DevFeed: [From dotnet run to Foundry Hosted Agent in 3 lines of C#]() Original publisher: [Read original article]() Author: Bruno Capuano Published: 2026-08-24T19:00:00Z Content type: tutorial Language: en Sources: [.NET Blog]() Topics: [hosted-agents](), [Microsoft Agent Framework](), [Azure](), [C#](), [.NET](), [NuGet](), [Entra ID](), [Containers](), [telemetry]() Tags: [agent](), [agents](), [ai](), [azd](), [azure](), [blog](), [c-sharp](), [csharp](), [dotnet](), [entra-id](), [framework](), [hosted-agents](), [hosting](), [infrastructure](), [microsoft](), [microsoft-agent-framework](), [microsoft-foundry](), [net](), [nuget](), [observability](), [post](), [production]() ### AI overview This tutorial shows how to deploy a Microsoft Agent Framework console agent as a Foundry Hosted Agent using one NuGet package, three lines of C#, and two commands. Foundry provides managed Azure infrastructure, scaling, identity, session state, observability, and lifecycle management. ### Source excerpt You built an agent with Microsoft Agent Framework and it works great on your machine. Now what? Turns out deploying it to production takes 1 NuGet package, 3 lines of C#, and 2 commands. Let's do it. The post From dotnet run to Foundry Hosted Agent in 3 lines of C# appeared first on .NET Blog. ## Monitor Azure Functions across every hosting plan with Datadog DevFeed: [Monitor Azure Functions across every hosting plan with Datadog]() Original publisher: [Read original article]() Author: Duncan Harvey; Kathie Huang; Piyali Banerjee Published: 2026-08-24T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [Azure](), [serverless monitoring](), [Serverless](), [telemetry](), [tracing](), [Traces](), [Application Performance Management (APM)](), [cpu](), [Node.js](), [Python](), [.NET]() Tags: [apm](), [azure](), [azure-functions](), [cpu](), [digital-experience-monitoring](), [metrics](), [monitor](), [monitoring](), [net](), [node-js](), [observability](), [performance](), [python](), [serverless](), [serverless-monitoring](), [telemetry](), [traces](), [tracing]() ### AI overview Datadog Serverless Monitoring expands observability for Azure Functions across Linux and Windows hosting plans, with telemetry collection, distributed tracing, enhanced CPU metrics, and continuous profiling. ### Source excerpt Trace requests, get enhanced CPU metrics, and profile code across Azure Functions hosting plans with Datadog Serverless Monitoring. ## Why GitHub feels less reliable lately DevFeed: [Why GitHub feels less reliable lately]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-23T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [GitHub](), [incident](), [migration](), [systems](), [Azure](), [GitHub Actions](), [pull-requests]() Tags: [autoscaling](), [capacity](), [concurrency](), [data-centers](), [deployment](), [github](), [incident](), [incident-management](), [istio](), [reliability](), [request](), [resilience](), [sre](), [transformation]() ### AI overview The article argues that GitHub's recent reliability problems reflect the difficult middle of a major infrastructure transformation. It connects incidents to migration complexity, unsafe automation, configuration mistakes, capacity and concurrency weaknesses, database migration errors, and autoscaling problems. ### Source excerpt GitHub is not having one outage problem. Its recent incident reports show the difficult middle of a platform transformation. ## Avoid Azure secret rotation with secretless authentication DevFeed: [Avoid Azure secret rotation with secretless authentication]() Original publisher: [Read original article]() Author: Cody Murray-Bruce; Ben Johnson-Staub Published: 2026-08-12T00:00:00Z Content type: tutorial Language: en Sources: [Datadog | The Monitor blog]() Topics: [Azure](), [Authentication](), [Entra ID](), [OpenID connect (OIDC)](), [telemetry](), [Terraform](), [migration]() Tags: [authentication](), [azure](), [cli](), [entra-id](), [identity-and-access-management](), [infrastructure-monitoring](), [integration](), [microsoft](), [migration](), [oidc](), [secrets](), [telemetry](), [terraform]() ### AI overview This article explains how Datadog's secretless authentication for Azure replaces long-lived client secrets with federated identity using Microsoft Entra ID and OpenID Connect. It describes the short-lived token flow and configuration or migration options through Quickstart, Terraform, the Azure CLI, or the Azure portal. ### Source excerpt Learn how secretless authentication for Datadog's Azure integration helps prevent telemetry interruptions that result from expired client secrets. ## Pushing container images to China: what we learned the hard way DevFeed: [Pushing container images to China: what we learned the hard way]() Original publisher: [Read original article]() Author: Team Honey Badger Published: 2026-08-06T15:34:42Z Content type: article Language: en Sources: [Giant Swarm Blog]() Topics: [container images](), [ACR](), [Azure](), [Kubernetes](), [AI Infrastructure](), [Inference](), [Cloud]() Tags: [acr](), [ai-infrastructure](), [azure](), [china](), [circleci](), [container](), [container-image-building](), [container-images](), [firewall](), [inference](), [kubernetes]() ### AI overview This article explains why container image pushes to China can be much slower than elsewhere. It attributes the problem to China's separate registry infrastructure and cross-border transfer throttling, and says Giant Swarm cut delivery time to under two minutes with a split push through Singapore. ### Source excerpt Why container pushes to China take 30 minutes, and how Giant Swarm cut it to under 2 with a split push through Singapore. ## Build Azure Skills Faster with Cloud Academy, a Visual Studio Subscriber Benefit DevFeed: [Build Azure Skills Faster with Cloud Academy, a Visual Studio Subscriber Benefit]() Original publisher: [Read original article]() Author: James Rempt Published: 2026-08-04T14:00:38Z Content type: article Language: en Sources: [Visual Studio Blog]() Topics: [Azure](), [Visual Studio](), [Cloud](), [Artificial Intelligence](), [DevOps](), [Automation](), [workflow automation](), [Prompt Engineering]() Tags: [ai](), [automation](), [azure](), [cloud](), [devops](), [learn](), [learning](), [prompt-engineering](), [visual-studio](), [visual-studio-subscriptions]() ### AI overview This article presents Cloud Academy as a Visual Studio subscriber benefit for building practical Azure skills. It highlights hands-on labs, certification-focused learning paths, assessments, sandbox experimentation, and AI-powered guidance, with examples spanning Azure administration, deployment, DevOps, security, cost optimization, Azure AI, and prompt engineering. ### Source excerpt If you've been looking for a practical way to build Azure skills, Cloud Academy (a QA company) gives Visual Studio subscribers hands-on learning that fits into busy schedules. Whether you're new to Azure, expanding your cloud expertise, working towards certifications or preparing for more advanced projects, this benefit helps you learn by doing. What you'll find in Cloud Academy The Cloud Academy benefit gives Visual Studio subscribers a flexible [...] The post Build Azure Skills Faster with Cloud Academy, a Visual Studio Subscriber Benefit appeared first on Visual Studio Blog. ## Discovered Stacks: One Place for All Your Infrastructure DevFeed: [Discovered Stacks: One Place for All Your Infrastructure]() Original publisher: [Read original article]() Author: Alejandro Cotroneo Published: 2026-07-30T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Infrastructure as code](), [migration](), [AWS CloudFormation](), [Azure](), [Terraform](), [Cloud]() Tags: [aws-cloudformation](), [azure](), [cloud](), [deployment](), [features](), [fragmentation](), [governance](), [infrastructure](), [insights](), [migration](), [product](), [pulumi-cloud](), [terraform]() ### AI overview Pulumi launches Discovered Stacks, a Pulumi Cloud capability that models AWS CloudFormation stacks and Azure Resource Manager deployments alongside Pulumi stacks. It tracks resource migration status from live state and supports migration into Pulumi management with verification before changes are made. ### Source excerpt Today we're launching Discovered Stacks: Pulumi Cloud now models your AWS CloudFormation stacks and Azure Resource Manager deployments as stacks, right alongside your Pulumi IaC stacks. And when you're ready to bring them under Pulumi management, migration is built in, with every resource tracked until the code provably matches the cloud. Why: your infrastructure doesn't live in one tool Almost nobody's cloud estate is a single technology. There's the CloudFormation that came with the AWS account, the ARM templates from the Azure team, the Terraform from an acquisition, and the Pulumi you're standardizing on. Each tool has its own console, its own grouping, its own idea of state, and no single place shows you everything you run. That fragmentation is also why migrations stall. Moving a stack to Pulumi has never been the hard part; knowing where you stand is. The tracking lives in a spreadsheet, the spreadsheet goes stale the day it's written, and six months later nobody can say which of the 800 resources made it across and which were quietly forgotten. Nothing gets lost Discovered Stacks gives you confidence that your migration plan or governance efforts will include all resources. This catches a common failure mode where resources are missed by your existing migration scripts or automations. When Pulumi Insights scans your accounts, every CloudFormation stack and ARM deployment becomes a discovered stack, and every resource in it appears as a row with an explicit migration status: ready to migrate, requiring review before migration, or already migrated. Every status is computed from live state on both ends -- what Pulumi manages and what the source tool reports -- so it's never a stale annotation someone forgot to update. Each resource shows its origin type (AWS::S3::Bucket) next to its Pulumi type (aws:s3/bucket:Bucket), with the origin properties side by side with Pulumi's view, so you can verify that Pulumi sees exactly what your source tool sees before you change ## The Fellowship of Code: My Quest at Ruby for Good in Ghent DevFeed: [The Fellowship of Code: My Quest at Ruby for Good in Ghent]() Original publisher: [Read original article]() Author: Fiona McLaren Published: 2026-07-27T14:09:36Z Content type: opinion Language: en Sources: [FreeAgent]() Topics: [Ruby](), [Rails](), [Azure](), [Content Management System](), [Open Source]() Tags: [azure](), [cms](), [coding](), [conferences](), [culture](), [development](), [open-source](), [open-source-code](), [rails](), [ruby](), [ruby-on-rails]() ### AI overview A junior developer describes attending Ruby for Good in Ghent and contributing to SkillRX, a project providing medical education materials in low-resource areas. The team addressed inefficient Azure file-storage synchronization by planning Beacons that communicate directly with the health professionals' CMS. ### Source excerpt It isn't very hard to pitch tech conferences. Offering a getaway from the usual desk work, a chance to pick up on new wisdoms from like-minded and genuinely inspiring folk, and room in the itinerary for sightseeing and socialising in the hip host city in between times? It's a no-brainer... well, for most. I had [...] ## Mastering the 50-state AI maze: A platform strategy for sovereignty DevFeed: [Mastering the 50-state AI maze: A platform strategy for sovereignty]() Original publisher: [Read original article]() Author: Marc Mangus Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [AI Strategy](), [Artificial Intelligence](), [Generative AI](), [Azure](), [Microsoft](), [cloud-infrastructure]() Tags: [ai](), [azure](), [compliance](), [developer](), [healthcare](), [microsoft](), [platform](), [policy](), [regulatory](), [strategy](), [vendor-lock-in]() ### AI overview The article argues that healthcare organizations need platform sovereignty to manage conflicting AI regulations across U.S. states. It presents policy-as-code, golden paths, and internal developer portals as scalable defenses against compliance risk and vendor lock-in, illustrated by a health insurer's costly replacement of Microsoft AI and Azure-based services. ### Source excerpt As state AI laws collide, healthcare organizations face mounting compliance risk and vendor lock-in. Learn why platform sovereignty--policy-as-code, golden paths, and internal developer portals--is the only scalable defense against a 50-state regulatory civil war ## Connect Your Cloud Accounts to Pulumi in Minutes DevFeed: [Connect Your Cloud Accounts to Pulumi in Minutes]() Original publisher: [Read original article]() Author: Levi Blackstone Published: 2026-07-15T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Cloud](), [Amazon Web Services](), [Azure](), [OpenID connect (OIDC)](), [Google Cloud Platform (GCP)](), [configuration](), [Authentication]() Tags: [aws](), [azure](), [cloud](), [configuration](), [esc](), [google-cloud](), [governance](), [identity](), [insights](), [openid-connect](), [policy](), [product](), [pulumi-cloud]() ### AI overview Pulumi introduces a Connect cloud accounts wizard for discovering and onboarding AWS accounts, Azure subscriptions, and Google Cloud projects in a single guided flow. It automates OIDC setup, creates Pulumi ESC environments, and applies discovery scans and policy packs. ### Source excerpt Pulumi Insights gives you visibility and governance across your entire cloud footprint, but that visibility is only as complete as the set of accounts you've connected. Until now, connecting an account meant repeating a manual setup for each one: OIDC configuration, hand-written Pulumi ESC environments, and per-account scan and policy setup. For an organization with dozens or hundreds of AWS accounts, Azure subscriptions, or Google Cloud projects, that per-account friction was the biggest obstacle to getting a complete picture. Today, the new Connect cloud accounts wizard removes it: discover every account in your cloud organization, select the ones you want, and onboard them all in a single guided flow. From hours of setup to a single flow The time savings are real: connecting a batch of accounts across AWS, Azure, and Google Cloud takes about three minutes end to end. Setting up those same accounts with the manual per-account workflow would take hours to days. The wizard handles the entire onboarding lifecycle for AWS, Microsoft Azure, and Google Cloud: Bulk discovery: Authenticate once with your cloud organization and the wizard lists every account, subscription, or project you can access. Accounts that are already connected are recognized and skipped. Automatic OIDC setup: The recommended flows configure each account with short-lived credentials based on OpenID Connect (OIDC) and workload identity federation. No long-lived cloud secrets are stored in Pulumi Cloud. ESC environments, created for you: The wizard generates Pulumi ESC environments that follow the best practices from the manual OIDC guides -- environments that previously had to be authored one by one. Scans and policies from day one: By default, scheduled discovery scans and a pre-built policy pack are applied to every account as part of setup: the Pulumi Best Practices pack on the Team and Enterprise editions, or a compliance pack (CIS, or NIST 800-53 for AWS and Google Cloud) on Business Critical. Ho ## Eliminate Reliability Blind Spots in AWS, Azure, and GCP DevFeed: [Eliminate Reliability Blind Spots in AWS, Azure, and GCP]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-07-14T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Cloud](), [Kubernetes](), [Resilience](), [Amazon Web Services](), [Azure](), [Chaos Engineering]() Tags: [availability](), [aws](), [azure](), [containers](), [deployment](), [experimentation](), [features](), [gcp](), [gremlin](), [kubernetes](), [orchestration](), [outages](), [resilience](), [uptime]() ### AI overview Gremlin's expanded Detected Risks feature automatically identifies high-priority reliability risks across AWS, Azure, GCP, and Kubernetes environments. It is designed to reveal issues such as misconfigured deployments, crash-looping containers, missing readiness probes, and poor pod distribution before they cause outages. ### Source excerpt Discover reliability risks without running a single test. See how Gremlin identifies high-priority reliability risks across AWS, Azure, and GCP to prevent outages. ## Introducing the Hyperscaler GTM Playbook DevFeed: [Introducing the Hyperscaler GTM Playbook]() Original publisher: [Read original article]() Author: flashdba Published: 2026-07-13T21:11:00Z Content type: article Language: en Sources: [flashdba]() Topics: [Cloud](), [cloud-infrastructure](), [Amazon Web Services](), [Azure](), [Google]() Tags: [articles](), [aws](), [azure](), [cloud](), [cloud-alliances](), [cloud-co-sell](), [cloud-marketplace](), [google-cloud](), [guide](), [hyperscaler](), [isv](), [partner](), [practitioner]() ### AI overview A vendor-neutral 16-article Hyperscaler GTM Playbook explains cloud alliances, co-sell, and marketplace operations for ISVs selling alongside AWS, Azure, and Google Cloud. It emphasizes the practical differences among the hyperscalers and the importance of whether software runs in the provider's or the customer's cloud account. ### Source excerpt A vendor-neutral practitioner guide on cloud alliances, co-sell and marketplace - 16 articles covering everything from partner programs to private offers, for ISVs selling with AWS, Azure and Google Cloud. ## Core dump epidemiology: fixing an 18-year-old bug DevFeed: [Core dump epidemiology: fixing an 18-year-old bug]() Original publisher: [Read original article]() Published: 2026-06-30T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [bug](), [OpenAI](), [Rockset](), [C++](), [Data Infrastructure](), [Azure](), [Hardware](), [race-condition](), [Open Source](), [Streaming]() Tags: [azure](), [bug](), [c-plus-plus](), [data-infrastructure](), [engineering](), [hardware](), [open-source](), [openai](), [race-condition](), [software]() ### AI overview OpenAI engineers analyzed a large population of core dumps to investigate rare crashes in the Rockset service. The investigation uncovered two unrelated causes: silent CPU corruption on an Azure host and an 18-year-old race condition in GNU libunwind. ### Source excerpt OpenAI engineers used large-scale core dump analysis to debug rare infrastructure crashes, uncovering both a hardware fault and a long-standing software bug. ## Six Live Kubernetes Recommendations: AKS, Cilium, Rate Limiting, and More DevFeed: [Six Live Kubernetes Recommendations: AKS, Cilium, Rate Limiting, and More]() Original publisher: [Read original article]() Author: Adam Gordon Bell Published: 2026-06-15T12:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [Kubernetes](), [Azure](), [C#](), [Cilium](), [Docker Hub](), [Web app]() Tags: [ai-coding](), [aks](), [azure](), [c-sharp](), [cilium](), [container-registry](), [dotnet](), [kubernetes](), [tutorials](), [web-app]() ### AI overview A writeup of a live workshop on building an AKS cluster, Azure Container Registry, and a random-cat web app in C# with Pulumi. It presents recommendations for working with Kubernetes on Azure, including choosing a language the team already uses, and describes how Docker Hub rate limiting affected the workshop. ### Source excerpt On June 10th, Engin and I ran a live workshop building an AKS cluster, an Azure Container Registry, and a random-cat web app from scratch in C#. This is the writeup, including the parts we didn't get to live. Since this post was published, Pulumi has added first-class support for HashiCorp Configuration Language (HCL). You can now write Pulumi programs in HCL directly, alongside general-purpose languages like TypeScript, Python, Go, and C#. To see how it works, see Pulumi HCL. Live demos keep you honest. On June 10th my AKS workshop went a little sideways. Partway through, Docker Hub rate-limited my image pull and we had to adapt the content on the fly. The original plan was to stand up an AKS cluster with Cilium, an Azure Container Registry with the cluster's pull permission wired in code, and a random-cat web app, then split the infrastructure from the workload into separate Pulumi stacks. Live, we didn't make it through all of that, but we had some fun tangents and it turned out to be a great session. So here are my six recommendations for working with Kubernetes on Azure from this recent workshop. 1. Pick the language your team already uses I opened the session by asking the room what language they prefer to work in, with one caveat from me: "Hopefully, it's not PowerShell because this is not in PowerShell." We got some C# answers and zero requests for PowerShell, which works out, because the whole workshop is in PowerShell C#. I chose C# because, first, I genuinely love the language. I spent the early part of my career as a C# developer, and on Azure it just makes sense. Second, an Azure workshop tends to draw a big turnout of C# devs, and if they aren't C# devs themselves, they often work somewhere the backend team uses C#. Pulumi lets you bring that language to your infrastructure rather than learn a new DSL. AI coding assistants also came up. LLMs have substantially more C# and Go in their training data than HCL or Bicep. As I put it live: "If you're working [Next page]()