Nilepet Plans Microsoft 365 Migration and IT Overhaul Across South Sudan

What Nilepet has announced​

Eye Radio says Managing Director Eng. Emmanuel Athiei Ayual Makoi is leading the program, which attempts to tackle long-standing logistical hurdles and communication gaps between Nilepet's Juba headquarters and its regional field sites. According to Athiei, this digital transformation will provide the national oil company with a stronger technological foundation as it continues to develop its operations.

The overhaul is structured around three core components: enterprise networking, physical security systems, and data center modernization. Here is what each one covers, based on the reporting:

Plans include deploying a modern IP-based CCTV surveillance system at the Juba headquarters, paired with a centralized electronic access control system. In the final phase, establishing a fully operational ICT data center equipped with resilient power architecture, alongside a complete migration to a Microsoft 365 email and collaboration platform.

Eye Radio also reports that the contract terms require complete project documentation, structured staff training, testing reports and a formal handover to Nilepet's internal ICT team. It has not published the contract. No contract value, supplier, timetable or migration date has been reported, and nothing suggests Microsoft is directly involved as a vendor.

Section summary: The plan has three pillars: networking and voice, physical security, and a data center plus Microsoft 365. What's missing is almost every number an IT professional would ask for first.

Where the project stands​

The October report reads like a description of the program's scope, not a status report on finished work. Earlier coverage gives one checkpoint. A July 2026 item, reproduced by Derawet Media and attributed to Alwadi Newspaper, said Nilepet's Management Committee had confirmed that the first phase of high-speed internet connectivity across its facilities was complete. CCTV installation was named as the next phase, "followed by the implementation of additional digital technologies and solutions."

That account came through a secondary outlet, and it doesn't mention the data center, the IP PBX, access control or Microsoft 365. So the two reports shouldn't be stitched together into a confirmed schedule. The fair reading is that connectivity work appears to have started earlier in 2026, and the larger set of components described in October is still being rolled out.

One small inconsistency is worth noting. Eye Radio calls Athiei the managing director, while the Alwadi item reproduced by Derawet Media refers to him as Minister of Petroleum guiding the program. Readers should keep both descriptions in mind until official sources clear it up.

Why "migrate to Microsoft 365" is a project, not a checkbox​

Anyone who has run a tenant migration knows the phrase "complete migration to Microsoft 365" hides a lot of decisions. Microsoft's own FastTrack data migration documentation treats Exchange Online, SharePoint, OneDrive, and Teams and Microsoft 365 Groups as separate migration targets, each with its own prerequisites. For eligible customers with 150 or more licenses, FastTrack offers guidance and migration services. Nothing in the reporting says whether Nilepet qualifies or plans to use it.

Microsoft's Exchange Online guidance lists customer-side work that applies to any organization doing this, whatever tooling or partner it uses:

1. Finish tenant setup first. Exchange Online has to be configured, and the migration prerequisites met, before mailboxes move.
2. Plan mail routing coexistence. If the old and new systems will run side by side, SMTP routing between them has to be set up.
3. Check mailbox sizes against quotas. Microsoft says some source platforms may need data held to 85 percent of the target mailbox quota.
4. Decide what to do with client-side data. Local address books, PST files, Outlook rules and local Outlook settings don't move automatically. Someone has to choose whether to bring them across.
5. Budget for user support. Microsoft notes that customers are responsible for helping end users fix client-side migration problems.

File migrations have their own catches. Microsoft notes that only NTFS permissions visible in Windows File Explorer get migrated. Permissions managed directly on file-share devices don't. When files go into a Teams channel or Microsoft 365 Group, that group decides the final permissions. This matters for any organization moving off on-premises file shares, because "it's in SharePoint now" is not the same as "the right people can see it."

Section summary: The Microsoft 365 pillar covers mail, files and collaboration, and each workload has its own prerequisites. Mail routing, quotas, PST data and file permissions are where these projects usually get bogged down.

Physical security isn't cybersecurity​

The CCTV and access-control systems are physical security, and the reporting doesn't describe any named cyber defense. Eye Radio does acknowledge the gap. It says the real test is whether Nilepet can maintain the systems on its own and safeguard its networks against cyber vulnerabilities, but it reports no security assessment, incident or specific protective controls.

That leaves some obvious implementation questions, which are questions and not confirmed features. One is identity protection for the new Microsoft 365 accounts. Microsoft's support documentation explains that administrators must turn on multifactor authentication before users can register for it. Admins also decide which methods are allowed, such as Microsoft Authenticator, passkeys, Windows Hello for Business, SMS or hardware tokens, and when prompts appear. Users who lose a registered phone need IT to get back in, so account recovery has to be planned from day one.

IP cameras, IP telephony and networked door controllers also add devices to the corporate network. Whether they sit on segmented networks with managed credentials and regular firmware updates will matter as much as whether they work on day one. That observation comes from general industry practice, not from the Nilepet reporting.

Power, terrain and the handover​

Eye Radio is open about the risks. While technical connectivity is expected to ease administrative friction, institutional analysts note that the success of such networks in South Sudan will heavily rely on addressing persistent regional challenges, including stable power supply and infrastructural reliability outside the capital. A cloud collaboration platform only helps if the field site has power and a working link. The "resilient power architecture" for the data center deals with one building. It doesn't fix the branch sites.

The contract's handover requirements are the most encouraging detail. Documentation, training, test reports and a formal handover to in-house staff are what separate a system a ministry owns from one it rents from its integrator forever. The same report points out that maintenance bottlenecks often hit state-led technology projects in the region. Without a published contract or named supplier, though, readers can't yet judge how strong those requirements are in practice.

The bottom line​

According to Eye Radio, Nilepet's plan combines enterprise networking, IP telephony, premises security, a local data center and a full Microsoft 365 migration under one program. The design looks sensible. The open questions are about execution: unreliable power outside Juba, a migration with several workloads, new networked devices to secure, and an internal ICT team that has to run all of it once the contractor leaves.

Does a national oil company in a country with patchy infrastructure need cloud email and IP cameras? Probably yes, but only if the basics underneath them work. That means power at the field sites, real handover documents, MFA on the new accounts and a plan for the old PST files on someone's desktop. Until there's a timetable, a supplier and some evidence of completed milestones, this is still a plan and not a finished project.