Domains & Hosting · Email Marketing

Email Hosting or Microsoft 365: How to Compare Business Requirements

Compare business email proposals through actual tasks, shared access, administration, migration, user experience, total effort and handover.

Published

Email Hosting or Microsoft 365: How to Compare Business Requirements

Choosing business email begins with the way your team communicates. Some businesses need reliable individual mailboxes and straightforward administration. Others need shared addresses, coordinated calendars, document collaboration and a wider set of managed accounts. The right comparison starts with those requirements rather than the largest advertised storage allowance.

Microsoft 365 offers plans that include hosted email as part of a broader service arrangement, while email-focused hosting packages have their own capabilities and limits. Check the specific proposed plan in each case. Product names alone do not establish that two quotations provide equivalent tools, support or administration.

List the email tasks your business must support

Record who needs an individual mailbox and how they use it. Include office staff, mobile workers, part-time colleagues and anyone requiring access from several devices. Identify the email applications already in use and whether the team depends on particular features.

List business addresses separately from people. An enquiries address, accounts address and support address may each represent a working process. Ask who reads the messages, who replies and what happens when the usual person is away.

Include calendars, contacts and document collaboration where they matter. A provider comparison becomes clearer when you know whether you are buying email alone or a wider working environment. Avoid paying for a broad collection of tools simply because they are available, but do not overlook a feature the team already relies on.

Distinguish mailboxes, aliases and shared working arrangements

Ask each provider to explain how the proposed setup handles the addresses in your inventory. An alias that delivers messages to an existing mailbox is different from a separate mailbox with its own stored correspondence. A shared address also needs a clear arrangement for access and replies.

Use a practical example. Two colleagues may need to monitor enquiries and send replies from the business address. Ask the provider to demonstrate that journey, including how each person accesses it and how the team sees sent messages.

In Microsoft 365, delegated access to a shared mailbox uses users' own licensed Exchange Online mailboxes. A shared mailbox is not intended for direct sign-in with a shared password, and requirements vary for storage and additional features. Check the arrangement against the actual plan and intended use. Our business email and shared mailbox guide provides the related checks.

Compare the exact services included in each proposal

Create a requirement matrix with a row for each important task and a column for each proposal. Ask suppliers to mark what is included, what requires an additional service and what remains outside the arrangement. Keep unresolved questions visible.

Check whether the proposed Microsoft 365 subscription includes email. Also check the applications, security features and administrative capabilities that the supplier says you need. Do the same for an email hosting package, including any separate licences required for the applications your team will use.

Avoid assuming that a familiar brand provides every feature under every subscription. Ask for the specific product names and configuration in the quotation. Those details let you compare the operating service rather than a loosely defined package.

Review account control and administration

Establish who controls the business's administrative account and who can add users, change access and manage billing. If a supplier performs administration, record the responsibilities and the route for requesting changes. The business should understand its own arrangement.

Walk through joining, changing role and leaving. How does a new colleague receive access? What happens to correspondence when someone moves role? Who removes departing access and preserves information the business needs through its agreed handling process?

Ask how account recovery and administrator continuity work. A service that relies entirely on one employee's personal contact details can be difficult to manage when that person is unavailable. Keep account ownership and support contacts current.

Check security and information handling in context

Discuss the controls available in the proposed plan with the responsible administrator. Ask about sign-in protection, access management, device arrangements and ways to investigate suspicious activity. Relate the discussion to how your staff actually work.

Identify any information handling requirements the business has already established and ask how the proposed service supports them. Storage, retention, recovery and export are different questions. A large mailbox does not by itself explain how records are managed or recovered.

Keep the comparison specific and avoid treating security as a single tick box. Ask which controls will be configured, who maintains them and how staff will be trained. Features that are available but never set up may not support the operating arrangement you expect.

Plan migration around more than messages

Inventory the material that needs to move: mailboxes, folders, calendars, contacts and any relevant shared resources. Ask the migration team to inspect the current environment and explain which elements can transfer through the proposed method.

Include website forms, newsletters, invoicing tools and other senders using the domain. Changing the main mailbox provider does not automatically update those services. Assign someone to review their configuration and test important customer communications.

Agree the migration sequence and the point at which staff will use the new service. Plan how changes made during migration will be handled and how the team will recognise the authoritative mailbox afterwards. Keeping two environments active without clear instructions can create confusing gaps and duplicate work.

Test the everyday user experience

Choose representative staff and tasks for a pilot or demonstration. Check reading and replying, searching older messages, using a shared address and managing appointments. Include mobile use if that is part of normal work.

Ask people to follow the proposed process without a supplier narrating every step. A service that appears straightforward during a demonstration may require training when the team uses it independently. Record difficulties and decide whether they need configuration, instruction or a different approach.

