Your customers register, grant Microsoft consent and deploy their Teams apps from buttons in your portal. They never get a TeamMate email and never sign in to another portal. TeamMate runs in the background.
Free 30-day proof of concept for service providers.
Normally, a customer’s Microsoft 365 admin gets a registration email, approves access to their Teams organization, and then configures services in the TeamMate enterprise portal. Bespoke Access is an alternative for providers who want to keep customers entirely in their own environment. You create the customer through the TeamMate API. The API then gives you a one-time link for each step the admin has to take. You show those links as buttons or links in your portal, and the admin is returned to your portal when each step is done.
Customers never see a TeamMate registration email or portal. Every step happens in yours.
You decide where each step appears and what it says: on a signup page, a setup wizard or a settings screen.
Admins approve permissions on Microsoft’s own consent screen, then land back on the page you choose.
Ask for each permission when it is needed: user sync, presence sync, app deployment, and the Teams app for each service.
With the optional “Allow management by service provider” consent, your team can handle ongoing provisioning for the customer.
Works with PBX Connector, SIP Trunk Connector, ACS Call App, Teams Call Recording, SMS Connector and ChatBridge.
Call the API to create the customer account, pick their services, and assign SBC regions and PBX types.
Ask the API for the link for a step, such as registration, a consent or admin sign-in, along with the address in your portal to return to.
The customer’s Global Admin clicks your button, reviews the permissions on Microsoft’s consent screen and approves them.
TeamMate processes the response and sends the admin back to your page. Registration returns sign-in tokens for further API calls, and consent steps return a status.
The customer’s admin gets a registration email and manages services in a TeamMate enterprise portal branded with your name. Quickest to launch, with no development work. See white-label Microsoft Teams.
Every step happens in your own portal through the API. For providers with their own customer portal who want one seamless experience.
A TeamMate API workflow that lets a service provider run the whole Microsoft Teams onboarding process, including registration, Microsoft consent and app deployment, from its own portal. Customers never receive a TeamMate email or use a TeamMate portal.
Yes. Each step opens Microsoft’s own consent screen, where the customer’s admin reviews and approves the permissions. Afterwards they are sent back to the page in your portal that you chose.
User sync, presence sync and app deployment are required. Call app and Teams app consents are needed depending on the services you sell. “Allow management by service provider” is optional but recommended, because it lets your team handle provisioning for the customer.
PBX Connector, SIP Trunk Connector, ACS Call App, Teams Call Recording, SMS Connector and ChatBridge.
Yes. Bespoke Access uses the TeamMate REST API, so you will need someone to add the API calls and buttons to your portal. If you would rather not build anything, standard onboarding with your white-label portal needs no development.
After registration, the access token lasts 60 minutes and can be renewed with a refresh token, which lasts 30 days. After that, the admin signs in again from your portal.
See Bespoke Access in a live demo, or try it in a proof of concept.
Free 30-day proof of concept for service providers.