diff --git a/assets/images/integrations/microsoft-teams/3.png b/assets/images/integrations/microsoft-teams/3.png
new file mode 100644
index 000000000..d7a93f893
Binary files /dev/null and b/assets/images/integrations/microsoft-teams/3.png differ
diff --git a/assets/images/integrations/microsoft-teams/4.png b/assets/images/integrations/microsoft-teams/4.png
new file mode 100644
index 000000000..aceb5035f
Binary files /dev/null and b/assets/images/integrations/microsoft-teams/4.png differ
diff --git a/assets/images/integrations/microsoft-teams/connect-worflow.mp4 b/assets/images/integrations/microsoft-teams/connect-worflow.mp4
new file mode 100644
index 000000000..b06ef278d
Binary files /dev/null and b/assets/images/integrations/microsoft-teams/connect-worflow.mp4 differ
diff --git a/assets/images/integrations/microsoft-teams/uninstall-workflow.mp4 b/assets/images/integrations/microsoft-teams/uninstall-workflow.mp4
new file mode 100644
index 000000000..28e7956a8
Binary files /dev/null and b/assets/images/integrations/microsoft-teams/uninstall-workflow.mp4 differ
diff --git a/assets/images/microsoft-teams-integration/Capture13.webp b/assets/images/microsoft-teams-integration/Capture13.webp
deleted file mode 100644
index d7a65286f..000000000
Binary files a/assets/images/microsoft-teams-integration/Capture13.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/Capture15.webp b/assets/images/microsoft-teams-integration/Capture15.webp
deleted file mode 100644
index c8033dcbe..000000000
Binary files a/assets/images/microsoft-teams-integration/Capture15.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/Capture9-4.webp b/assets/images/microsoft-teams-integration/Capture9-4.webp
deleted file mode 100644
index fb98118de..000000000
Binary files a/assets/images/microsoft-teams-integration/Capture9-4.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-1.webp b/assets/images/microsoft-teams-integration/teams-1.webp
deleted file mode 100644
index 1a1acf0cb..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-1.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-10.webp b/assets/images/microsoft-teams-integration/teams-10.webp
deleted file mode 100644
index f87fd8b7f..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-10.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-11.webp b/assets/images/microsoft-teams-integration/teams-11.webp
deleted file mode 100644
index b1786bc83..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-11.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-12.webp b/assets/images/microsoft-teams-integration/teams-12.webp
deleted file mode 100644
index ef47a99b5..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-12.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-2.webp b/assets/images/microsoft-teams-integration/teams-2.webp
deleted file mode 100644
index 15493f862..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-2.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-3.webp b/assets/images/microsoft-teams-integration/teams-3.webp
deleted file mode 100644
index 3ea2a9b24..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-3.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-4.webp b/assets/images/microsoft-teams-integration/teams-4.webp
deleted file mode 100644
index cca2b284c..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-4.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-5.webp b/assets/images/microsoft-teams-integration/teams-5.webp
deleted file mode 100644
index dec1d6375..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-5.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-6.webp b/assets/images/microsoft-teams-integration/teams-6.webp
deleted file mode 100644
index 4040c99c7..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-6.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-7.webp b/assets/images/microsoft-teams-integration/teams-7.webp
deleted file mode 100644
index a6aa8a8a4..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-7.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-8.webp b/assets/images/microsoft-teams-integration/teams-8.webp
deleted file mode 100644
index 634633b4d..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-8.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/teams-9.webp b/assets/images/microsoft-teams-integration/teams-9.webp
deleted file mode 100644
index 43b834a96..000000000
Binary files a/assets/images/microsoft-teams-integration/teams-9.webp and /dev/null differ
diff --git a/assets/images/microsoft-teams-integration/w5-1.webp b/assets/images/microsoft-teams-integration/w5-1.webp
deleted file mode 100644
index ac2e08c9e..000000000
Binary files a/assets/images/microsoft-teams-integration/w5-1.webp and /dev/null differ
diff --git a/docs/microsoft-teams-integration.md b/docs/microsoft-teams-integration.md
index e23411909..a20be2a3d 100644
--- a/docs/microsoft-teams-integration.md
+++ b/docs/microsoft-teams-integration.md
@@ -1,7 +1,7 @@
---
id: microsoft-teams-integration
title: Microsoft Teams Integration
-hide_title: true
+hide_title: false
sidebar_label: Microsoft Teams
description: LambdaTest integration with Microsoft Teams allows you to push a bug directly to your specified Teams channel from LambdaTest platform. Share your UI observations and input with your teammates on any time, by capturing a screenshot in the middle of your test session through LambdaTest. You can annotate the screenshot & highlight your issue or input. The fields populated by you when marking as a bug through LambdaTest are displayed as information on the respective Teams channel for that testing instance.
keywords:
@@ -9,7 +9,6 @@ keywords:
- lambdatest integration
- bug reporting
- team communication
-
url: https://www.lambdatest.com/support/docs/microsoft-teams-integration/
site_name: LambdaTest
slug: microsoft-teams-integration/
@@ -38,127 +37,71 @@ slug: microsoft-teams-integration/
})
}}
>
+Microsoft Teams is a leading communication and collaboration platform that combines workplace chat, video conferencing, file storage, and app integration. Designed for teamwork, it enables seamless interaction and productivity within organizations, making it an ideal tool for managing projects and workflows.
-# Microsoft Teams Integration
-* * *
-
-Microsoft teams is a cloud-based group chat software meant to get everyone in your team on the same page. You can conduct online meetings, voice-calling, instant messaging, file sharing with your colleagues for faster and thorough collaboration.
-
-LambdaTest integration with Microsoft Teams allows you to push a bug directly to your specified Teams channel from LambdaTest platform. Share your UI observations and input with your teammates on any time, by capturing a screenshot in the middle of your test session through LambdaTest. You can annotate the screenshot & highlight your issue or input. The fields populated by you when marking as a bug through LambdaTest are displayed as information on the respective Teams channel for that testing instance.
-
-## How To Integrate Microsoft Teams With Your LambdaTest Account?
-
-* * *
-
-**Step 1:** Login to your LambdaTest account. You would need to have Admin or User level access to see and install integrations.
-
-**Step 2:** Select **'Integration'** from the left navigation menu bar. This will guide you to a screen where you will find a list of 3rd party applications, available to integrate with your LambdaTest account.
-
-**Step 3:** Click on **'Add'** under the block that says 'Microsoft Teams'.
-
-
-
-**Step 4:** You will be asked to provide the Webhook URL of your Microsoft Teams instance for authentication purpose. This would help LambdaTest to connect with Microsoft Team API for your account.
-
-
-
-**Step 5:** Go to your Microsoft Teams instance. Visit the team from left navigation menu and hit the menu button for any channel & select **Connectors**.
-
-
-
-**Step 6:** Hit the **'Configure'** button for **Incoming Webhooks**.
-
-
-
-**Step 7:** Enter a text as you see fit for generating a webhook by clicking the **Create** button.
-
-
-**Step 8:** Copy the generated webhook for authentication purpose on LambdaTest.
-
-
-
-**Step 9:** Paste the Webhook URL into LambdaTest authentication field for integrating LambdaTest with Microsoft Teams & hit **install**.
+The Microsoft Teams integration with LambdaTest enables seamless collaboration and real-time updates on your test automation workflows. With this integration, you can:
+- Receive instant notifications on test status and results directly in your Microsoft Teams channels.
+- Collaborate efficiently by sharing test execution logs and reports with your team.
+- Stay informed about your test runs without leaving your Teams environment.
-
+> **NOTE :** You must have either any **Bug Tracker** or **Project Management** tool integrated before proceeding with Teams integration.
-That's it! Go to Integrations again and you will be able to notice a **green tick** indicating that Microsoft Teams is successfully **installed** with your LambdaTest account.
+## Generate your Webhook URL
-
+**Step 1:** Visit your Teams account -> click on the **+** button and create a channel in which you want to recieve all your notifications.
-## How To Log Your First Bug Through Microsoft Teams Integration?
+**Step 2:** Click on the **...** button in the top right section of your channel and select workflows.
-* * *
+**Step 3:** Provide the description and create a new workflow by selecting the channels
-**Step 1:** Go for any of the test from the left navigation menu. For demo, we will be taking "**Real Time Test**" option.
+
-**Step 2:** Present a URL of the web-app you need to test in the dialog box. After that, select any configuration for browser and operating system of your choice & hit '**Start**'.
+**Step 4:** Copy your generated workflow, you will need it in the next step.
-
+
-**Step 3:** After the VM is launched and operable. You can perform testing on your web-app for finding bugs. If a bug gets revealed, then you need to click on the **Bug icon** from the left panel for capturing a screenshot of the same. We have highlighted that option with yellow in the below image.
+## Integrate Teams with your LambdaTest Account
-
+**Step 1:** Login to your LambdaTest account. You should have Admin or User level access to see and install integrations.
-**Step 4:** After a screenshot is captured, you can annotate any issue or a task with an **in-built image editor**. Once you are done highlighting the bug, click on the button that says **"Mark as Bug"**.
+**Step 2:** Click on Settings -> Integrations -> Communication.
-
+**Step 3:** Click on **Connect** button of `Microsoft Teams` block.
-**Step 5:** After clicking on **"Mark as Bug"** button a form would open up. Fill the fields as per your requirement.
->* You can select the **Issue type**.
-* You can set the **priority** of the bug.
-* You can assign the bug to a colleague by populating the field '**Assignee**'.
-* You can post a relevant **summary** for keeping your bug inventory well organized.
-* You also get to post a **description** to help relate the cause of the issue or the task.
+**Step 4:** Now, provide your Microsoft Teams Workflow URL to establish integration with LambdaTest and click on **install** button.
-At the bottom of the form you will find a check button **"Send to Microsoft Teams"**. By default, it would be **checked** if you have already integrated LambdaTest with Microsoft Teams. This button when checked, will push the screenshot directly to your workspace after you click on **"Create Bug"**. You can **uncheck** the button if you do not wish to share a particular screenshot with your team.
+
-
+## Lodge your First Bug
-**Note:** After you click on **"Create Bug"**, you will be able to observe it being successfully marked through a single click effort. You will get **prompt messages** on top of your Virtual Machine indicating the progress of bug logging. After few seconds you will be notified with a prompt message "**Bug successfully marked**" indicating that the screenshot has been pushed to your Microsoft Teams workspace.
+> Note: If you are using Rocket.Chat for the first time, then make sure to create a project for yourself. It is a pre-requisite in order to push screenshots from your LambdaTest account.
-
+**Step 1:** Start with any type of testing, for the demo purpose we are going with the **Real Time Testing**.
-Login to your workspace and you will be able to notice the logged issue right away! All the data you provided through LambdaTest would already be presented in it. LambdaTest automatically includes test environment details and related screenshots in the screenshot as attachments.
+**Step 2:** Enter your Project URL and configure for browser and operating system of your choice & hit **Start**.
-
+**Step 3:** After the VM is launched and operable. You can perform testing on your web-app for finding bugs. If a bug gets revealed, then you need to click on the Bug icon from the left panel for capturing a screenshot of the same.
->**Note:** At the bottom of your logged bug in Microsoft Teams, you will notice the following two buttons.
-* Goto Generated Ticket: Instantly routes you to LambdaTest platform's Issue Tracker, where you can find all the details related to that specific bug.
->
->* Goto Attached Screenshot: Instantly routes you in a new browser tab for a full-screen view of the bug.
+**Step 4:** After clicking on "**Mark as Bug**" button your respective **Bug Tracker** tool or **Project Management** tool specific form would open up. Fill the fields as per your requirement.
-## How To Remove Microsoft Teams Integration?
+> Make sure you mark on the check at the last of the form to send the notification on your integrated Teams channel.
-* * *
+**Step 5:** Click on **Mark as Bug** button. Now go to your dashboard and check a ticket will be created for the same.
->You can work with one integration at a time. So if you would want to integrate to a similar 3rd party application, then you would have to **remove** your current integration. Here is how you can do that.
+**Step 6:** Go to your Teams channel and you can check a notification is sent for the same.
-**Step 1:** Login to your LambdaTest account.
+## Uninstall Microsoft Teams Integration
-**Step 2:** Select **'Integrations'** from the left-navigation menu. This will guide you to a screen where you will find 3rd party applications, available to integrate with your LambdaTest account.
+**Step 1:** Login to your LambdaTest account. You should have Admin or User level access to see and install integrations.
-**Step 3:** Click on **'REMOVE'**. You can find the remove button right under the **'Microsoft Teams'** block which would be highlighted with a green tick.
+**Step 2:** Click on Settings -> Integrations -> Communication.
-
+**Step 3:** Click on the **Remove** button.
->That was all you need to know for LambdaTest + Microsoft Teams Integration. Increase your productivity with our integrations. If you still have any questions for us, please feel free to let us know. Our experts are always window.openLTChatWidget()}>**available on chat** to help you out with any roadblock regarding our product. Happy testing! 🙂
+
-
\ No newline at end of file
+> That was all you need to know for LambdaTest + Teams Integration. Increase your productivity multifold with our integrations. If you still have any questions for us, please feel free to let us know. Our experts are always window.openLTChatWidget()}>**available on chat** to help you out with any roadblock regarding our product. Happy testing!
\ No newline at end of file