What implementation should include
- Eligibility and licensing review using Microsoft’s current program information
- Tenant, domain and administrator setup
- User, group and shared-mailbox planning
- Email and file migration
- MFA, least privilege and access policies
- Device and application management
- Backup, retention and recovery decisions
- Staff training and ongoing support
Questions to ask an IT provider
- Will you document licensing assumptions and recurring costs?
- How will you protect administrator and user accounts?
- What data will be migrated, and how will it be validated?
- Which security and backup services are included?
- How will new staff, volunteers and departures be handled?
- Who provides ongoing Microsoft 365 support?
What the grant does not decide
Eligibility, which licenses are donated or discounted, and whether a tenant qualifies are Microsoft's current program rules. A provider can prepare the tenant and the answers Microsoft asks for. The provider cannot promise approval, a particular product name, or that a donated license stays free. Costs the grant does not cover still need a budget line. Backup, advanced email security, and after-hours support are the usual ones. Confirm the current program page before anyone tells the board the software is free.
Set up identity before mail moves
Create the tenant, confirm the domain, and name who will hold global administrator rights. An everyday mailbox should not also be a global administrator. Turn on multi-factor authentication before the migration, not after the first scare. Shared mailboxes and volunteer accounts need a named owner. A shared password is how a former volunteer still opens donor mail six months later. Write down who can approve a new admin role. That list should be short.
Move mail and files in an order you can check
List what must move: staff mailboxes, shared mailboxes, distribution lists, and the files people open every week. Move a pilot group first. Confirm they can send, receive, and find last year's folders. Then move the rest. Leave the old system read-only until someone who does the work says the new mailbox is complete. A weekend cutover with no check is how a donor history file goes missing. The provider should give you a list of what moved and what was left behind.
Security and backup are separate from the license
If Microsoft approves the grant, that is a licensing decision. It does not configure anti-phishing, least privilege, device enrollment, or a backup an attacker cannot delete from the tenant. Those controls belong in the operating scope. Standard plans at Outsource IT Canada include the help desk on weekdays from 9 AM to 5 PM ET. 24/7 support is a paid add-on. The priority one response target is 15 minutes to start work on a business-wide outage or an active security incident. Starting work is not the same as finishing a restore. PIPEDA accountability for donor and supporter information stays with the organization.
Plan for ongoing ownership
Microsoft 365 changes after launch as users, permissions, applications and program needs evolve. Assign responsibility for administration, security reviews, licensing and recovery instead of treating migration as a one-time project. New staff, seasonal volunteers, and departures change the directory every month. Someone has to add accounts, remove them, review admin roles, and test a restore. That is ongoing managed IT, not a leftover task for the executive director.
Outsource IT Canada is a Group 4 Networks service, 100% Canadian-owned, and the team has been Toronto-based since 2008. A scoping call starts with the user count, the systems that hold donor information, and whether anyone already administers Microsoft 365. Call (416) 623-9677 or use the contact form. You do not need a network diagram.
Related: IT services for non-profits, Microsoft 365 services, and Microsoft 365 security checklist.
Need an IT plan for your organization?
Start with your users, systems, information, support needs and security responsibilities.