Deploying Beedeez as a Microsoft Teams app
Your office-based teams already spend their day in Microsoft Teams, and opening a separate application to follow a training path is one step too many. Beedeez can be published inside Teams, so that your learners reach their platform without leaving the tool they already have open. This article explains what you need to gather, what your Teams administrator does, and what to check before you roll the app out to everyone.
Deploying Beedeez as a Microsoft Teams app
Your office-based teams already spend their day in Microsoft Teams, and opening a separate application to follow a training path is one step too many. Beedeez can be published inside Teams, so that your learners reach their platform without leaving the tool they already have open. This article explains what you need to gather, what your Teams administrator does, and what to check before you roll the app out to everyone.
⚠️ Prerequisites: you need a Microsoft Teams administrator account with application management rights in the Teams Admin Center, and the Beedeez application package as a ZIP file. That package is prepared by Beedeez for your account: ask your Beedeez contact for it, as it cannot be downloaded from the back office.
Settle two questions before you upload anything
The first question is the name your learners will see in Teams. The package carries that name, and changing it later means asking Beedeez for a new package and uploading it again. Decide on the name with the people who will announce the app internally, before the first deployment.
The second question is who the app is for. Teams lets you authorise the application for your whole organisation or for specific groups only, and it treats authorising and installing as two separate decisions. Settle both with the person who administers Teams, because they are set in the Teams Admin Center and not in Beedeez.
Upload the package into Teams
Your Teams administrator uploads the ZIP file as a custom application in the Teams Admin Center, from the application management screens. Microsoft owns those screens, so the exact wording depends on the version of the Teams Admin Center you use. Once the upload succeeds, the application appears in the list of applications published for your organisation.
Authorise the app, then install it
Authorising the application and installing it are two different actions, and confusing them is the most common reason a deployment looks finished while nobody sees the app.
- Authorising decides who is allowed to add the application. A person who is merely authorised still has to find Beedeez in the Teams application store and add it.
- Installing pushes the application to the people or groups you choose. They find it in Teams without doing anything themselves.
If you want your learners to see Beedeez without being asked to install anything, your Teams administrator has to install it for them, not only authorise it.
ℹ️ Good to know. Teams does not always propagate a newly published application or a new version immediately. Leave time between the deployment and your internal announcement, and check again later before concluding that the deployment failed.
Grant administrator consent
The application asks Microsoft for permission to read the signed-in person’s basic profile. Beedeez uses that identity to recognise the learner and open their platform. As long as a Microsoft administrator has not granted consent for your organisation, sign-in from Teams fails.
Consent is granted once, in the Teams Admin Center or on the Microsoft identity side, by an administrator of your tenant.
Check that sign-in works
Run the test with a standard account, not with your administrator account. An administrator account can behave differently, and it tells you nothing about what your learners will get.
- Open Teams with the test account and find the application.
- Open it and wait for the Beedeez platform to load.
- Check that the person reaches their content without being asked to sign in again.
The third point is the one that matters. Beedeez recognises the learner by matching the Microsoft identity Teams provides with the Beedeez account that carries it. When no Beedeez account matches that identity, the application opens on a sign-in screen instead of the platform.
⚠️ The Teams app does not replace single sign-on, it relies on identity being settled. If your learners’ Microsoft identity does not correspond to their Beedeez accounts, everyone lands on the sign-in screen. Settle identity and provisioning before deploying the application.
Update or rename the application
An update follows the same route as the first deployment: Beedeez sends a new ZIP package, and your Teams administrator uploads it as a new version of the existing application. This is also how the displayed name changes, since the name travels with the package.
After an update, install the new version on a test account and open it before announcing anything. As with a first deployment, propagation is not immediate.
What this integration does not cover
The Teams application is an access route to the Beedeez platform. It does not create video meeting links for your remote sessions: that is a separate integration, described in Generating Teams or Google Meet meetings.
It also does not replace the mobile application for teams without a workstation. The two coexist on the same accounts and the same progress records, so a learner who uses Teams at the office and the mobile application in the field keeps one history.