Check the receiving team's workflow too. A shared inbox can provide access without establishing who owns each enquiry. If your support process needs assignment, status tracking or a full customer history, identify how those requirements will be met rather than assuming email alone resolves them.

For an illustrative installation company, let an office coordinator receive a customer message while an engineer is away. Ask the proposed service to support a reply from the agreed team address and let the engineer find that correspondence afterwards. Then repeat the task with the coordinator absent. Record whether the required visibility comes from the mailbox configuration, an additional tool or a staff procedure. Do not infer the answer from the phrase “shared email”. A demonstration of this complete task can reveal whether a cheaper quotation genuinely fits the working arrangement or relies on forwarding messages and keeping a separate manual record. Include any resulting training or administration work in the comparison.

Compare costs over the intended operating period

List recurring subscriptions, setup work, migration, support and any separately required applications. Include the number and type of users assumed. Record introductory and ongoing arrangements clearly enough to update the comparison when staffing changes.

Consider administration and training effort alongside the invoice. A package with fewer features may suit the business well, but any manual work required to compensate for a missing capability belongs in the decision. A broader package may also create unnecessary complexity if the team uses only a small part of it.

Ask suppliers to explain renewal, cancellation and changes in user numbers. You need understandable commercial terms and operating responsibilities before choosing. Do not substitute an old advertised price for a current quotation based on your requirements.

Define acceptance and the exit arrangement

Agree what a successful setup will demonstrate. Test incoming and outgoing mail, important shared addresses, devices and connected senders. Confirm that the required historical material is present and that staff know where to get help.

Establish how the business can export necessary information and move elsewhere if its needs change. Ask for account records and practical handover documentation. A provider's export feature is most useful when the team knows who can use it and what the result contains.

Giraffe Digital's digital strategy service can help map how email, websites and business tools support customer communication. A good email comparison gives you a clear account of fit, responsibilities, migration and ongoing use, making the choice easier to explain and maintain.

Frequently asked questions

How should we list the email tasks our business must support?

Record who needs an individual mailbox and how they use it. Include office staff, mobile workers, part-time colleagues and anyone requiring access from several devices. Identify the email applications already in use and whether the team depends on particular features. List business addresses separately from people. An enquiries address, accounts address and support address may each represent a working process. Ask who reads the messages, who replies and what happens when the usual person is away. Include calendars, contacts and document collaboration where they matter. A provider comparison becomes clearer when you know whether you are buying email alone or a wider working environment. Avoid paying for a broad collection of tools simply because they are available, but do not overlook a feature the team already relies on.

How should we compare the exact services included in each proposal?

Create a requirement matrix with a row for each important task and a column for each proposal. Ask suppliers to mark what is included, what requires an additional service and what remains outside the arrangement. Keep unresolved questions visible. Check whether the proposed Microsoft 365 subscription includes email. Also check the applications, security features and administrative capabilities that the supplier says you need. Do the same for an email hosting package, including any separate licences required for the applications your team will use. Avoid assuming that a familiar brand provides every feature under every subscription. Ask for the specific product names and configuration in the quotation. Those details let you compare the operating service rather than a loosely defined package.

How should we check security and information handling in context?

Discuss the controls available in the proposed plan with the responsible administrator. Ask about sign-in protection, access management, device arrangements and ways to investigate suspicious activity. Relate the discussion to how your staff actually work. Identify any information handling requirements the business has already established and ask how the proposed service supports them. Storage, retention, recovery and export are different questions. A large mailbox does not by itself explain how records are managed or recovered. Keep the comparison specific and avoid treating security as a single tick box. Ask which controls will be configured, who maintains them and how staff will be trained. Features that are available but never set up may not support the operating arrangement you expect.

How should we test the everyday user experience?

Choose representative staff and tasks for a pilot or demonstration. Check reading and replying, searching older messages, using a shared address and managing appointments. Include mobile use if that is part of normal work. Ask people to follow the proposed process without a supplier narrating every step. A service that appears straightforward during a demonstration may require training when the team uses it independently. Record difficulties and decide whether they need configuration, instruction or a different approach. Check the receiving team's workflow too. A shared inbox can provide access without establishing who owns each enquiry. If your support process needs assignment, status tracking or a full customer history, identify how those requirements will be met rather than assuming email alone resolves them.

How should we define acceptance and the exit arrangement?

Agree what a successful setup will demonstrate. Test incoming and outgoing mail, important shared addresses, devices and connected senders. Confirm that the required historical material is present and that staff know where to get help. Establish how the business can export necessary information and move elsewhere if its needs change. Ask for account records and practical handover documentation. A provider's export feature is most useful when the team knows who can use it and what the result contains. Giraffe Digital's digital strategy service can help map how email, websites and business tools support customer communication. A good email comparison gives you a clear account of fit, responsibilities, migration and ongoing use, making the choice easier to explain and maintain.

Domains & HostingEmail Marketing