Microsoft Teams - Collaboration

Created by David Esposito, Modified on Fri, 24 Jan at 8:33 AM by David Esposito

App Install

  1. Click the "Install Teams With OAuth" button under the "Installation Settings" section.

  2. Follow the Steps to complete the OAuth Flow to install the Teams integration

    • Check "Consent on behalf of your organization" before clicking "Accept"

Bot Install

  1. Navigate to Teams Admin Center → Teams Apps → Manage Apps.

  2. Managed Apps → Actions (Drop Down) → Upload New App.

  3. Download the App's Zip file from here and Upload it.
    (https://assets.ctfassets.net/a4bu6lgkooz7/1o95rUONse1VEq6QPITlk4/9d6d1663983376d979c11a9ee87f0ee4/Ampy-20250124.zip)

  4. Next Navigate to Setup Policies → Global (Org-wide default)

  5. Click on Add Apps → Select Global → Search by Name of App "Ampy".

  6. Select App and Add → Save.


Best Practices for Installing and Using Ampy in Teams


#1 Create a Dedicated Team for Amplifier Security

  1. Create a specific team, such as “Amplifier Security Team” to centralize all Ampy related activities. This ensures better organization and simplifies monitoring bot usage.
    1. Open Microsoft Teams on your desktop or web browser. In the left-hand sidebar, click on Teams.
    2. Click on plus ( + ) sign to Join or create a team.
    3. Select Create a team.
    4. Choose From scratch if displayed option to choose.
    5. Select Private to allow specific users in organization to join the team if necessary.
    6. Enter a Team Name (e.g., "Amplifier Security Team") and a brief description.
    7. Click Create.
  2. Add Channels To Dedicated Team 
    1. In the newly created team, click on the ellipsis (•••) next to the team name.
    2. Select Add channel.
    3. Enter a Channel Name (e.g., "Bot Notifications").
    4. Under Choose Channel Type, select Standard - Everyone on a Team has Access. ⚠️ Important: Private and shared channels do not support bot installation by Microsoft Teams
    5. Click Add.
    6. Repeat this step to create multiple channels if needed for different types of bot messages or audiences.

#2 Limit Installation to Necessary Teams and Channels

  1. Install Ampy only in teams and channels where its functionality is required. 
    1. Open Microsoft Teams and click the Teams icon on the left menu bar.
    2. Select the specific Team you want to add the app to. Click on the three dots (...) next to the Team name.
    3. From the dropdown menu, choose Manage team.
    4. In the Manage Team view, navigate to the Apps tab at the top menu.
    5. Click on Get more apps or use the search bar to search for the app you wish to install.
    6. Enter the app name (Ampy) and press Enter.
    7. Locate the app in the search results and click on App.
    8. Select Open.
    9. In the app installation dialog, select the Channel where you want to install the app. Use the search field to locate the desired channel, then select it.
    10. Click Go to finalize adding the app to the selected channel.

#3 Use Standard (Public) Channels Only

  • Ampy is compatible only with standard (public) channels.
  • Ensure channels intended for Ampy interactions are configured as standard, as private or shared channels are not supported by Microsoft Teams.

#4 Restrict Access to Ampy Managed Teams

  • Limit team membership to individuals who need to interact with Ampy. This ensures that only relevant users have access and reduces unnecessary usage.

#5 Use Clear and Descriptive Channel Names

  • Assign intuitive names to channels where Ampy operates to clearly indicate their purpose, such as, “QA Updates” for system updates , “Vulnerability Updates” for reports , etc.

#6 Restrict Unnecessary Interactions

  • Use Ampy's functionality to focus only on relevant actions and outputs to avoid unnecessary messages or distractions in the channels where it operates.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article