Deploy AI for Work directly inside your organization’s collaboration platforms. This guide covers integration with Microsoft Teams and Slack, including architecture, prerequisites, and step-by-step configuration.
Microsoft Teams
AI for Work integrates with Microsoft Teams using Azure Bot Service, enabling users to access AI assistance, receive proactive notifications, and use Copilot features without leaving Teams.
When to Use
| Scenario | Details |
|---|
| Heavy Teams usage | Organizations using Teams as the primary hub for communication, meetings, and file sharing |
| Workflow integration | Teams needing AI assistance during active chats, meetings, or collaborative document sessions |
| Proactive notifications | Businesses requiring AI-driven alerts, reminders, or time-sensitive updates delivered in Teams |
| Copilot enhancement | Companies extending standard Copilot with custom AI agents and specialized workflows |
Architecture
The integration uses Azure Bot Service as the communication bridge:
[AI for Work Platform] ↔ [Azure Bot Service] ↔ [Microsoft Teams]
| Component | Role |
|---|
| AI for Work Platform | Processes user requests |
| Azure Bot Service | Routes messages between the platform and Teams |
| Microsoft Teams | User-facing interface |
| Azure App Registration | Manages authentication and permissions |
Prerequisites
| Requirement | Details |
|---|
| Azure Subscription | Active subscription with administrative privileges |
| Teams Admin Access | Permission to upload and manage custom apps in the Teams Admin Center |
| AI for Work Account | Active subscription with access to the Admin Console |
Configuration
Follow these phases sequentially to ensure proper deployment and functionality.
Phase 1: Initial Setup and Webhook Configuration
Objective: Establish communication between AI for Work and Azure Bot Service.
- Log in to the Admin Console.
- Navigate to Channels > Microsoft Teams and Copilot.
- Copy and save the Webhook URL, to use in Azure Bot configuration later.
Phase 2: Azure Bot Service Creation
Create and configure the Azure Bot that serves as the communication bridge.
Create Azure Bot Resource
-
Sign in to the Azure Portal.
-
Click + Create a resource → Search for Azure Bot.
-
Select Azure Bot and configure the following:
- Bot Handle: Choose a unique name.
- Subscription: Select your active subscription.
- Resource Group: Create or reuse an existing group.
- Pricing Tier: Select based on expected usage.
- App Type: Select Multi-Tenant or Single-Tenant based on organizational needs.
Configure Bot Resource
- After deployment completes, click Go to resource and navigate to Configuration in the left sidebar.
- Paste the webhook URL copied from the AI for Work platform into the Messaging endpoint field and click Apply to save the configuration.
Phase 3: Authentication and Security Setup
This phase varies based on your chosen App Type (MultiTenant vs SingleTenant).
For MultiTenant Applications
Generate Client Secret
-
In Configuration, click Manage Password next to the Microsoft App ID.
-
Go to Certificates & secrets → + New client secret.
-
Enter description and expiry → Add.
-
Copy the Value of the client secret (App Password).
-
Record the Microsoft App ID and App Password for the Platform configuration.
For Single-Tenant Applications
Follow the steps for Multi-Tenant setup. Also, note the Tenant ID for the Platform configuration.
Phase 4: Enable Microsoft Teams Channel Integration
Configure the bot to communicate with Microsoft Teams and enable Copilot integration.
-
Navigate to Channels in the bot resource menu and locate the Available Channels section.
-
Select the Microsoft Teams channel and M365 Extensions channel (required for Copilot integration), review channel information, and select Save.
The Web Chat channel isn’t supported for this integration, so keep it disabled.
Phase 5: Proactive Notifications Setup
Enable the bot to send proactive notifications to users, which is essential for AI-driven interactions.
Create App Registration for Notifications
-
In the Azure Portal, navigate to App registrations and select + New registration.
-
Register New Application:
- Name: Provide a descriptive name (for example, Platform-Microsoft Teams-Notifications).
- Supported account types: Choose based on organizational requirements.
- Redirect URI: Leave blank for this use case.
-
Select Register.
Add Microsoft Graph Permissions
-
In the app registration, navigate to API permissions and select Add a permission.
-
Select Microsoft Graph → Application permissions.
Required Permissions: Add the following permissions for full functionality:
MS TeamsAppInstallation.ReadForUser.AllMS TeamsAppInstallation.ReadWriteSelfForUser.AllMS TeamsAppInstallation.ReadWriteForUser.AllUser.Read.AllAppCatalog.Read.All
-
Grant Admin Consent.
-
Generate a Client Secret and note down App ID, Directory (Tenant) ID.
-
Configure these values in AI for Work under Microsoft Teams & Copilot Channel Settings.
-
Generate a JWT token for secure communication.
Phase 6: Configure AI for Work Platform
Provide Azure Bot credentials to the Platform to establish secure communication.
-
Navigate to the Admin Console.
-
Locate Channels on the left pane.
-
Select Microsoft Teams and Copilot.
-
Enter the following credentials under Configuration:
- Microsoft App Tenant ID: (SingleTenant only) The tenant ID from the bot’s app registration.
- Microsoft App ID: The App ID from your Azure Bot resource.
- App Password: The client secret from the bot’s app registration.
- App ID of the Microsoft Teams App: The additional app credentials for sending Proactive Notifications.
- Application (Client) ID: From the notifications app registration.
- Client Secret: From the notifications app registration.
- Delivery (Tenant) ID: From the notifications app registration.
Customization Options
By default, the Microsoft Teams app appears with the name AI for Work, the standard logo, and the default description. Administrators can customize the application before publishing to Microsoft Teams:
- App Name – Choose a custom display name for Microsoft Teams.
- Logo – Upload an organization-specific logo.
- Description – Provide a tailored description that reflects organizational context.
Copilot Enablement
During configuration, you are prompted to Enable Copilot Integration. We recommended you to enable this option so that Teams users can access the Platform features using Copilot.
Phase 7: Microsoft Teams Application Deployment
Deploy the Platform app to Microsoft Teams for user access.
Generate Application Manifest
Upon configuring credentials in the Platform, generate and download the Microsoft Teams application manifest file. This manifest file contains all the necessary configurations for integrating with Microsoft Teams.
Upload to Microsoft Teams Admin Center
Ensure you have Upload Custom App permissions in the Microsoft Teams Admin Center. Verify organizational policies allow custom app installations.
-
Sign in to Microsoft Teams Admin Center.
-
Navigate to Microsoft Teams apps → Manage apps.
-
Click Upload new app.
-
Select the downloaded manifest file from the Platform.
-
Wait for upload and validation to complete.
Configure App Permissions and Policies
Review the uploaded application details and configure app permission policies as needed. Set up app setup policies for automatic installation (optional).
Phase 8: User Access Configuration
You can decide how to distribute the Platform app in Microsoft Teams:
- Add App for All Users (Recommended) — Automatically adds the Platform app for all employees in the organization. All users receive a notification in Microsoft Teams and a welcome message when the app is added.
Users must also be provisioned in the Account Hub of the Platform to access the app.
- Let Users Add App Themselves — The app is available in the Microsoft Teams App Marketplace. Users need to search for the app in Microsoft Teams and add it manually. No automatic notifications or installations occur.
Users must be present in the Account Hub to use the app.
- Add App for Selected Users or User Groups — Assigns the app only to specific users or security groups. Selected users are automatically notified in Microsoft Teams and receive the welcome message. Other users must find and install the app manually from the Marketplace.
Selected users must also exist in the Account Hub for access.
Troubleshooting
Bot Not Responding in Microsoft Teams
- Verify the webhook URL is correctly configured in Azure Bot.
- Check that the Microsoft Teams channel is enabled and saved.
- Validate client secrets haven’t expired.
Authentication Failures
- Confirm all required API permissions are granted with admin consent.
- Verify client secrets are copied correctly (Value, not Secret ID).
- Check tenant ID matches between configurations.
Manifest Upload Failures
- Ensure you have proper permissions in the Microsoft Teams Admin Center.
- Verify the manifest file is not corrupted during download.
- Check organizational policies to allow custom app uploads.
Proactive Notifications Not Working
- Verify all required Microsoft Graph permissions are granted.
- Verify that the notification app registration client secret is valid.
- Ensure JWT token generation is working correctly.
Slack
AI for Work integrates with Slack as a custom app, enabling users to perform work tasks, query enterprise knowledge, and interact with AI agents without leaving Slack.
When to Use
| Scenario | Details |
|---|
| Seamless workflow integration | Teams needing AI assistance during active conversations, with persistent chat history and context retention |
| Enterprise knowledge access | Organizations connecting users to knowledge repositories — documents, LLMs, and data-driven answers — within Slack channels |
| Heavy Slack usage | Remote or hybrid teams that treat Slack as their central hub for communication and project coordination |
Architecture
The integration uses Slack’s Developer Portal and OAuth authentication:
[AI for Work Platform] ↔ [Slack App Configuration] ↔ [Slack Workspace]
Prerequisites
| Requirement | Details |
|---|
| Slack Workspace | Active workspace with administrative privileges |
| Slack Developer Portal Access | Permission to create and manage apps in your workspace |
| AI for Work Account | Active subscription with access to the Admin Console |
Integration Lifecycle
| Phase | Steps |
|---|
| Configuration and creation | Customize app details in the Admin Console to generate an App Manifest, then use the manifest to create the app in the Slack Developer Portal |
| Connection and security | Perform a credential exchange to link the platforms, then authorize the required permissions |
| Rollout | Define the welcome experience, then grant user access to onboarded employees |
Configuration
Step 1: Configure App Display Settings
-
Log in to the Admin Console.
-
Navigate to Channels → Slack.
-
Open the Configuration page and set the following:
| Setting | Description |
|---|
| App Name | Name users see when interacting with the app in Slack |
| App Description | Explains the app’s capabilities; appears in the About section in Slack |
If you change the app name or description after deployment, generate a new manifest and update the Slack app in the Developer Portal.
Step 2: Generate the App Manifest
-
On the Configuration page, click Get Manifest.
-
Copy the entire manifest code.
The manifest contains all permissions, features, and settings required for the Slack app.
Step 3: Create the App in the Slack Developer Portal
Access the portal
-
Go to the Slack Developer Portal.
-
Sign in with your workspace credentials.
-
Click Your Apps.
Create the app
-
Click Create New App (or Create an App for first-time users).
-
Select From a manifest.
-
Select the target workspace from the Slack Workspace dropdown.
Paste the manifest
- Paste the manifest code copied from the Platform.
- Click Next, review the configuration and permissions, then click Create.
Step 4: Configure App Credentials
Retrieve credentials from Slack
-
In the Slack Developer Portal, navigate to Basic Information in the left sidebar.
-
Scroll to App Credentials and copy:
- Client ID
- Client Secret
- Signing Secret
Enter credentials in AI for Work
-
Return to the Admin Console > App Credentials page.
-
Paste the copied values into the corresponding fields.
-
Click Authorize.
Complete authorization
- Review the permission request that Slack displays.
- Click Allow.
On successful authorization, the app deploys to your Slack workspace and becomes visible to all onboarded users.
Step 5: Customize the Welcome Experience
-
In the Admin Console, navigate to the Welcome Experience page.
-
Configure the following:
| Setting | Description |
|---|
| Welcome Message | Introductory message users see when they first open the app |
| Sample Prompts | Up to four clickable prompts to help users start a conversation |
-
For each sample prompt, set:
- Display Message — Text shown to users as the prompt button.
- Actual Query — The complete query sent to the Platform when the user clicks the prompt.
-
Click Save and Update. Changes take effect immediately for all users.
You can update the welcome experience at any time. Changes apply to all users immediately.
Step 6: Customize the App Icon (Optional)
-
In the Slack Developer Portal, go to Basic Information → Display Information.
-
Click Upload next to App Icon and select an image file.
-
Optionally, set a Background Color.
-
Click Save Changes.
User Access Management
Only users who have onboarded to AI for Work can interact with the Slack app. Before deploying, ensure you:
- Invite all intended users to the Platform.
- Onboard users with the appropriate access permissions.
- Confirm users exist in both the Platform and the target Slack workspace.
Users in the Slack workspace who have not onboarded will see the app but receive an error when attempting to send a message.
Current Limitations
| Limitation | Details |
|---|
| Single workspace | The app deploys to one Slack workspace. Multi-workspace deployments require a separate app instance per workspace. |
| Direct messaging only | The app functions as a direct messaging interface. Adding the app to channels is not supported, and mentions in public or private channels do not trigger responses. |
