Skip to content

Commit 175a3ab

Browse files
committed
Edit to Prerequisites in Sentinel for MSSP
1 parent 187639d commit 175a3ab

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,18 +19,18 @@ ms.author: yelevin
1919
---
2020
# Work with multiple tenants in Azure Sentinel
2121

22-
If youre a managed security service provider (MSSP) and youre 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 customers 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 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.
2323

2424
## Prerequisites
2525
- [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, in the Azure portal, select **Subscriptions** followed by **Resource providers** and then search for `Microsoft.Security.Insights` and select **Register**.
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**.
2727
![Check resource providers](media/multiple-tenants-service-providers/check-resource-provider.png)
2828
## How to access Azure Sentinel from other tenants
29-
1. Under **Directory + subscription**, select the delegated directories, and the subscriptions where your customers Azure Sentinel workspaces are located.
29+
1. Under **Directory + subscription**, select the delegated directories, and the subscriptions where your customer's Azure Sentinel workspaces are located.
3030

3131
![Generate security incidents](media/multiple-tenants-service-providers/directory-subscription.png)
3232

33-
1. Open Azure Sentinel. You will see all the workspaces in the selected subscriptions, and youll be able to work with them seamlessly, like any workspace in your own tenant.
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.
3434

3535
> [!NOTE]
3636
> 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.

0 commit comments

Comments
 (0)