Azure Lighthouse Pulling subscription, but not Sentinel Workspace

Sam C 46 Reputation points
2020-11-13T20:05:09.247+00:00

We're trying out lighthouse + sentinel as a way to get a first look at a threat landscape of an adjacent tenant in the organization, and we've got it all set up to the point where I can see the subscription of the other tenant that has the sentinel workspace, but I can't get the sentinel workspace to populate. Any ideas? The two sentinel instances are in different areas (both US) and we can't seem to find the security group that was supposed to be created on the Customer side. Could either of those be causing this? Thanks!

Azure Lighthouse
Azure Lighthouse
An Azure service that provides secure managed services and access control for partners and customers.
71 questions
Microsoft Sentinel
Microsoft Sentinel
A scalable, cloud-native solution for security information event management and security orchestration automated response. Previously known as Azure Sentinel.
1,041 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Deo Jain, Keshav 6 Reputation points
    2021-02-04T02:08:44.15+00:00

    Ideally it should come. We are able to see the Sentinel from two different subscriptions and used light house. I dont think it has anything to do with Location.

    However, check this new feature

    https://video2.skills-academy.com/en-us/azure/sentinel/multiple-workspace-view

    1 person found this answer helpful.
    0 comments No comments

  2. Clive Watson 5,951 Reputation points MVP
    2021-11-08T13:59:32.023+00:00

    That drop-down will show the Subscription, not the workspace. When you open Microsoft Sentinel, you should see the workspace listed (as per the link above)

    1 person found this answer helpful.

  3. Andrew Blumhardt 9,831 Reputation points Microsoft Employee
    2021-11-29T05:03:42.09+00:00

    You cannot activate connectors using Lighthouse accounts. You need a local tenant account.

    “You will not be able to deploy connectors in Microsoft 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.”

    https://video2.skills-academy.com/en-us/azure/sentinel/multiple-tenants-service-providers

    0 comments No comments