Microsoft Teams

Microsoft Teams is a Communicator Integration. Communicator Integrations allow Dropzone to ask questions of your employee base and use their responses to improve the quality of analysis.

Dropzone uses a Microsoft Teams Bot and an Azure AD Application to communicate directly with people in your organization. This guide will walk you through the necessary setup in the Azure Portal, Azure AD, and Microsoft Teams Developer/Admin portals.

For more information, see our Communicators overview.

Setup Overview

To enable the Microsoft Teams Communicator, you will perform the following actions:

• Create an Azure Bot and configure it for Microsoft Teams

• Ensure your existing Azure AD App Registration for Microsoft Graph has the correct API permissions and a client secret. (This is often the same App Registration used for other Dropzone Microsoft 365 integrations.)

• Create a Teams App in the Developer Portal, linking it to your Azure Bot

• Publish the Teams App to your organization's app catalog via the Teams Admin Center

• Collect the necessary IDs and secrets for Dropzone configuration

---

Azure Portal & Azure AD Setup

1. Create Azure Bot

• Navigate to "Azure Bot" service:

  • In the Azure Portal (portal.azure.com), use the top search bar to find "Azure Bot"

    • 

  • Click "Azure Bot" from the Marketplace results

  • Click "+ Create"

• Configure Project Details:

  • Bot handle: Enter a unique name (e.g. dropzone-ai-interviewer)

    • 

  • Subscription: Select your Azure subscription

  • Resource group: Select or create a new one

  • Microsoft App ID section:

    • Select "Use existing app registration"

    • Application ID: Enter the Application (client) ID of your Azure AD App Registration that is configured for Microsoft Graph API access. This is typically the same App Registration used for other Dropzone integrations with Microsoft 365 services. (e.g. adc383dc-d84f-463d-ac62-153330eccb57)

      • (To find this App ID: Azure Portal > Azure Active Directory > App registrations > [Your App Name] > Overview page. If you have an existing Dropzone Microsoft 365 integration, this is likely already configured.)

      • 

    • Type of App: Select "Multi Tenant"

  • Click "Review + create", then "Create"

    • 

2. Configure Bot Channels

• Once the Azure Bot resource is deployed, navigate to it

  • 
• In the left menu, under "Settings", click "Channels"

• Click on the "Microsoft Teams" channel icon

• On the "Configure Microsoft Teams" page:

  • Under "Messaging", ensure "Microsoft Teams Commercial (most common)" is selected (or "Microsoft Teams Government" if applicable for your tenant)

  • Click "Apply"

  • The channel should now show as "Running" or "Healthy"

    • 

3. Configure Bot Messaging Endpoint & Link to App Registration

• In the Azure Bot resource's left menu, under "Settings", click "Configuration"

• Messaging endpoint: Enter https://_mycompany_.dropzone.app/interviewer/webhooks/ingest/msteams

• The Microsoft App ID field should display the App ID you entered during the bot's creation

• Click the "(Manage Password)" link next to the Microsoft App ID. This redirects you to the associated Azure AD App Registration

  • 

4. Azure AD App Registration - Create or Verify Client Secret

• You should now be on the Azure AD App Registration page (e.g. "Dropzone local development - do not break") that you identified or linked from the Bot Configuration

• In the App Registration's left menu, click "Certificates & secrets"

• Under the "Client secrets" tab:

  • You can use an existing, valid client secret if one is already configured for this App Registration and its value is known

  • If you need a new secret, or if the existing secret's value is unknown, click "+ New client secret"

    • Description: Provide a clear description (e.g. MSTeamsCommunicatorSecret or DropzoneBotSecret)

    • Expires: Select an appropriate expiration period

    • Click "Add"

      • 
  • CRITICAL: If you created a new secret, immediately copy its Value. This will be needed for the Dropzone configuration. It is only shown once

    • 

5. Azure AD App Registration - Configure API Permissions

• In the same App Registration's left menu, click "API permissions"

• Ensure the following Application permissions for Microsoft Graph are added and granted:

  • User.Read.All

  • Chat.Read.All

  • TeamsAppInstallation.ReadWriteForUser.All

  • Application.Read.All

  • AppCatalog.Read.All

• To add a permission:

  • Click "+ Add a permission"

  • Select "Microsoft Graph"

  • Select "Application permissions"

  • Search for and select each required permission, then click "Add permissions"

    • 
• Grant Admin Consent: After adding permissions, an Azure AD Administrator must click the "Grant admin consent for [Your Organization]" button

  • 
