Skip to content

Commit 6ce2c5f

Browse files
authored
Merge pull request #183050 from v-ddennis/12132021-image-updates-azure-docs-pr
Rebranded images from Azure Sentinel to Microsoft Sentinel
2 parents cf66f75 + c9c5e3b commit 6ce2c5f

36 files changed

+3
-4
lines changed

articles/sentinel/collaborate-in-microsoft-teams.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ In order to create teams from Microsoft Sentinel:
3434

3535
- The user creating the team must have Incident write permissions in Microsoft Sentinel. For example, the [Microsoft Sentinel Responder](../role-based-access-control/built-in-roles.md#microsoft-sentinel-responder) role is an ideal, minimum role for this privilege.
3636

37-
- The user creating the team must also have permissions to create teams in Microsoft teams.
37+
- The user creating the team must also have permissions to create teams in Microsoft Teams.
3838

3939
- Any Microsoft Sentinel user, including users with the [Reader](../role-based-access-control/built-in-roles.md#microsoft-sentinel-reader), [Responder](../role-based-access-control/built-in-roles.md#microsoft-sentinel-responder), or [Contributor](../role-based-access-control/built-in-roles.md#microsoft-sentinel-contributor) roles, can gain access to the created team by requesting access.
4040

@@ -71,7 +71,7 @@ Investigate together with an *incident team* by integrating Microsoft Teams dire
7171

7272
1. Select your **Teams integration** link to switch into Microsoft Teams, where all of the data about your incident is listed on the **Incident page** tab.
7373

74-
[ ![Incident page in Microsoft Teams.](media/collaborate-in-microsoft-teams/incident-in-teams.jpg) ](media/collaborate-in-microsoft-teams/incident-in-teams.jpg#lightbox)
74+
[ ![Incident page in Microsoft Teams.](media/collaborate-in-microsoft-teams/incident-in-teams.png) ](media/collaborate-in-microsoft-teams/incident-in-teams.png#lightbox)
7575

7676
Continue the conversation about the investigation in Teams for as long as needed. You have the full incident details directly in teams.
7777

43.8 KB
Loading
31.6 KB
Loading
60.5 KB
Loading
-26 KB
Loading
Binary file not shown.
1.28 MB
Loading
42 KB
Loading
1.02 KB
Loading
4.44 KB
Loading

0 commit comments

Comments
 (0)