Articles on: Integrations

MS Teams - Technical Prerequisites & Integration Overview

Blify is a learning & development app that integrates directly into your daily communication tools. To ensure your managers and teams can interact with Blify seamlessly within Microsoft Teams, a few configuration steps are required from your IT administrator.


This guide covers app permission policies, network whitelisting, and user provisioning.


1. Microsoft Teams App Policy (IT Admin)


Blify is available as a verified application on the Microsoft Teams Store. However, depending on your organization's security posture, end-users may not be able to install third-party apps by default.


Action Required: The Microsoft 365 / Teams Administrator must authorize the Blify app for the target users.


Option A: Direct Installation (No Admin Action Required) In many organizations, access to Microsoft-verified third-party apps is open by default.

  • The Test: Ask a user (or yourself) to open the "Apps" tab in Teams, search for "Blify," and click "Add."
  • Result: If the app opens and the chat starts, no action is required from your IT department regarding access.


If installation is blocked or requests approval, proceed to Option B or C below.


Option B: Global Rollout (Recommended for ease)

  1. Go to the Microsoft Teams Admin Center.
  2. Navigate to Teams apps > Manage apps.
  3. Search for "Blify" and ensure the Status is set to "Allowed".
  4. Go to Permission policies, select the policy assigned to your users (e.g., Global), and ensure "Third-party apps" allows Blify.


Option C: Pilot Group / Restricted Rollout If you are deploying Blify to a specific cohort (e.g., a specific Managers' program):

  1. Create a specific App Permission Policy allowing Blify.
  2. Assign this policy to the specific group of users or the pilot team involved in the training.


💡 Best Practice: Pin the App To maximize adoption and keep learning "in the flow of work," we highly recommend creating an App Setup Policy to pin Blify to the Teams sidebar for your users. This ensures the AI coach remains visible and accessible.


2. Network & Domain Whitelisting


Blify sends occasional emails to learners to drive engagement (nudges) and provide weekly training reports. To ensure these important updates reach your employees' inboxes and are not filtered as spam, we recommend authorizing our domain.


Action Required: Please whitelist the following domain in your network security configuration:*.blify.co



Note: Blify is hosted on Microsoft Azure (France Region), ensuring high standards of availability and security compatible with enterprise environments.


3. User Provisioning


Blify’s system needs to know who to engage with to personalize the learning experience. You have two options to onboard your users:

  • Option A: Self-Service (via Admin Dashboard) Admins can directly invite learners via the Blify web platform at app.blify.co. You can add users individually or bulk upload them using our template.
  • Option B: Managed Import via Customer Success If you prefer, you can provide your dedicated Customer Success Manager with a CSV file containing the list of users (First Name, Last Name, Professional Email), and we will handle the import for you.



4. Security & Data Flow FAQ


We are currently undergoing SOC 2 Type II validation, with controls implemented and the assessment in progress; certification is not yet finalized.


We understand that security is paramount when integrating AI into your workspace.

  • Does Blify read all our messages? No. Blify does not scan your internal conversations. The AI only processes messages when a user directly interacts with the Blify app (1:1 chat) or when the bot is explicitly mentioned in a channel (@Blify).
  • Where is data stored? All application data is encrypted and stored securely on AWS/Heroku servers located in European Union, in full compliance with GDPR regulations.
  • Compliance: Blify is a French company (SAS) compliant with European data protection standards. We do not share your employee data with unauthorized third parties.

Updated on: 30/01/2026