Lumen and Microsoft deepen joint sales effort for enterprise AI networks
The companies want customers to plan connectivity and cloud AI together. Broader Azure and Marketplace availability remains a plan, not a completed rollout.
Loading page…
The companies want customers to plan connectivity and cloud AI together. Broader Azure and Marketplace availability remains a plan, not a completed rollout.
Listen to this story
The November 2, 2026 announcement gives Lumen and Microsoft a broader plan to sell network connectivity alongside Azure migration and enterprise AI projects. The change is coordinated account planning, not a newly launched networking service: Alkira is the current Marketplace option, while wider access to Lumen capabilities through Azure remains planned. The companies also intend to explore how connectivity could support Microsoft’s agent governance and security tools, but have not announced a delivered agent-control offering.
Joint account planning will bring network upgrades, Azure migrations and AI projects into the same enterprise sales process.
Lumen Connect’s Alkira is already available through Microsoft Marketplace, offering cloud-native networking with orchestration through a single portal.
Broader Lumen capabilities on Azure and Marketplace are still planned; the release cites development delays, partner changes and customer adoption as risks.
Lumen and Microsoft are promising closer coordination between enterprise networks and cloud AI—not announcing a finished new networking service. On November 2, 2026, they announced an expanded joint sales collaboration aimed at connecting the data, applications and infrastructure behind AI workloads. More Lumen capabilities are intended for Azure, but that work remains ahead.
The practical change is in how the companies intend to approach enterprise customers. They plan to extend joint account planning where network upgrades, migration to Azure and AI projects overlap. The aim is to bring decisions about connectivity, security, data movement and computing infrastructure into the same planning process, rather than handle the network separately.
Their stated problem is that business data and applications sit across public clouds, private data centers, offices and partner environments. Those locations must connect for the proposed Azure-based AI work. Microsoft executive Katy Brown described the collaboration as helping customers connect existing environments to Azure while retaining choices about how they do it.
There is already a purchasing option: Alkira, a Lumen Connect solution, is available through Microsoft Marketplace for cloud-native networking. The companies describe Lumen with Alkira as combining network infrastructure with orchestration—software that coordinates network connections—through a single portal for connecting, securing and managing networks across private and public cloud environments.
Lumen’s larger ambition is to bring its full suite of cloud networking and application connectivity capabilities to Azure. The companies will identify opportunities for additional offerings over time. The release’s forward-looking statement explicitly covers future availability and integration, and names development delays, changes in partner plans and customer adoption among risks to those expectations.
The collaboration builds on work in both directions. Lumen’s Private Connectivity Fabric supports Microsoft’s data-center connections, while Azure supports Lumen’s own workload modernization. For enterprise customers, the announcement describes using Azure’s native networking tools, including Azure Virtual WAN, alongside Lumen connectivity according to business requirements. It does not frame those tools as mutually exclusive choices.
A further exploratory strand concerns AI agents: systems intended to carry out business processes, rather than only answer questions. Microsoft and Lumen plan to explore how connectivity could work with Microsoft’s agent governance and security capabilities. Their stated concern extends beyond moving data to controlling an environment that spans networks, cloud infrastructure, identities, applications and agents. That work broadens the collaboration’s intended scope beyond network access to the rules and safeguards surrounding agent-operated business processes.
Loading discussion...
Join the conversation
Explain which decisions benefit from coordination—and which should stay separate.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.