KENYA · GUIDE 0595 · EDITION 4.7
Email account setup in Kenya: Equipment and Supplier Buying Checks
Editorial update: 28 October 2026 · Business planning reference · Review scope
Purchase for the required result
Compare Tenant licences, Registrar DNS access, Test matrix by specification, compatibility and buying checks, before comparing prices.
This is a planning reference for email account setup. The order below is an invented teaching case. It is not a completed customer job, an operating approval or a prediction of demand or earnings.
The example offer and its boundary
Fictional email setup EMA-95 prepares three Microsoft 365 business mailboxes on an owner-held domain. Output is user/alias map, approved DNS change plan, mail-flow tests and owner recovery handover. Historical migration, mass mail, impersonation, credential sharing and guaranteed inbox placement are excluded. Owner/admin approves access and creates recovery factors personally.
The resource brief to send for quotations
| Resource | Required variant or quantity | Inspection or document check |
|---|---|---|
| Tenant licences | Three appropriate user licences under owner control. | Confirm exact plan/cost and required features. |
| Registrar DNS access | Authorised change role and previous records. | Agree rollback and support contacts before cutover. |
| Test matrix | Three users/aliases plus external mail checks. | No real customer data used in testing. |
Use the delivery checkpoints to check suitability
| Planning stage | Acceptance evidence to agree |
|---|---|
| Inventory mail dependencies | Do not change MX before all required mailboxes exist. |
| Verify domain/access | No invented verification record or shared personal password. |
| Prepare DNS changes | Do not overwrite an SPF policy blindly or add conflicting records. |
| Test mail flow | Check destination and headers/status where appropriate; a sent-folder copy is not receipt. |
| Handover recovery | Old mail stays at prior host unless a separate migration is performed; explain this before cutover. |
Compare like with like
Request the same specification, unit/pack size, usable quantity, destination, lead time and support terms from each supplier. Keep an unmatched lower-priced variant separate. A supplier’s photograph, headline price or description does not establish that the delivered item fits this order.
Goods received record
| Field | What to enter for this offer |
|---|---|
| Quote and delivery reference | Exact supplier quote and date, plus the receiving document |
| Item match | Confirm exact plan/cost and required features. |
| Quantity and condition | Count or measure the actual received lot; keep mismatches separate |
| Release decision | Old mail stays at prior host unless a separate migration is performed; explain this before cutover. |
| Unresolved evidence | Actual tenant, DNS, licences and sender inventory unverified. |
Do not use an item with an unresolved suitability question for work that depends on that question. Obtain the relevant competent assessment rather than treating this checklist as technical approval.
References and their limits
Connect domain DNS records — Microsoft 365
Mailbox preparation before MX change and tenant-specific DNS records. Reference check recorded 2026-10-26.
Rights Of A Data Subject
Kenyan privacy principles and data minimisation; not a complete compliance assessment. Reference check recorded 2026-10-26.
Small organisations guide to cyber security — NCSC
Defensive small-business account/device/backup/scam guidance, not a security certification. Reference check recorded 2026-10-26.
Recorded references support only the scope stated beside them. They do not prove current supplier stock, a local quotation, actual buyer demand, operator competence or the feasibility of this particular business. Later editorial changes do not refresh earlier source-check dates.
Prepared by Business Starter Guides using AI-assisted drafting and desk editorial checks. Independent operator trials and specialist certification are not claimed. See the editorial method for the review scope.
Editorial method and evidence limits