• Verify that the "Status" column for these permissions shows "Granted for [Your Organization]"

  • 

---

Teams Developer Portal & Admin Center Setup

1. Create/Configure Teams App in Developer Portal

• Navigate to the Teams Developer Portal (dev.teams.microsoft.com)

  • 
• Click "Apps" then "+ New app"

• Name: Enter a suitable name (e.g. Dropzone AI Interviewer)

• Basic Information:

  • Fill in Developer information (Name, Website, etc.)

  • Privacy policy and Terms of use URLs are required

  • Application (client) ID: Enter the same Azure AD App ID used for the bot and Microsoft Graph API (e.g. adc383dc-d84f-463d-ac62-153330eccb57)

    • 
• App features:

  • Click "Bot"

  • Select "Enter a bot ID"

  • Enter the same Azure AD App ID (Microsoft App ID for the bot) used previously

  • Select the desired scopes for the bot (e.g. "Personal", "Team", "Group Chat")

    • "Personal" is typically sufficient for interviewer functionality

    • 
• Save your changes in the Developer Portal

2. Publish in Teams Admin Center

• A Teams Administrator must perform these steps

• Navigate to the Microsoft Teams Admin Center (admin.teams.microsoft.com)

• Go to "Teams apps" > "Manage apps"

  • 
• Search for your app by the name you provided in the Developer Portal (e.g. Dropzone AI Interviewer). It may take a few minutes to appear after configuring it in the Developer Portal

  • 
• Select the app from the list

• Click "Publish" and confirm

  • 
• The app status will likely show as "Submitted", indicating it is pending administrator approval

  • 
• Once an administrator approves and publishes the app, it will become available. View its details again in "Manage apps"

• Locate and copy the "App ID" (note: NOT the label "External App ID"). This ID is the Teams App Catalog ID required for Dropzone

  • 
• Setup Policies: Ensure the app is available to users by checking and configuring your organization's Setup policies in the Teams Admin Center (Teams apps > Setup policies). Add the app to the relevant policy assigned to users or groups

---

Credentials to Provide to Dropzone

You will need the following information to configure the MS Teams Communicator in Dropzone:

1. MS Teams Bot App ID: The Application (client) ID from your Azure AD App Registration (e.g. adc383dc-d84f-463d-ac62-153330eccb57). This is entered into the "MS Teams Bot App ID" field in Dropzone

2. MS Teams Bot App Secret: The Value of the client secret generated in your Azure AD App Registration. This is entered into the "MS Teams Bot App Secret" field

3. MS Graph Tenant ID: The Directory (tenant) ID from your Azure AD App Registration's overview page. This is entered into the "MS Graph Tenant ID" field

4. MS Teams App Catalog ID: The "App ID" obtained from the Microsoft Teams Admin Center after publishing the app. This is entered into the "MS Teams App Catalog ID" field

In the Dropzone configuration UI, you will see a checkbox labeled "Use Bot Credentials for Graph API". This option is checked by default and is the recommended configuration for most users.

• When "Use Azure Bot Credentials for Graph API" is checked (Recommended):

  • The Bot App ID and Bot App Secret you provide will also be used for Microsoft Graph API calls

  • The fields required are: MS Teams Bot App ID, MS Teams Bot App Secret, MS Graph Tenant ID, and MS Teams App Catalog ID

• When "Use Azure Bot Credentials for Graph API" is unchecked (Advanced):

  • Two additional fields will appear: Dedicated MS Graph App ID and Dedicated MS Graph Client Secret

  • This advanced configuration allows you to use a separate Azure AD App Registration specifically for Microsoft Graph API calls, if your organization's policies or existing Azure setup requires it

  • Documentation for this specific advanced scenario (using a separate App ID/Secret for Graph) is not covered in this guide. Most users should keep the checkbox enabled

(Refer to your Dropzone UI for the specific field names when configuring the integration.)

Go to the interviewer page to change the default communicator.

---

Enable Microsoft Teams in Interviewer Configuration

After successfully configuring and saving the Microsoft Teams communicator credentials, you need to set it as the active interviewer for desired scenarios.

1. Navigate to Settings > Interviewer Configuration in Dropzone

2. On the Interviewer Configuration page, locate Microsoft Teams in the top-right dropdown menu and select it

3. Ensure the toggle switch next to Microsoft Teams is enabled (blue and toggled to the right)

   • 

This will activate Microsoft Teams as a communicator for initiating interviews based on your configured scenarios.

---

If you encounter any issues during this setup or when configuring the integration in Dropzone, please engage your Dropzone AI support representative.