Microsoft Teams and Copilot Integration - Configuration¶
This document provides detailed step-by-step instructions for implementing AI for Work integration with Microsoft Teams. Follow these phases sequentially to ensure proper deployment and functionality.
Step-by-Step Implementation Guide¶
Phase 1: Initial Setup and Webhook Configuration¶
Objective: Establish communication between AI for Work and Azure Bot Service.
- Log in to the AI for Work Admin Console.
- Navigate to Channels → Microsoft Teams and Copilot.
- Copy the Webhook URL (you will use this in Azure Bot configuration).
Phase 2: Azure Bot Service Creation¶
Create and configure the Azure Bot that will serve 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.
-
Enter description and expiry → Add.
- Copy the Value of the client secret (App Password).
- Record the Microsoft App ID and App Password for AI for Work configuration.
For Single-Tenant Applications
Follow the steps for Multi-Tenant setup. Also, note the Tenant ID for AI for Work configuration.
Phase 4: Enable MS 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 MS Teams channel and M365 Extensions channel (required for Copilot integration), review channel information, and click Save.
Note
The Web Chat channel is not supported for this integration and should remain 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 click + New registration.
- Register New Application:
- Name: Provide descriptive name (e.g., AIWork-MS Teams-Notifications).
- Supported account types: Choose based on organizational requirements.
- Redirect URI: Leave blank for this use case.
- Click Register.
Add Microsoft Graph Permissions
-
In the newly created app registration, navigate to API permissions and click + Add a permission.
-
Select Microsoft Graph → Application permissions.
Required Permissions: Add the following permissions for full functionality:
MS TeamsAppInstallation.ReadForUser.All
MS TeamsAppInstallation.ReadWriteSelfForUser.All
MS TeamsAppInstallation.ReadWriteForUser.All
User.Read.All
AppCatalog.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 MS Teams & Copilot Channel Settings.
- Generate a JWT token for secure communication.
Phase 6: Configure AI for Work Platform¶
Provide Azure Bot credentials to the AI for Work platform to establish secure communication.
Access AI for Work Configuration:
- Navigate to your AI for Work Admin Console.
- Locate Channels on the left pane.
- Select Microsoft Teams and Copilot.
-
Feed the following credentials under the 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 MS Teams App: The additional app credentials for sending the 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 MS Teams app appears with the name AI for Work, the standard AI for Work logo, and the default description. Administrators can customize the application before publishing to MS Teams:
- App Name – Choose a custom display name for MS Teams.
- Logo – Upload an organization-specific logo.
- Description – Provide a tailored description that reflects organizational context.
Copilot Enablement
During configuration, you will be prompted to Enable Copilot Integration. It is recommended to enable this option to ensure that MS Teams users can access AI for Work features through Copilot.
Phase 7: Microsoft Teams Application Deployment¶
Deploy the AI for Work application to Microsoft Teams for user access.
Generate Application Manifest
Download Manifest: Upon configuring credentials in the AI for Work platform, generate and download the MS Teams application manifest file. This manifest file contains all the necessary configurations for integrating with Microsoft Teams.
Upload to MS Teams Admin Cente
Prerequisites Verification: Ensure you have Upload Custom App permissions in the MS Teams Admin Center. Verify organizational policies allow custom app installations.
- Sign in to Microsoft Teams Admin Center.
- Navigate to MS Teams apps → Manage apps.
-
Select the downloaded manifest file from AI for Work.
- Wait for upload and validation to complete.
Configure App Permissions and Policies
App Approval: Review the uploaded application details and configure app permission policies as needed. Set up app setup policies for automatic installation (optional).
After uploading, configure app permission and setup policies.
Phase 8: User Access Configuration Options in AI for Work¶
You can decide how to distribute the AI for Work app in MS Teams:
-
Add App for All Users (Recommended)
- Automatically adds the AI for Work app for all employees in the organization.
- All users receive a notification in MS Teams and a welcome message when the app is added.
Note
Users must also be provisioned in the AI for Work Account Hub to access the app.
-
Let Users Add App Themselves
- The app will be available in the MS Teams App Marketplace.
- Users will need to search for the app in MS Teams and add it manually.
- No automatic notifications or installations occur.
Note
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 MS Teams and receive the welcome message.
- Other users must find and install the app manually from the Marketplace.
Note
Selected users must also exist in the Account Hub for access.
Troubleshooting Guide¶
Bot Not Responding in MS Teams
- Verify the webhook URL is correctly configured in Azure Bot.
- Check that the MS 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 MS 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.
This integration enables seamless access to AI for Work capabilities within Microsoft Teams, providing users with powerful AI assistance without leaving their collaborative environment. The bot-based architecture ensures secure, scalable communication while maintaining compliance with organizational security policies.
Regular maintenance of credentials and permissions, along with proper monitoring, will ensure the continued reliable operation of the integration.