The addresses your business answers from
The client did not email a person. They emailed the business. That is precisely where the trouble starts.
An SME’s inbox estate can include info@, sales@, enquiries@, accounts@, admin@ and orders@. There may be a noreply@ address that people reply to anyway, plus several addresses created for a campaign in 2019 and never retired. They take minutes to set up. Depending on the agreement and configuration, they may not need a separate user licence. That makes them feel free.
Which is exactly why a business can end up with dozens it cannot account for.
Ask someone to name every public-facing address, who owns each one and what should happen to incoming messages. If the answer requires rummaging through old emails, the address estate is already a business risk. Not because every group address is wrong, but because customers, suppliers and staff need to know where a message goes and who is responsible for acting on it.
Four addresses that look alike to a sender
From the outside, four different Microsoft 365 arrangements can look like the same “team email”. Their behaviour is not the same.
A shared mailbox has its own storage and sent items, with access delegated to named users. Permissions need configuring deliberately, including whether people can read messages and whether they can send as the shared address. Used properly, it can keep a business conversation in a business location.
A distribution list or group is principally a routing mechanism. A message is delivered to its members, but there may be no central mailbox that retains the conversation and its replies. A client writes to sales@, the message fans out to forty people, and every recipient assumes somebody else has responded. That is not a queue. It is a small experiment in optimism.
An alias is another address attached to an existing mailbox. If enquiries@ points to one employee’s personal mailbox, then the business address depends on that person’s account and whoever remembers the arrangement. The address may stop working, or be reassigned without a clear decision, when their role changes.
Then there is a person’s own mailbox being used as the business address. A customer writes to accounts@ but gets a reply from an employee’s personal address. The thread moves away from the business route; what was quoted, promised or agreed may now sit in an individual mailbox.
The sender sees one address. The business needs to know what sits behind it.
Ownership is the missing field
Every address needs a named accountable owner and a stated purpose. A list of members is not ownership. The owner is the person or role accountable for the address’s purpose, its day-to-day handling and the decisions about access and retention. That does not mean they personally answer every message.
An inbox may contain quotes, order confirmations, contract variations agreed by email, complaints and invoice disputes. It may also hold personal information. A message to a group address is still a record the business may need to locate, retain appropriately or produce under pressure. If the business cannot say who owns that record, it may struggle to say who keeps it, who deletes it or how to find it.
The GOV.UK data protection guidance for businesses is a plain-English starting point: if a business stores or uses personal information, it must follow data protection rules, including keeping information secure and responding to data protection requests. The ICO’s storage limitation principle also means personal data should not be kept for longer than necessary for its purpose.
An inbox used as an indefinite archive is how a business fails a retention test it never knowingly set. Keeping everything forever is not a retention policy. It is postponing a decision until someone else needs an answer.

Access has to be designed, not inherited
Membership and sending rights are different decisions. A colleague may need to see messages but not send from the address. Someone else may need to send as accounts@, making the message appear to come from that address, or send on behalf of it, showing their own identity too. Send-as is not just a convenience setting. It is a decision about who is authorised to speak for the business under that identity.
Do not give a team a shared password. Give named users delegated access through their individual accounts, so permissions can be reviewed and removed and each person’s own sign-in protections still apply. Multi-factor authentication should remain part of the account security design. The NCSC’s Cyber Essentials overview sets out user access control as one of its core technical controls and provides a useful security baseline.
There is also the device problem. A returned laptop or phone may still be signed in to accounts@. A distribution list may have external members left behind from an old campaign. These are not theoretical reasons to review access: they are ordinary consequences of treating an address as a quick admin task rather than a business asset. The NCSC guidance on managing deployed devices is relevant when considering how access and data persist on devices after they have been issued.
What actually goes wrong
The leaver whose personal mailbox was the de facto accounts address leaves with the history of supplier conversations and the context behind an unresolved invoice. The business can still receive mail at accounts@, perhaps, but the person who understood what it meant is gone.
A rule forwards client messages to someone’s personal webmail so they can “keep an eye on things” at the weekend. Now a business conversation has crossed into an account outside its normal access and retention controls. An auto-reply stays active after the campaign or holiday ends, making customers think the business is closed. A mailbox reaches its storage quota and starts rejecting messages; the issue is reported as an email outage, when the underlying problem is capacity and no one was monitoring it.
There is the mailbox treated as a filing cabinet, with a decade of attachments and no clear retention decision. And there is the group address where a request to change bank details arrives. Several people see it, none is clearly responsible for verifying it, and the person who acts is the least inclined to be suspicious.
These are different failures, but they share one cause: the address exists without a clear operating model. Effective Managed IT Services can support the technical controls and review process, but cannot decide who in the business owns an invoice dispute or approves a payment change. That decision belongs in the business strategy first.
A fraud surface and a data protection surface
A shared inbox can be attractive to an attacker precisely because responsibility is diffuse. Everyone assumes someone else checked. A message asking to change bank details can be sent to a group address, where it may look like routine administration rather than a high-risk instruction. The response should be a verification process, not a better-looking email. Call a known number already held in your records. Do not use the number supplied in the message. The NCSC’s phishing guidance recommends using other channels to verify important requests.
An address is also a route into data protection responsibilities. A subject access request sent to info@ can sit there for weeks while the response clock runs. Staff may not recognise it as a request, or may assume another team is handling it. The ICO’s right of access guidance explains how organisations should recognise and respond to requests. A business needs a route that identifies the request, assigns an owner and makes sure it reaches the people who can search relevant records.
A mailbox export copied to a personal device can expose an address list or other personal information. Whether an incident must be reported depends on the circumstances and the risk to people, but the organisation should assess and document its decision either way. The ICO guidance on personal data breaches explains the assessment and reporting process.
There is a marketing question too. A sales@ address used to send bulk email does not, by itself, answer whether the business has a lawful basis to process the personal information involved. That conversation needs to happen before the activity, not after a campaign has gone out. The ICO guide to lawful basis explains that the appropriate basis depends on the purpose and context, and should be determined and documented.

