Business Email
The overview: mailboxes on your domain, aliases, and why the business should own the account.
Read the email guideYou have decided you probably want more than a mailbox. Here is what Microsoft 365 for small business commits you to: what you are licensing, what setup involves, and where businesses over-buy.
Microsoft 365 is a bundle, and mail is one part of it. Everything else in the subscription is what you are paying the difference for. The business email overview covers the basics this page assumes you already have.
Two things follow. You license people, not computers. And nothing is owned at the end of it: anyone who remembers buying a copy of Office once and using it for years is used to a different arrangement. Stop paying and the applications stop working the way they did.
Which applications are in which plan, how much storage comes with an account and what it costs all change. Every figure is left off this page on purpose.
The unit is a person, not a machine, so one member of staff is one licence however many devices they read mail on. How many devices a single licence covers is a plan detail worth confirming before you buy. What catches people out is the other direction: hire three people and you need three more licences, and each one is a whole bundle, not just a mailbox.
So the cost shape differs from a plain mailbox plan. Both grow with the business, but with mailbox hosting you add mailboxes, and here you add whole subscriptions, whether the new person opens a spreadsheet or not.
The Office applications, tied to the same account as the mail. Which applications, and whether they run on the desktop or only in a browser, depends on the plan. Add shared calendars and storage a team can reach, and that is the case for buying it: the things around the mail, not the mail.
What gets skipped is that a subscription with people in it is an account somebody has to run. Not much work, but it has to belong to a named person, and these decisions are easier before the accounts exist than after.
Ask about the team, not about yourself. Does more than one person need the same calendar, or the same document? If yes, the bundle earns its place. If one person needs mail and everyone else just needs an address customers can write to, it does not.
| What you are weighing | Microsoft 365 | Plain mailbox hosting |
|---|---|---|
| What you are buying | A subscription bundle that includes mail | A mailbox on your domain |
| The question it answers | Does the team need to work in the same tools? | Does everyone need a professional address? |
| How the bill grows | Per person, so it tracks headcount | Per mailbox |
| Desktop applications | Included on some plans, so check which | Not included, you keep whatever you use now |
| Shared calendars | A core part of the product, confirm which plan | Varies by provider, check before relying on it |
| Two people in one document | Part of what the applications do, plan dependent | Handled by whatever you already use |
| If you stop paying | Mail stops and the applications stop with it | Mail stops, the address is still yours |
Notice what is not in that table: storage figures, mailbox counts, feature lists. They decide almost nothing at this size, and every comparison page leads with them.
Most of it is not particular to this product. The migration and the DNS work are the same whichever provider you move to, and are covered in the email migration guide and in how DNS management works. What follows is the part that only applies here.
You publish a record on the domain and setup checks for it before the domain may carry mail. The registration and the website both stay where they are; only records are added. It stalls in two places: nobody at the business can sign in to wherever the DNS records are edited, which is the real first job, or the host field goes in the way the registrar's form suggests rather than the way the instructions read, so the record lands on the wrong name and the check fails on something you can plainly see is there.
Signing up creates an organisation account and everything you buy afterwards sits inside it. The name is picked in the first few minutes, usually by whoever is nearest a keyboard, and it appears to be awkward enough to change later that it deserves five minutes now. Use the business name, not a person's name and not the one project that prompted the purchase.
Decide on paper who signs in and who only needs an address. A person's mailbox appears once a licence is assigned, so the licences you hand out are both what creates somewhere to copy mail into and what you start being billed for. Doing it the other way round is how businesses pay for accounts nobody opens.
New empty mailboxes change nothing on their own: the old ones carry on receiving, because the mail records still point at them. The trap is that setup will generally offer to update those records for you, and taking that offer before the copy has run sends new mail into empty mailboxes. Decline it, copy the mail, then change the records deliberately.
All of them are about paying a subscription for something a cheaper arrangement already covers.
One case where the answer is to leave things alone: if you already run Microsoft 365 and it works, there is no reason to move it to put the bill on one invoice. Consolidating suppliers is a convenience, not an improvement.
We size the licences with you first, because that is where the money is, then set the accounts up, run the migration and make the DNS change carefully. AldoMedia, LLC. has been building and maintaining websites for Western New York businesses since 1999, and email has always come with that work. We are an independent authorised reseller, not the platform operator.
Tell us how many people actually need an account, call 716-771-2536, or read the support page first. The website is a separate purchase again: see web hosting and what website security covers.
No. Email is one part of a subscription that also carries the Office applications, shared calendars and file storage. Most small businesses buy it for the mailbox and then use a few of the other parts. If none of the rest sounds useful, plain mailbox hosting covers the mail.
Only for the people who need their own account. Somebody who is simply one of the people reading a shared address does not need a licence of their own, because an alias delivers into a mailbox that already exists. Licensing is per person, so over-buying here is what makes the bill look wrong.
Yes, and you do not have to move the registration or the website. You prove you control the domain by publishing a record Microsoft asks for, then point the mail records at your new mailboxes. Where the domain is registered and where the website is hosted can both stay exactly as they are.
Yes, in the way that matters. A domain's mail records point at one system, so the mix is not two providers on one name. It is Microsoft 365 holding the domain, with licensed accounts for the people who sign in and plain addresses delivering into an existing mailbox for everybody else. You pay per account, not per address.
A one-person business that only needs a professional address, a team that does not share calendars or edit the same documents, and anyone already paying for the same applications somewhere else. Paying twice for Office is common.
The overview: mailboxes on your domain, aliases, and why the business should own the account.
Read the email guideMoving mail from an existing provider without customers noticing.
How a migration runsThe records that decide where your mail goes, and why the website records are a different set.
DNS explainedBrowse all guides, or check who your domain is registered to, since whoever controls it controls the mail.
Tell us who signs in daily and who just needs to be reachable. That one answer usually changes the order.