Software licences are easy to forget once the systems are running. Across South Sudan, Tanzania and Rwanda, many organisations have grown quickly: new branches, new staff, new servers and new projects funded by donors or head office. Licences bought years ago rarely keep pace with that growth. When Microsoft or Oracle later asks for a licence review, the gap between what you use and what you own can turn into an unplanned bill, and sometimes a difficult conversation with your board or donors.
The good news is that most compliance problems are avoidable. This guide explains where banks, microfinance institutions, government offices, NGOs and SMEs usually go wrong with Microsoft and Oracle licensing, and the practical steps to stay audit-ready.
Why Licence Compliance Matters
Your licence agreements with major software vendors normally give them the right to verify that you are using their products within the terms you signed. A review may start as a friendly request to complete a questionnaire or run a data collection tool, or as a formal audit notice. If the review finds that you are using more than you have paid for, you are usually asked to buy the missing licences, often at list price and sometimes with back-dated support fees. Because of this, the cost of a shortfall found in an audit is almost always higher than the cost of getting it right in advance.
Compliance is also about trust. Banks are expected by regulators and partners to run properly licensed, supported systems. NGOs must show donors that funds are used correctly. Government offices are accountable for public money. Unlicensed or unsupported software can also mean missing security updates, which creates a cyber risk on top of the financial one.
Common Microsoft Licensing Mistakes
Using consumer or Home editions for business
Laptops bought from retail shops often come with Windows Home or a consumer Office edition. These are not intended for organisational use in the same way as business editions. Standardise on Windows 11 Pro and Microsoft 365 business or enterprise plans.
Missing Client Access Licences (CALs) for Windows Server
Buying a Windows Server licence is only part of the cost. Users or devices that access the server generally need CALs, and Remote Desktop Services needs its own separate CALs. Organisations that add staff or branches without adding CALs are a very common finding.
Under-licensing SQL Server and virtual machines
SQL Server and Windows Server are typically licensed by processor cores, with rules that change depending on whether you run them on physical servers, virtual machines or in the cloud. When servers are upgraded or virtualised, the licence count often needs to change too, but nobody updates it.
Shared accounts and leftover users in Microsoft 365
Microsoft 365 is licensed per user. Sharing one mailbox login among several staff breaks the terms and weakens security. On the other side, licences assigned to people who left months ago waste money. Review your user list regularly.
Common Oracle Licensing Mistakes
Virtualisation without understanding Oracle’s rules
Oracle Database is widely used by banks and large institutions in the region. Oracle has specific policies on which types of virtualisation it accepts for limiting the number of licences needed. Depending on how your virtual environment is set up, you may need licences for far more of the underlying hardware than the virtual machine actually uses. Always check this before moving Oracle workloads to a new virtual platform.
Using database options and packs you have not bought
Oracle Database Enterprise Edition includes features, such as certain options and management packs, that can be switched on easily but must be licensed separately. A database administrator may enable one for troubleshooting and forget about it. These features are recorded in the database and can appear in a review.
Overlooking Oracle Java
Oracle has changed how it licenses Java SE in recent years, and commercial use of Oracle’s Java distribution may now require a paid subscription. Many organisations do not know which Java versions are installed on their servers and PCs. Find out what you have and decide whether you need a subscription or can move to an alternative.
Letting support lapse
Stopping annual support may look like an easy saving, but it means no security patches, and restarting support later can be expensive. Make support renewal decisions deliberately, with advice, rather than by accident.
Steps to Stay Audit-Ready
Step 1: Build a complete software inventory
List every server, virtual machine, PC and cloud subscription, and the Microsoft and Oracle software installed on each. Include branches, field offices and project sites, not just head office.
Step 2: Collect your proof of entitlement
Gather contracts, invoices, licence certificates, ordering documents and portal records in one place. If a licence cannot be proven, it is usually treated as not owned. Keep these records safe when staff or suppliers change.
Step 3: Compare usage against entitlement
Match what is installed and used against what you own. This shows any shortfall, and very often also shows licences you are paying for but not using.
Step 4: Fix gaps before the vendor finds them
Buy what is missing, remove software that is not needed, switch off unlicensed features and reassign unused licences. Correcting issues yourself is normally much cheaper than settling them during an audit.
Step 5: Control changes
Most compliance problems start with a change: a new server, a virtualisation project, a new branch or a cloud migration. Add a licensing check to your change process so that someone confirms the licence impact before the change goes live.
Step 6: Respond to audit letters carefully
If you receive a review or audit request, do not ignore it and do not rush to send data. Read the terms of your agreement, agree the scope and timeline in writing, check any data before sharing it, and get experienced licensing advice early.
Quick Licence Compliance Checklist
- Complete inventory of servers, virtual machines, PCs and cloud subscriptions
- All licence contracts, invoices and portal records stored in one place
- Business editions only (no Home or consumer versions) on work devices
- Windows Server and Remote Desktop CALs match your users or devices
- SQL Server and Oracle Database core counts checked after any hardware or virtualisation change
- Oracle database options and packs reviewed and unused ones switched off
- Java installations identified and licensing position confirmed
- Microsoft 365 users reviewed, with leavers removed and no shared logins
- Licensing check included in your IT change process
- A clear plan for how to respond to an audit letter
How Junubia Host Can Help
Junubia Host works with both Microsoft and Oracle, and supports organisations in South Sudan, Tanzania and Rwanda to keep their software properly licensed. We can help you to:
- Build an inventory of your Microsoft and Oracle software and compare it with what you own.
- Choose the right Microsoft 365, Windows and server licences through our Microsoft partnership.
- Review Oracle licensing before upgrades, virtualisation or moves to new hardware, including platforms such as Sangfor HCI.
- Plan renewals and support so that your systems stay patched and secure, alongside network protection from our Fortinet partnership.
You can see our full range of IT services, or read more about our IT solutions in Tanzania.
Check Your Licence Position Before the Vendor Does
Not sure whether your Microsoft and Oracle licences match what you are running? Start with a free IT assessment, and we will review your current environment and highlight any licensing risks and savings. You can also reach us on WhatsApp: +255 768 404 666 (Tanzania and Rwanda) or +211 924 786 666 (South Sudan).
Written by Dut Majak, CEO and Founder of Junubia Host Co Ltd. Dut leads Junubia’s work with banks, government institutions, NGOs and businesses across South Sudan, Tanzania and Rwanda.
