Expert PerspectivesPrivate Wireless

Nokia Enterprise Campus Edge Is Changing Owners: The SI’s Pre-Close Checklist

Quick Answer: Nokia has agreed to sell its Enterprise Campus Edge (ECE) business to the private equity firm Aurelius, with closing expected in the first half of 2027. The Digital Automation Cloud (DAC) platform, MX Industrial Edge (MXIE) and Modular Private Wireless (MPW) move to the new owner, while Nokia keeps the radios. For a systems integrator (SI), PrivateLTEand5G recommends three steps before closing: rank each client by what its network depends on, get written answers from Nokia on radio supply, the contracting entity and the patent license, and add a review point to any renewal signed before the deal closes. The same method applies to any future vendor change.

Nearly 900 private wireless customers, in industries including manufacturing, mining, logistics, airports, ports and power generation, run on the Nokia Enterprise Campus Edge portfolio, according to Nokia’s announcement of the sale on October 13, 2026. Where an integrator sold or supports one of those networks, the client’s first call goes there, and this quarter the first thing clients ask is whether the network is safe.

Nokia and Aurelius say they are cooperating to ensure continuity for existing customers and employees, and ECE staff are expected to transfer with the business at closing. Neither company addressed transition services or radio supply in its announcement.

The details that decide what continuity means for a particular client sit in order confirmations, partner addenda and the DAC terms that applied when the network went live.

What Moves to Aurelius and What Nokia Keeps

After closing, a DAC network will rely on two owners: ECE under Aurelius for the platform, and Nokia for the radios and patent licensing. When Nokia announced in November 2025 that ECE would leave its core business, PrivateLTEand5G read that strategic pivot as a sign of a maturing market with more room for integrators. The checklist starts from that split, because many of the open questions sit at the hand-off between ECE and Nokia.

The Platform Side

Aurelius is taking the whole Nokia Enterprise Campus Edge portfolio apart from Nokia Drone Networks, which stays with Nokia (RCR Wireless, October 14, 2026). Four parts affect an integrator’s clients directly:

•    DAC: the private wireless core plus the cloud-based DAC manager, which handles configuration, alarms, troubleshooting, subscriber provisioning and software management.

•    MXIE: the on-premises edge platform that can host the core alongside industrial and AI applications from Nokia’s catalog.

•    MPW: the platform for larger and wide-area private networks.

• Industrial devices and applications: the ruggedized handhelds, other devices and software sold alongside DAC.

The Radio and Patent Side

Nokia keeps its radio access network (RAN) business, and ECE is set to go on pairing Nokia radios with its own core, edge, devices and applications. The commercial terms behind that arrangement aren’t public; a radio licensing agreement between Nokia and Aurelius was expected but unconfirmed when RCR Wireless covered the deal on October 13, 2026.

The split is already visible at the Thames Freeport deployment, announced as complete in November 2026, where DAC and MXIE came from ECE and the radio equipment came through Nokia’s mobile infrastructure division (RCR Wireless, November 10, 2026). The patent license also traces back to Nokia, since under the IP-as-a-Service terms for DAC (version 1.0, applicable from January 25, 2024) the licensor is Nokia Technologies Oy, the group’s patent-licensing business.

MXIE also hosts AI workloads such as video analytics and worker-safety applications, and Aurelius has pointed to AI-powered industrial automation as an area to expand into. Until the new owner publishes a roadmap, PrivateLTEand5G treats that as intent, and an integrator can’t yet tell a client what will get priority on MXIE.

Table 1 maps each part of a Nokia DAC network to its owner after closing.

ComponentOwner after closingWhat the client relies on it forOpen question before closing
DAC core and DAC managerECE under AureliusCore functions, cloud management, subscriber provisioning, software updatesWhere DAC manager is hosted after closing, and for how long
MXIEECE under AureliusOn-site compute for the core and for industrial and AI applicationsSupport for third-party catalog applications and hardware refresh
MPWECE under AureliusLarger and wide-area private networksSupport for MPW sites that Nokia deploys with its own RAN
Industrial devices and applicationsECE under AureliusHandhelds, other devices and software sold with DACWarranty, replacement and application licenses
Nokia radios (RAN)NokiaRadio accessSupply terms and supported combinations with the ECE core
Patent license (IP-as-a-Service)Nokia Technologies Oy as licensorPatent license and indemnity attached to each DAC subscriptionHow the license continues once licensor and platform owner differ

Sort Every Nokia Client by What Its Network Depends On

Before any client conversation, PrivateLTEand5G recommends an exposure ranking across the installed base. The inputs already exist: each client’s order confirmation, the DAC manager view and the integrator’s own support records.

Seven factors decide where a client lands:

•    Subscription end date: Software licenses expire with the subscription term, and Nokia may include functionality that makes the service unusable on expiry, under Nokia’s DAC Terms of Service (version 1.0, applicable from November 3, 2023).

