Skip to content

Commit b051eaa

Browse files
committed
adding image
1 parent 18b7419 commit b051eaa

File tree

2 files changed

+2
-0
lines changed

2 files changed

+2
-0
lines changed
121 KB
Loading

articles/sentinel/overview.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,6 +130,8 @@ For the sake of the changes described in this section, new Microsoft Sentinel cu
130130

131131
Starting **July 1, 2025**, such new customers who are not Azure Lighthouse-delegated users, and who have the permissions of a subscription [Owner](/azure/role-based-access-control/built-in-roles#owner) or a [User access administrator](/azure/role-based-access-control/built-in-roles#user-access-administrator), have their workspaces automatically onboarded to the Defender portal together with onboarding to Microsoft Sentinel. Users of such workspaces, who also aren't Azure Lighthouse-delegated users, see links in Microsoft Sentinel in the Azure portal that redirect them to the Defender portal. Such users use Microsoft Sentinel in the Defender portal only.
132132

133+
For example:
134+
133135
New customers who don't have relevant permissions aren't automatically onboarded to the Defender portal, but they do still see redirection links in the Azure portal, together with prompts to have a user with relevant permissions manually onboard the workspace to the Defender portal.
134136

135137
The following table summarizes these experience:

0 commit comments

Comments
 (0)