Microsoft 365
plans, seats, and renewals.
Patolink is a Microsoft Partner. We place Microsoft 365 plans and can stay for the tenant. Seats are this product. Migration and administration are the Microsoft Solutions service.
Products / Microsoft 365
-
check_circle
Seats on their own line
Plan name, licence type, users, billing cycle, price, and renewal date sit on the product record.
-
check_circle
No public seat price
Those fields are filled on the quotation. This page does not pretend every SKU is in stock at a published rate.
-
check_circle
Service is optional
You can buy seats alone, or seats plus deployment, migration, and tenant work.
-
check_circle
Renewals stay readable
The portal will show seat renewals separately from Patolink time.
What this product is
Licences are the Microsoft 365 product. Standing up the tenant, moving mail, onboarding staff, and staying for administration are the Microsoft Solutions service. Keep them separate on the quote so a finance team sees what is software and what is Patolink.
A product record supports plan name, licence type, number of users, billing cycle, price, renewal date, implementation or setup charges, and a support package. Those fields are filled when we quote — they are not hard-coded in the shop.
Email migration fails when MX, autodiscover, and the user device wave are improvised on Friday night. If you need that work, it is scoped as service hours next to the seats. Training is part of the job, not a PDF left in a share.
Security configuration — identity, access, and tenant hardening — often sits next to the Cyber Security line. Backup and continuity are quoted when native retention is not enough for the organisation. Dynamics and Azure sit on the same Microsoft service line when the account needs them.
Who typically buys it
- —Organisations placing or renewing Microsoft 365 seats in Kenya and East Africa.
- —Tenants that need mail moved with a written cutover, not a weekend guess.
- —Teams that want tenant administration on a retainer instead of in-house.
- —Accounts that will also buy Dynamics, 3CX, or a Cloud EA VPS on the same order.
What we capture on a 365 product
Product / plan name
Which Microsoft 365 plan the organisation is buying.
Licence type
The entitlement model for that plan.
Users / seats
How many people the order covers.
Billing cycle
Monthly, annual, or another agreed cycle.
Price
Set on the quote, not hard-coded in the shop.
Renewal date
Visible later in the customer portal.
Implementation / setup charges
One-off work to stand the tenant up.
Support package
Whether ongoing Microsoft 365 support is attached.
Service versus product
Licences are this product. Deployment, migration, onboarding, tenant administration, security configuration, and backup are Microsoft Solutions services. You can buy seats alone, or seats plus service.
Google certification covers accounts that are already on Google Workspace and need the same quality of implementation rather than a forced move. We will not pretend every estate should land on 365.
After go-live
Tenant administration can move onto a managed-services retainer. Renewals for seats stay on the Microsoft 365 product line. That split is how invoices stay readable in the portal.
Administrators can add more Microsoft SKUs later without a website release. What you read here is the published starting set.
Related
Quote Microsoft 365
Send seat count, current tenant state, and whether you need migration or only licences.