1Direct from KOBIL
KOBIL provisions your tenant in an EU region and stays your first call. The route for named accounts that want one contract and one accountable vendor.
Tenant, same business day
Billed by KOBIL
Support from KOBIL
2Microsoft Marketplace
Buy on the Microsoft agreement you already hold. The subscription activates at purchase and the tenant is provisioned automatically, with no order form to route through procurement.
Tenant in minutes
Billed by Microsoft
Support from KOBIL
3Through your reseller
Your partner sets the commercial terms and owns the relationship. The product is the same one KOBIL ships, on the same editions, whatever the logo on the invoice says.
Tenant from KOBIL
Billed by Microsoft or your partner
Support from your partner
THE PARTNER ROUTE
4Partner-provisioned tenant
The systems integrator who already runs your workplace creates your tenant in the KOBIL partner console in under an hour, then hands your IT the distribution kit. They administer the platform. Nobody but you touches your MDM.
Tenant in under an hour
Billed by your partner
Support from your partner, KOBIL behind it
KOBIL operates the platform and owns break-fix in all four, without exception.
DAYS, NOT MONTHS
Nobody installs anything. Nobody approves anything.
The rollout is a handful of objects in the management tools your IT already runs, on your own change window.
Windows service
A signed package for Intune, assigned as required to a group. It installs silently at the next device check-in, per machine, no reboot. Other MDMs take the plain MSI.
macOS service
A signed and notarised package plus a system extension profile that pre-approves the KOBIL Team ID, so the extension loads without a single user prompt.
Browser extensions
The extension ID goes on the Chrome or Edge force-install list. Users cannot remove it, and the tenant is preconfigured by policy, so there is no setup screen to walk anyone through.
.svg.webp){kind=icon}
.svg.webp)
Outlook and Teams
The add-in and the app are deployed centrally from the Microsoft 365 and Teams admin centers to the same group. The pane simply appears.
Salesforce and SAP
A managed package and a permission set for Salesforce. SAP connects over REST, so no transport is needed.
That is the whole rollout. The pilot ring is live in five working days and the estate follows in two to six weeks, entirely on your MDM's schedule.
No user prompts. No local admin rights. No VPN dependency and no inbound firewall rules.
WHAT YOUR IT DOES
Five objects in the tools you already run.
This is the whole task list for the customer side, in the order it is done. None of it is new work for an administrator who has deployed anything before.
1Create one group
A directory group holding the people who get the platform. Everything below is assigned to that one group, so adding a person later is adding a person to a group.
2Assign the service
The signed Windows package in Intune, or the plain MSI in any other MDM, and the signed and notarised macOS package with its system extension profile. Both silent, both per machine.
3Force-install the extension
One extension ID on the Chrome or Edge policy list, with the tenant preconfigured by the same policy. There is no setup screen for anyone to walk through.
4Publish the two Microsoft pieces
The Outlook add-in from the Microsoft 365 admin center and the Teams app from the Teams admin center, both to the same group. Salesforce takes a managed package and a permission set; SAP connects over REST, so there is no transport to schedule.
5Point identity at your directory
One federation to Active Directory, Entra ID or any OIDC or SAML provider. Or skip it entirely and use the built-in directory, which is ready on day one and can be federated later.
AND NOBODY DOES THIS
No user installs, approves or configures anything.
No local admin rights, and no reboot.
No inbound firewall rule and no VPN dependency.
Nobody but your own IT touches your MDM, on any of the four buying motions.
Frontline people without a managed desktop need none of it. They get the same identity, chat, approvals, tasks and signing on a mobile or shared device.
HOW IT STARTS, AND HOW IT ENDS
Try it before the contract, leave with your evidence.
30-day trial
A provisioned tenant with up to 50 seats, the built-in identity provider so day one needs no directory work, and the full client kit. No card.
Guided proof of concept
Ninety days, fixed scope, success criteria written down before it starts, and what it produces is yours whether you convert or not.
Fixed-fee onboarding
Published scope and a fixed fee, the same runbook whether KOBIL delivers it or a certified partner does.
Leaving is documented too: a read-only tenant for 30 days, a full export of chats, signed documents and audit records, then deletion on a schedule you can hand to an auditor.
No new app. No passwords. No switching. Just trust, built in.