Build an address register, then manage it
The practical starting point is one register, with one line for every address. Record its purpose, type, named owner, who can see it, who can send as it, the retention approach and what should happen instead if it is retired. Add any relevant forwarding or routing arrangements, and record when the entry was last reviewed.
Use one owner and one purpose per address. No new address without both. That does not mean an address can only have one member or one person who works on the mail. It means the business knows who is accountable for its operation and why it exists. Triage should belong to a named team or role, not to the vague hope that somebody will notice.
A good Helpdesk Support model can turn an inbox into a logged request that is assigned, tracked and closed, rather than relying on someone’s attention and memory. For operational questions, that creates a clearer route from receipt to resolution. It is not necessarily the right treatment for every customer or legal correspondence, but it is better than an unowned message sitting in a crowded inbox.
At platform level, Cloud Solutions can support the design and review of Microsoft 365 mailboxes, permissions and access controls. The register also helps your provider deliver Managed IT Services against decisions the business has actually made. If system or device alerts go to generic addresses that nobody reads, Network Solutions can help review how those alerts are routed and monitored. An alert address that nobody checks is not a monitoring process.
When an inbox is really a workflow
If three people refresh orders@ all day, copy details into another system by hand and try to remember which messages are waiting, the business may have a case queue pretending to be email. The issue is not that email is inherently unsuitable. It is that the volume and nature of the work may need structured ownership, statuses, hand-offs and a reliable record of action.
A governed Dynamics 365 Jump Start can be a point to design that workflow properly, alongside the wider system-modernisation decisions. The aim is not to move an inbox into software for its own sake. It is to decide what work arrives, who acts on it, what information is needed and where the authoritative record belongs.
The same principle applies to a legacy system. An IBM i job may email a nightly report or alert from a generic address, while any replies land nowhere useful. IBM i Management should include understanding how these system-generated messages fit into the operating model: which alerts matter, who receives them, and how an issue becomes owned work rather than unread mail.
The cost of not knowing
A mailbox may have storage and licensing implications under the business’s particular agreement, so the right question is not whether every address is free. It is whether the configuration matches the purpose and the terms in use. Full mailboxes kept purely as storage, duplicate subscriptions attached to addresses nobody recognises, and alert-only inboxes effectively dedicated to robots all deserve a review.
Technology Expense Management helps reconcile what is being paid for with what is actually in use. That review is more useful when the address register identifies which accounts and services support a real business process. It can also show where a change in design might simplify access, reduce duplication or make responsibilities clearer, without assuming savings that have not been assessed.
The same review should include Voice and Connectivity. The published business phone number and published business email address have the same basic problem: customers need a reliable route, and the business needs someone accountable for what arrives. When the register is built, review phone numbers, enquiry routes and any published out-of-hours contact details alongside the mail addresses.
Unattended addresses matter in a continuity event too. After an outage, the shared inbox may be where both the “we are back” message and the backlog arrive. Someone has to own both: the communication and the work waiting behind it. Disaster Recovery planning should account for how customers will contact the business, who can access the relevant addresses and how incoming work will be handled while normal systems recover. A technical recovery without a person responsible for the inbox is only half a recovery.
A first-month tidy
Start with the administration centre, not a memory test. List every address in the tenant, then compare that list with the website, invoices, signatures and systems that send mail. Find aliases that point into individual mailboxes. Review forwarding and inbox rules, including any that route messages outside the organisation. Confirm the purpose and owner for each address before changing how it works.
Where an address is effectively a team inbox but is configured as an accidental group or tied to an individual, decide whether a shared mailbox is more appropriate. Review who can read it and who can send as it. Set a retention approach that reflects the purpose and any relevant record-keeping requirements; do not simply retain everything indefinitely because the storage exists.
Record the owner, purpose, type, permissions and retirement route in the register. Tell clients and suppliers if their route is changing, and make sure the new route is actually monitored before retiring the old one. Then review the register regularly and alongside role changes and leavers. The point is not to create a ceremonial spreadsheet. It is to keep the business’s public routes aligned with the people and processes that answer them.

Decide who speaks for the business
An address register is not an IT tidy-up. It is the business deciding who speaks for it, what that identity is for and what happens to the record once the conversation ends.
That is where the Fractal IT Director approach begins: strategic consultation establishes the operating model, accountability and the infrastructure needed to execute it. Cloud Solutions can support the right platform configuration; Helpdesk Support can turn incoming work into a managed queue; Network Solutions and Voice and Connectivity can help make alerts and contact routes dependable. These execution services support the decisions. They cannot substitute for them.
For businesses reviewing how their technology and operational support fit together, Evestaff is the gateway to the group’s services.
An address without an owner is not a shared inbox. It is a shared risk.
SEO keywords:
Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity, IT Consultancy, Fractal IT Director
Join The Discussion