•    Cloud management: DAC keeps operating when the management plane is down, Nokia says, but under the same Terms of Service, services may become inoperable if the internet connection isn’t re-established within 30 days.

•    CBRS path to the SAS: For US sites in the Citizens Broadband Radio Service (CBRS) band, the network must stay connected to the Spectrum Access System (SAS) through DAC under Nokia’s CBRS supplementary terms (version 1.0, applicable from November 3, 2023), and it turns off while that connection is unavailable.

•    MXIE workloads: AI and other applications from Nokia’s catalog, including third-party applications sold under their own merchant terms, add a second layer of licenses at renewal.

•    Industrial devices: Nokia handhelds and other devices bought with DAC fall under separate hardware terms, including their own warranty provisions.

•    Subscriber data and SIM credentials: The subscriber database runs in the core on site, so the open question is who holds the identifier range and SIM keys, and whether the client can move them.

• Support chain: Resellers give first- and second-line support and Nokia Innovations provides remote third-tier support, under the DAC reseller addendum published by distributor Westcon.

Table 2 shows where an integrator finds each factor and when it raises a client’s exposure.

FactorWhere the SI finds itHigher exposure when
Subscription end dateOrder confirmationThe term ends close to the expected closing window
Cloud managementDAC manager, site network designThe site relies on a single internet path
CBRS path to the SASDAC manager, CBRS registration recordsThe network runs in CBRS in the US
MXIE workloadsMXIE application inventoryAI or third-party applications run on MXIE
Industrial devicesAsset register, order historyDaily operations depend on Nokia handhelds or other devices
Subscriber data and SIM credentialsCore configuration, SIM supplier recordsThe client doesn’t hold its own SIM keys
Support chainPartner agreement, ticket historyCases often escalate to Nokia’s third tier

Clients whose subscriptions end near the expected closing window and who run AI or third-party workloads on MXIE go to the top of the list, because they face a renewal decision before the open questions have answers. Sites on standard DAC connectivity, with terms running well past 2027, can wait for the new owner’s first published terms.

PRO TIP: A Dated Export Before ClosingUnder Nokia’s DAC terms, backups are the customer’s job, and Nokia offers no access to customer content after the term ends. An export of the network configuration, subscriber records and MXIE application inventory, dated before closing, gives each client a baseline that holds however the transition is handled. Integrators that already run regular exports for support work have most of it in hand.
Closing is still months away, and the terms that matter most to integrators haven’t been published yet. Subscribe to PrivateLTEand5G to follow vendor changes that affect deployed private networks as the details emerge.

Get the Open Questions Answered in Writing Before Closing

PrivateLTEand5G advises integrators to raise six points with their Nokia channel contact now and keep the replies with each client record.

Each one covers a gap left open when the deal was announced:

•    Radio supply and software compatibility: Which combinations of Nokia radio software and ECE core releases will be supported after closing, and through which channel radios will be ordered.

•    Contracting entity: Nokia’s DAC Terms of Service define the contracting party as “Nokia Innovations Ltd, or its Affiliate” named in the order confirmation, and Nokia may transfer the terms to any party, while customers need Nokia’s consent to assign. Still open is which entity will invoice, support and renew after closing, and whether partner agreements move with it.

•    DAC manager hosting: Under the terms, the service runs on Nokia’s computing cloud. Integrators need to know whether a transition period applies and what changes for logins, APIs and data location.

•    Patent license: The IP-as-a-Service ends immediately if the underlying subscription is terminated, and its licensor is a Nokia company. Nobody has said yet how the license and indemnity will work for subscriptions the new owner sells.

•    Third-tier support, spares and returns: Who handles escalations, replacement hardware and return authorizations on the first day after closing.

• Roadmap and end-of-life notices: The path from LTE to 5G standalone on existing DAC sites, the MXIE hardware refresh, and who will issue end-of-life notices.

The channel contact may not have every answer before closing, and some answers may depend on agreements Nokia and Aurelius haven’t published. A dated “not yet decided” has value too, because it tells the integrator which renewals need a review point.

Written answers also give the integrator something specific to show a client, beyond the continuity statements both companies have made.

PRO TIP: Transition Services Have an End DateCorporate carve-outs commonly rely on a transition services agreement, with the seller running shared systems for a fixed period after closing. For DAC, the likeliest candidates are the cloud management platform, ordering and the support portal. If Nokia or Aurelius discloses such a period, its end date becomes the deadline for settling who manages and supports each client’s network.

What to Tell the Client, and What to Change at Renewal

PrivateLTEand5G suggests a written update that covers what is known, what isn’t known yet and what the integrator is doing in the meantime, in that order.

The Client Conversation

