Eligibility is Microsoft's decision
A nonprofit program is not automatic because you have an EIN, a charity number, or a .org website. We collect the legal name, the country, and the evidence Microsoft asks for at the time we apply, and we file it against the tenant. If the organization is approved, we look up which Microsoft 365 plans and which add-ons are donated, which are discounted, and which stay at commercial rates. You see that list before we assign a seat.
If Microsoft does not approve the organization, we can still license commercial plans. We will not describe a commercial seat as a grant. We also do not promise a discount percentage or a donated seat count on this page. The offer list changes, and the approval is not ours to give. Copilot, Teams Phone, Dynamics 365, and Azure each have their own place on that list, and several of them are often absent. We check product by product.
Staff, volunteers, and shared mailboxes
Nonprofit staff are often a mix of employees, a bookkeeper who works a few hours, and volunteers who should not have a full mailbox. We license the people who need mail and files. Volunteers usually get a guest invitation to one Teams team or one SharePoint library, not a paid seat, unless they send mail as the organization. Shared mailboxes for programs, such as intake or the board packet, stay shared mailboxes so they do not each consume a paid seat. We set them up that way on purpose.
Board members who only read a packet do not each need Business Premium. We will say who needs a license and who does not before we order. A departing executive director should not be the only global admin. We add a second admin you name, and we write it down, as part of setup rather than as an emergency later.
Migration and the desk after approval
Setup follows the same sequence as a small business, with that extra care about administrators. Migration of mail from a previous host is scoped on its own, with a cutover window you approve. Domain DNS does not change until that approval. Files move into the SharePoint libraries and Teams teams you named, not into a template site nobody opens.
Afterward, support is email to support@true.org. Adding a staff mailbox, closing one when someone leaves, and checking the nonprofit offer at renewal are ordinary requests. A typical reply is one business day, for organizations in the United States and Canada. Renewal is when a donated or discounted seat is most often replaced with a commercial one by accident. We look before that happens. Training, if you want it, is one session on the shared mailbox and the team your program actually uses.
Questions we answer before a quote
Does an EIN guarantee free Microsoft 365?
No. Microsoft approves or declines the organization. We prepare the request. If it is declined, we can still sell commercial licenses, and we will say that plainly.
Should every volunteer get a mailbox?
Usually no. A guest link to the team or the library is enough for most volunteers. A mailbox is for people who send mail as the organization. We will mark the difference in the seat list.
Can you move us off our current mail host?
Yes, as a scoped migration with a cutover window. The nonprofit license order does not move the old mail by itself, and we do not change domain DNS until you approve the cutover.
Who do we write when a staff member leaves?
support@true.org. Name the person and the tenant domain. We remove the sign-in and decide with you whether the mailbox becomes a shared mailbox or is closed. A typical reply is one business day.