If you've ever tried to figure out Microsoft 365 licensing for your NonProfit, you probably started with what sounded like a simple question: “Which Microsoft 365 license should we buy?”
Then you went online and discovered Business Basic, Business Standard, Business Premium, Microsoft 365 E3, Microsoft 365 E5, add-ons, security features, desktop applications, cloud services, and NonProfit eligibility requirements. Before long, what looked like a straightforward purchasing decision became a confusing mix of features, prices, and product names.
At that point, someone usually asks the question that seems easiest:
“Can't we just give everyone the same thing?”
You certainly can, and in some organizations that may even make sense. Standardization can make an environment easier to manage. But there is a difference between intentionally standardizing your Microsoft 365 licenses and simply assigning everyone the same plan because nobody has had time to figure out what they need.
For a 20–150 employee NonProfit, that distinction can become expensive.
Licensing costs tend to grow quietly. A new employee gets hired, so another license is added. Someone needs a feature, so their license gets upgraded. An employee leaves, but nobody remembers to remove or reassign the license. Another department purchases a separate application that overlaps with something you're already paying Microsoft for.
A few years later, finance looks at the technology budget and asks:
“What exactly are we paying for?”
That's usually a sign that licensing decisions have been happening one person and one problem at a time instead of as part of an overall technology plan.
The better approach is to work backwards. Rather than starting with Microsoft's licensing chart, start with your employees and the work they need to do.
Not Every Employee at Your NonProfit Works the Same Way
Imagine a 75-person health and social-services NonProfit.
Your Executive Director may spend much of the day in email, meetings, documents, and Microsoft Teams, while finance employees work with sensitive organizational information and depend heavily on desktop applications such as Outlook and Excel. Program managers may collaborate on documents from multiple locations, while field employees might spend most of their time in a browser-based case-management system and only occasionally use Microsoft Office.
You may also have part-time employees who need much less technology, and perhaps volunteers who need limited access to a few resources without needing the same tools as a full-time employee.
Those people do not necessarily require identical Microsoft 365 licenses.
That doesn't mean you should create a complicated licensing environment with a different plan for every person. Simplicity has value. But the goal should be intentional standardization, where you define a few sensible license profiles based on how people work.
For a NonProfit watching every dollar, that's very different from paying for features simply because everyone has always received the same license.
Start With the Employee, Not the License Name
Instead of asking a manager, “Does Jennifer need Business Premium?”, ask questions the manager can answer.
What does Jennifer do every day? Does she need the desktop versions of Word, Excel, PowerPoint, and Outlook, or will browser-based applications meet her needs? Will she have an organization-owned laptop? Does she work remotely or in the field? What information does she need access to? Does she work with sensitive client, financial, employee, or donor information? Does she need Microsoft Teams, shared files, mobile-device access, or additional protections if her laptop is lost or stolen?
Those answers are far more useful than expecting someone outside IT to understand Microsoft's licensing catalog.
A manager should be able to explain the employee's role and responsibilities. Someone who understands the technology should translate those requirements into the appropriate Microsoft 365 license and configuration.
The employee's work should determine the technology, not the other way around.
“They Just Need Email” Is Usually More Complicated Than It Sounds
This comes up all the time.
Someone says, “This employee just needs email.”
That may be true at first glance, but follow that employee through a normal workday and the requirement often expands quickly.
They open email and receive a link to a shared document, so now they need access to SharePoint or OneDrive. Their manager asks them to join a Teams meeting, so now they need Teams. They're working from home tomorrow, which raises questions about how they're accessing organizational information and from what device. They need to edit a spreadsheet, so now you need to determine whether the browser version of Excel is sufficient or whether the desktop application is necessary.
If the employee works with sensitive information, device management and security may also become part of the conversation.
Suddenly, “just email” wasn't really the requirement.
This is why licensing decisions should be based on how employees work, not just the first application someone mentions.
The Cheapest License Isn't Always the Least Expensive Choice
NonProfits are understandably careful about technology costs, and they should be.
But the lowest monthly license price does not always produce the lowest overall cost.
Suppose you choose a less expensive Microsoft 365 license that doesn't include a capability your organization needs. You may then purchase another product from another vendor to fill the gap. Now you have another subscription, another account, another invoice, another system to configure, another vendor to manage, another place where organizational information may live, and another application employees have to learn.
That may still be the right decision if the third-party product does something particularly well, but you need to look at the total technology environment, not only the price of one Microsoft license.
Your NonProfit may already be paying for Microsoft 365 capabilities that could replace other software, or you may discover that a third-party product genuinely adds enough value to justify keeping it.
The goal isn't to make Microsoft do everything.
The goal is to know what you already own before buying something else.
The Opposite Problem Happens Too
Some organizations are paying for more Microsoft 365 than employees use.
Maybe an employee was upgraded two years ago because they needed a particular feature for a project, but the project ended and the license never changed. Perhaps several former employees still have paid licenses assigned because licensing wasn't incorporated into the offboarding process. Maybe employees changed roles, or your organization standardized on a more expensive plan years ago even though the way people work has changed.
One unused license isn't going to destroy your technology budget, but waste rarely arrives as one enormous invoice labeled “MONEY YOU ARE WASTING.”
It accumulates quietly.
A few unnecessary Microsoft licenses. Several software subscriptions. A cloud application a department no longer uses. A phone line nobody remembers. A software tool someone put on a credit card years ago and never canceled.
Individually, those costs are easy to ignore. Collectively, they can become significant, especially for a NonProfit operating under increasing funding pressure.
NonProfit Microsoft Pricing Makes This Even More Important
Eligible NonProfits may have access to Microsoft grants, discounts, or other offerings designed specifically for the NonProfit sector, which can make Microsoft 365 significantly more affordable.
That's good news, but discounted technology can create an interesting psychological trap.
When something is inexpensive, it's easier not to pay attention to whether you're using it effectively.
The goal shouldn't simply be, “How cheaply can we get Microsoft 365?”
A better question is:
“How do we get the most value from the Microsoft environment we're already paying for?”
A heavily discounted license that nobody uses properly isn't necessarily a bargain. On the other hand, a slightly more expensive license that eliminates another subscription, improves how employees work, or gives the organization capabilities it genuinely needs may be the better investment.
Your technology budget should reflect value, not just price.
Your Microsoft 365 Environment May Already Do More Than You Realize
Before adding another software subscription, it's worth looking at what your existing Microsoft environment can already do.
Suppose your organization needs a better way to share files and someone suggests Dropbox. Before buying it, ask what you're currently doing with SharePoint and OneDrive.
A department wants better internal collaboration and starts researching another platform. Before adding another subscription, look at what Microsoft Teams already provides.
Employees need a way to create online forms or collect information. Again, before purchasing something new, ask whether a capability you already own can solve the problem.
That doesn't mean Microsoft will always be the right answer, but it does mean your first question should be:
“Do we already own something that can solve this?”
At I-M Technology, that's one of the reasons we approach Microsoft 365 and Cloud Services for NonProfits as part of the organization's broader technology environment rather than treating Microsoft 365 as simply an email subscription. We help NonProfits manage Microsoft 365, cloud environments, migrations, and collaboration tools around the way their employees need to work.
Watch Out for the Software Subscription Pile
One useful exercise is to ask finance for a list of every recurring technology and software expense your NonProfit paid during the last 12 months.
Then sit down and ask a few simple questions about each one.
Who uses it? What does it do? How many licenses are we paying for? When did we last review it? Does Microsoft 365 already provide something similar? Is the application still required? Does the department that originally purchased it still use it? What happens to those accounts when employees leave?
You may be surprised by what you find.
Growing NonProfits tend to accumulate technology one problem at a time. Someone needs electronic signatures, so a product is purchased. Someone else needs project management, file sharing, scheduling, surveys, video meetings, or AI, so another subscription gets added.
Each purchase may have made perfect sense at the time.
The problem is that nobody ever steps back and looks at the collection as a whole.
Eventually, you aren't really managing software anymore.
You're managing archaeology.
Employee Turnover Can Create Licensing Waste
Licensing is another reason employee onboarding and offboarding need to be connected to technology management.
When someone joins the organization, people generally remember that they need email, applications, and access.
When the employee leaves, the process may be less consistent.
Their Microsoft 365 account might get shut down, but what about every other paid application? What about the phone system, the AI subscription, the donor-management platform, or the other cloud tools they were using?
If employee offboarding doesn't include a licensing review, subscriptions can remain active long after the employee is gone.
That wastes money, but it also makes the environment harder to understand because nobody is completely sure which accounts are active, which licenses are assigned, or what still needs to be paid for.
A good offboarding process should answer two questions at the same time:
What access needs to be removed, and what are we paying for that can now be reassigned or canceled?
Licensing Decisions Matter More as Your NonProfit Grows
At 15 employees, a few inefficient licenses may not get much attention.
At 100 employees, small differences multiply quickly.
A $10-per-user monthly difference across 100 employees is $12,000 per year.
That doesn't mean you should automatically choose the cheaper plan. If the more expensive option gives your NonProfit capabilities it genuinely needs, that $12,000 may be money well spent.
But if nobody uses those capabilities, then it is simply waste.
The goal isn't to minimize the cost per employee.
The goal is to match the investment to what each group of employees needs to do their jobs.
That's how technology becomes stewardship rather than just an expense.
Your Finance Director Shouldn't Have to Become a Microsoft Licensing Expert
This is where the staff-capacity problem shows up again.
Somebody inside the NonProfit usually ends up trying to figure all of this out, and very often it's someone in finance because they see the bill, operations because they manage employee onboarding, or an office manager because everyone asks them about software.
Now someone who already has a full-time job is spending an afternoon comparing Microsoft licensing tables, calling Microsoft, searching online, and trying to determine which information applies to commercial customers and which applies to NonProfits.
Three hours later, they may be less confident than when they started.
That employee shouldn't need to become a Microsoft licensing specialist.
They should be able to say:
“Here's how our employees work, here's what we're trying to accomplish, and here's what we're currently paying.”
Someone who understands the technology should then help translate that into the right licensing and configuration.
Review Licenses When the Organization Changes
An annual licensing review is useful, but it shouldn't be the only time you look at your environment.
There are natural moments when your licensing assumptions deserve another look, such as when you hire several employees, expand a program, open another location, change a major software system, adopt AI tools, end a grant-funded program, move more work into the cloud, or notice that your technology budget suddenly increased.
These events can change how employees work and what technology they need.
A licensing decision made three years ago may have been perfectly reasonable at the time and still be completely wrong today.
Technology should evolve with the organization.
Your licensing should too.
Don't Optimize Microsoft Licensing in Isolation
There is one important caution here.
You don't want to save $4 per employee on a Microsoft license and accidentally create another $15-per-employee problem somewhere else.
Microsoft licensing can affect device management, security, employee access, cloud applications, and the other third-party products your organization needs, so significant licensing changes should be evaluated as part of the broader environment.
Before changing plans, look at the whole picture.
What are employees doing? Which Microsoft capabilities are already being used? Which other subscriptions could be affected? Are you solving a real business problem, or simply reducing one line item on an invoice? What will the organization need over the next few years?
This is the same principle I-M Technology applies to our broader Managed IT Services for NonProfits: technology decisions should support the organization's mission, staff productivity, growth, and budget instead of being made one product or one support ticket at a time.
The Goal Isn't to Become Good at Microsoft Licensing
Your NonProfit doesn't exist to understand Microsoft product names.
Your Executive Director shouldn't spend Friday afternoon researching licensing. Your finance director shouldn't need a spreadsheet with fourteen tabs just to understand why different employees have different subscriptions, and your managers shouldn't need to know which Microsoft plan includes which feature before they can hire someone.
The goal is much simpler:
Give each employee the technology they need to do their job, protect the information they're trusted with, and avoid paying for things the organization doesn't need.
If you're looking at your Microsoft bill and you're not completely sure what you're paying for, why employees have the licenses they have, or whether you're getting the full value from Microsoft 365, that's worth reviewing.
I-M Technology helps NonProfits manage Microsoft 365 as part of our Cloud Services and broader technology strategy, so licensing decisions aren't disconnected from how your employees work.
And you don't need to understand every Microsoft license before you talk with us.
Schedule a Discovery Call with I-M Technology and bring the question you're trying to answer:
“Are we paying for the right technology for the way our people work?”
We'll start there.
