Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit b37e924

Browse files
committedSep 29, 2020
Corrections per user issue #63348
1 parent 0c01b88 commit b37e924

File tree

2 files changed

+20
-12
lines changed

2 files changed

+20
-12
lines changed
 
Loading

‎articles/sentinel/multiple-tenants-service-providers.md

Lines changed: 20 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Work with multiple tenants to Azure Sentinel for MSSP service providers| Microsoft Docs
2+
title: Work with multiple tenants to Azure Sentinel for MSSP service providers | Microsoft Docs
33
description: How to work with multiple tenants to Azure Sentinel for MSSP service providers.
44
services: sentinel
55
documentationcenter: na
@@ -13,33 +13,41 @@ ms.devlang: na
1313
ms.topic: conceptual
1414
ms.tgt_pltfrm: na
1515
ms.workload: na
16-
ms.date: 09/23/2019
16+
ms.date: 09/29/2020
1717
ms.author: yelevin
1818

1919
---
20-
# Work with multiple tenants in Azure Sentinel
20+
# Manage multiple tenants in Azure Sentinel as an MSSP
2121

22-
If you're a managed security service provider (MSSP) and you're using [Azure Lighthouse](../lighthouse/overview.md) to manage your customers' security operations centers (SOC), you will be able to manage your customers' Azure Sentinel resources without connecting directly to the customer's tenant, from your own Azure tenant.
22+
If you're a managed security service provider (MSSP) and you're using [Azure Lighthouse](../lighthouse/overview.md) to offer security operations center (SOC) services to your customers, you can manage your customers' Azure Sentinel resources directly from your own Azure tenant, without having to connect to the customer's tenant.
2323

2424
## Prerequisites
25+
2526
- [Onboard Azure Lighthouse](../lighthouse/how-to/onboard-customer.md)
26-
- For this to work properly, your tenant must be registered to the Azure Sentinel Resource Provider on at least one subscription. If you have a registered Azure Sentinel in your tenant, you are ready to get started. If not, select **Subscriptions** from the Azure portal, followed by **Resource providers**. Then, from the **SOC - Resource providers** screen, search for and select `Microsoft.OperationalInsights` and `Microsoft.SecurityInsights`, and select **Register**.
27-
![Check resource providers](media/multiple-tenants-service-providers/check-resource-provider.png)
28-
## How to access Azure Sentinel from other tenants
29-
1. Under **Directory + subscription**, select the delegated directories, and the subscriptions where your customer's Azure Sentinel workspaces are located.
3027

31-
![Generate security incidents](media/multiple-tenants-service-providers/directory-subscription.png)
28+
- For this to work properly, your tenant (the MSSP tenant) must have the Azure Sentinel resource providers registered on at least one subscription. In addition, each of your customers' tenants must have the resource providers registered. If you and your customers have registered Azure Sentinel in your tenant, you are ready to get started. To verify registration, take the following steps:
3229

33-
1. Open Azure Sentinel. You will see all the workspaces in the selected subscriptions, and you'll be able to work with them seamlessly, like any workspace in your own tenant.
30+
1. Select **Subscriptions** from the Azure portal, and then select a relevant subscription from the menu.
3431

35-
> [!NOTE]
36-
> You will not be able to deploy connectors in Azure Sentinel from within a managed workspace. To deploy a connector, you must directly sign into the tenant on which you want to deploy a connector and authenticate there with the required permissions.
32+
1. From the navigation menu on the subscription screen, under **Settings**, select **Resource providers**.
33+
34+
1. From the ***subscription name* | Resource providers** screen, search for and select *Microsoft.OperationalInsights* and *Microsoft.SecurityInsights*, and check the **Status** column. If the provider's status is *NotRegistered*, select **Register**.
35+
36+
:::image type="content" source="media/multiple-tenants-service-providers/check-resource-provider.png" alt-text="Check resource providers":::
3737

38+
## How to access Azure Sentinel from other tenants
39+
40+
1. Under **Directory + subscription**, select the delegated directories, and the subscriptions where your customer's Azure Sentinel workspaces are located.
3841

42+
:::image type="content" source="media/multiple-tenants-service-providers/directory-subscription.png" alt-text="Choose tenants and subscriptions":::
3943

44+
1. Open Azure Sentinel. You will see all the workspaces in the selected subscriptions, and you'll be able to work with them seamlessly, like any workspace in your own tenant.
4045

46+
> [!NOTE]
47+
> You will not be able to deploy connectors in Azure Sentinel from within a managed workspace. To deploy a connector, you must directly sign into the tenant on which you want to deploy a connector, and authenticate there with the required permissions.
4148
4249
## Next steps
50+
4351
In this document, you learned how to manage multiple Azure Sentinel tenants seamlessly. To learn more about Azure Sentinel, see the following articles:
4452
- Learn how to [get visibility into your data, and potential threats](quickstart-get-visibility.md).
4553
- Get started [detecting threats with Azure Sentinel](tutorial-detect-threats-built-in.md).

0 commit comments

Comments
 (0)
Please sign in to comment.