DAC, MXIE and MPW move to ECE under Aurelius, the radios stay with Nokia, the ECE team is due to transfer, and closing is expected in the first half of 2027. Nothing published ties the network’s operation to the closing date itself; what to watch is the client’s subscription end date and, for US CBRS sites, the connection to the SAS.

The main unknowns are radio supply terms, the contracting entity after closing and the patent license. Listing each one with the date the integrator raised it gives the client a reason to wait for answers before opening an unbudgeted replacement project.

What Goes Into a Pre-Closing Renewal

PrivateLTEand5G recommends five clauses in the integrator’s own client agreement:

•    A review point once the new owner publishes its commercial terms, with the option to adjust scope then.

•    Co-termed subscriptions, so DAC, MXIE, devices and applications renew on one date.

•    Export rights for the client’s configuration and application data, with the integrator responsible for producing them on request.

•    Notice of change to the supplier, contracting entity or support path.

• Exit assistance, priced in advance, in case the client later decides to change platforms.

The Same Method for Any Vendor Change

Private network platforms have been retired before. AWS Private 5G reached its end of support on May 20, 2025, according to AWS’s list of services it has fully shut down, and Microsoft scheduled Azure Private 5G Core to retire on September 30, 2025. ECE is a different case: an ownership change with a public continuity commitment and staff expected to move with the business. The method still carries over, because the dependencies an integrator maps for ECE are the ones a platform retirement would hit first. Teams that already track these as part of private 5G network operations can reuse that work.

A second ownership change is possible as well. Dean Bubley of Disruptive Analysis notes that a private equity owner will likely want an exit at some point (Telco Magazine, October 13, 2026). An inventory kept current after closing means the next change starts from a list the integrator already has.

PRO TIP: One Renewal Date Per ClientClients that added MXIE, devices or applications after the original DAC order can end up with several renewal dates. Aligning them the next time one comes up means any future change of owner or terms triggers a single review per client, and the export and question list follow the same calendar.

Where Does This Leave You?

If you’re an integrator, managed service provider (MSP) or reseller with Nokia clients, aim to reach closing with an exposure ranking for each Nokia client, written answers on file for all six questions, and no renewal signed without a review point. If you’re a vendor, ECE included as it becomes a standalone company, PrivateLTEand5G expects integrators to give more weight to how each supplier carries an installed base through change. A documented transition plan for existing customers is the clearest evidence of that. The Executive Voice Program gives your executives a way to explain how your company handles transitions to the SI audience directly, and Partner With Us covers sponsorship options for reaching the same readers.

If you run a DAC or MXIE network inside the enterprise, the priority is knowing your own dependencies before the renewal conversation starts. Ask your integrator for your version of Table 2 and a dated export of your network settings and subscriber records, and find out whether you, the integrator or Nokia holds your SIM keys. Before any vendor conversation, the wireless self-audit, a 10-question, scored self-assessment that takes about five minutes, gives your team a baseline to bring to it. Expect answers to arrive in stages through 2027. The realistic goal before closing is a complete list of what your network depends on and who to ask about each item.

Frequently Asked Questions

Will our DAC network stop working when the sale closes?

Closing changes who owns the platform. The risk to day-to-day operation is a subscription due to lapse during the handover, when ordering and billing may be moving between companies. An early renewal with a review point covers that gap.

Should a planned DAC or MXIE expansion wait until after closing?

Radios or devices added under an existing term change little. A new multi-year MXIE subscription is a bigger commitment, because it locks in terms before the hosting, patent and support questions have answers. PrivateLTEand5G would keep it short.

Does the sale affect our spectrum license?

Spectrum rights stay with whoever holds them, the enterprise or an operator. Nokia’s CBRS terms, for example, leave a Priority Access License holder responsible for its own records and renewals. The dependency the sale touches is the SAS connection that runs through DAC.

Are Nokia’s mission-critical customers affected?

Nokia keeps serving rail, utility and other wide-area customers with its own RAN, but MPW, the platform it pairs with that RAN for larger deployments, moves to Aurelius. Those MPW sites need the same supply and support answers as campus networks.

Related posts
Expert PerspectivesPrivate WirelessUncategorized

Your CBRS Private Network Was Built for Rules That Are Still Open

10 Mins read
Quick Answer: Three proposals hang over the Citizens Broadband Radio Service (CBRS) band at 3.55 to 3.7 GHz: relocation, new higher-power base…
AirportExpert PerspectivesUncategorized

The Private Wireless Business Case Starts on the Shop Floor

7 Mins read
Quick Answer: On October 20, PrivateLTEand5G hosted a session on why Wi-Fi often fails industrial sites and how private 5G addresses those…
Expert PerspectivesManufacturing

Private 5G Network Operations Start When the Integrator Leaves

10 Mins read
Quick Answer: Private 5G network operations are the ongoing work that keeps a factory network running after the integrator’s project team moves…
Looking to amplify your brand presence and boost thought leadership through PrivateLTEand5G’s content and media offerings?