AI agents investigate every alert, add context, and prepare cases for response, on a full-stack SecOps platform that captures and correlates all your security data.
Cloud-based SIEM platform providing visibility across all your data sources
Every alert investigated, with a verdict and the evidence behind it
Manage your external footprint, publicly available data, and Dark Web leaks
Log management and threat detection across any of your log sources
Get ultimate assurance that your environment is free from threat actors
Fully featured distrubuted NDR for on-premises and public cloud environments
A SecOps platform purpose-built for industrial and OT environments
Integrated endpoint agent providing deep visibility, response and forensics
Deploy honeypots and honeytokens and stay ahead of threat actors
24x7 security operations from our Australian SOC. AI investigates every alert, and experienced analysts validate findings and contain threats around the clock.
Eyes-on-glass SOC and continuous threat hunting
24x7 managed detection and response across endpoint, network, cloud, identity, and log sources
AI investigations and 24x7 MDR on the Microsoft Sentinel you already own
Quickly recover from cyber attacks and breaches
Security Score, risk register, CISO program and reporting from live data
Fake sites, apps and accounts, leaked code and dark web exposure, taken down for you
AI agents map, watch and test your attack surface around the clock
ThreatDefence is the only SecOps as a Service company providing broad coverage across your entire technology stack with evidence-based security.
We provide security teams with full-stack SecOps infrastructure – you get deep visibility from day one, gain control over your security data, and get access to a comprehensive set of ready-to-use tools, detections, workflows, playbooks and scenarios.
24x7 SOC, Continuous Monitoring, Threat Containment and Incident Response
Expert hunters and AI agents find attacker activity your alerts missed
Leverage our Cyber Range to train defenders based on real-world scenarios and simulations
OT and industrial cyber security services for critical infrastructure
Monitoring, evidence and a 24×7 SOC in one platform
Compliance monitoring, evidence and board reporting
Privacy Act reform impacts, obligations, and practical security considerations
Monitoring and compliance support for critical infrastructure environments
A practical guide to securing critical infrastructure with continuous monitoring
A practical buyer’s guide for schools evaluating SIEM and SOC services
A practical guide to selecting the right SIEM and SOC service for local government
Articles on security operations, AI and compliance
Events, awards and company news
Read what our customers say about us
Solution briefs and datasheets
How we keep your data secure
Technical support and knowledge base
Guides, case studies, and advisories in one place
How AI agents investigate alerts and run security operations
Free ebook: a practical guide to adopting an AI SOC platform
A practical guide to incident response and digital forensics
Where SOAR playbooks fit and where AI agents take over
Free ebook: modern security operations with Microsoft Sentinel
How the framework is structured and what changes from the Essential Eight
How an attack unfolds stage by stage and how to detect each one
November 21, 2026
November 20, 2026
We provide end-to-end SecOps solutions for Managed Security Service Providers (MSSPs), Managed Service Providers (MSPs), and Value-Added Resellers (VARs).
Find out how you can become a ThreatDefence partner.
Protect your entire technology stack and build your SecOps on your own pace
White-labeled AI SOC for every client tenant, co-managed with our SOC team
Launch your SOC business without any upfront investment
Embed security operations, threat intelligence and exposure data in your product
Sovereign SOC for Australian MSPs and MSSPs, with onshore analysts and client data
Set the rules for closing alerts automatically, with evidence checks and review
How MSPs deliver branded security monitoring with a SOC partner
ThreatDefence was an official partner of the Cyber Resilience Summit NSW, 29 October 2026 at Hilton Sydney.
Our team was back at BSides Canberra, and our cyber quiz was a hit again.
Two days in Perth with our partner Ever Nimble, on security operations and cyber resilience.
Sponsors of the AUSCERT Cyber Security Conference on the Gold Coast.
Sponsors of the Gartner Security & Risk Management Summit in March.
Sponsors of the Cyber Security for Critical Assets Summit in Perth, February 2026.
Expert conversations with speakers and attendees at CyberCon Melbourne 2025.
Microsoft Sentinel gives MSSPs a way to deliver managed security across multiple client environments, combining Microsoft security signals with logs from the wider technology estate.
The usual architecture keeps a Sentinel workspace in each client’s Microsoft Entra tenant, with centralized management across those environments.
Microsoft Sentinel supports an MSSP model through separate client workspaces, delegated Azure management, and multitenant operations in the Microsoft Defender portal. Central management does not require collecting every client’s raw logs into a shared provider workspace.
Each component has a different job:
The MSSP builds the service around these capabilities: configuring sources, maintaining detections, investigating activity, coordinating response, and reporting the results.
For example, a suspicious mailbox rule may need evidence from Entra sign-ins, Microsoft 365 audit events, and the user’s endpoint. The client also needs someone to assess the evidence and take the agreed action. A central incident queue helps organize that work; the operating model determines how it gets done.
For most MSSPs, start with at least one Microsoft Sentinel workspace in each client’s Entra tenant. Microsoft recommends this approach because important native service-to-service connectors operate within their own tenant boundary.
A CSP billing relationship does not replace delegated access. Decide separately who pays for Azure and who can manage the resources.
Provider-hosted collection needs particular care. Microsoft identifies Defender XDR as an example of a source that cannot connect across tenants in this model. That makes a single provider workspace unsuitable for many Microsoft-focused MSSP services.
Create additional workspaces where region, tenant boundaries, or operational separation require them. Different retention periods alone may be handled through table-level settings.
Record workspace IDs, subscription IDs, billing owners, deployed content versions, and provider-hosted dependencies in a client service inventory. Keeping this information current makes troubleshooting, access reviews, and eventual handover much easier.
Azure Lighthouse, GDAP, and Entra B2B solve different access problems. Choose the access path for the task an analyst or engineer must perform.
Microsoft’s multitenant setup guidance distinguishes GDAP access to Defender data from access to Sentinel data. Its newer governance documentation also describes assigning remote tenant groups Sentinel permissions. Validate the chosen path against the actual portal, API, and response operations your service uses.
Azure Lighthouse and Microsoft 365 Lighthouse are separate products. A working Microsoft 365 administration relationship does not establish all the Azure and Sentinel permissions your SOC needs.
Use security groups for analysts, hunters, and engineers, with delegation at the subscription or resource-group scope the service requires. Lighthouse supports specific built-in roles; it does not support Owner, custom roles, or roles containing DataActions. Its User Access Administrator exception is limited to specified managed-identity role assignments.
A practical starting pattern is:
Reader, Responder, and Contributor provide progressively broader Sentinel permissions. Incident management rights do not automatically authorize endpoint isolation or directory changes.
Use eligible Lighthouse authorizations for temporary privileged work where appropriate. They require applicable PIM licensing and cannot be activated by service principals, so unattended deployments need a separately controlled permission model.
Protect the provider tenant accordingly. Client Conditional Access policies do not apply to users accessing resources through Lighthouse; the managing tenant’s policies apply to that access path.
Build new operating procedures around the Defender portal. Microsoft states that Sentinel will no longer be supported in the Azure portal after March 31, 2027.
Defender multitenant management provides a combined view across authorized client tenants. Microsoft currently documents a limit of 100 target tenants, so larger providers need an operating design that accounts for that boundary.
Where a client has multiple workspaces, distinguish their roles:
When integrated with Defender XDR, receives synchronized Defender XDR incidents and alerts and participates in the combined correlation experience.
Keep separate incident correlation. They can ingest supported Defender table data when configured, but do not inherit primary-workspace incident synchronization.
Document the primary workspace and test any change to it. Detection rules, playbooks, and ticket integrations may depend on the previous configuration.
Before accepting a client into the shared view, confirm that analysts can open its environment directly and complete the required tasks. Test MFA, role assignments, and permitted response actions. A client missing from the dashboard should trigger an access or health check.
Start with what the service must detect and investigate. Then identify the sources, rules, and response capabilities needed to support it.
A useful coverage matrix connects attack scenarios to evidence and operational tests:
Treat this as a planning framework and adapt it to each client’s estate and licenses.
For every source, record which accounts, devices, systems, and event categories it covers. Define expected latency and what should happen if collection stops. A connector showing recent activity does not establish that the whole environment is represented.
Use a shared detection baseline with client-specific settings. An education customer, a law firm, and an industrial operator may share core identity detections while needing different thresholds, exclusions, critical assets, and response approvals.
Track gaps alongside incidents. Missing audit events, failing rules, and unavailable response permissions belong in the service improvement plan, with an owner and a next action.
Manual rule changes become difficult to control as the client base grows. Content as code gives the MSSP a reviewed source for shared detections and a repeatable way to release them.
Keep common analytics rules, parsers, workbooks, and automation separate from client configuration. Parameterize thresholds, enabled sources, exclusions, and deployment scope. Record dependencies so a rule is deployed only where the required tables and supporting content exist.
Distribution profiles support several Sentinel content types, but automation rules that trigger playbooks cannot be distributed through that feature. Check outcomes by client and item when a publish is partially successful.
Validate templates and queries, test against representative data, and release to a small client group before expanding. Check whether the deployed rule runs successfully and produces useful investigations.
Record each client’s intended version, deployed version, exceptions, and failures. Use stable resource identifiers so an update changes the existing item.
Capture emergency portal edits back into source control before the next deployment. Otherwise, a later release can overwrite them. Handle retirement explicitly: deleting a repository file does not delete its deployed Sentinel resource.
Cross-client hunting helps answer whether a newly identified indicator or behavior affects other managed environments.
Two query patterns matter:
Runs a query independently in selected tenants and combines the results.
Uses workspace() references to query named workspaces, including supported cross-tenant access through Lighthouse.
workspace()
For example, this query summarizes non-success sign-ins in two client workspaces:
union (workspace("<acme-corp-workspace-id>").SigninLogs | where TimeGenerated >= ago(24h) | extend Client = "acme-corp"), (workspace("<acme-health-workspace-id>").SigninLogs | where TimeGenerated >= ago(24h) | extend Client = "acme-health") | where ResultType != "0" | summarize NonSuccessSignIns = count(), ApproxAccounts = dcount(UserPrincipalName) by Client, IPAddress | order by NonSuccessSignIns desc
Replace the placeholders with workspace identifiers and run with an authorized identity. The example requires SigninLogs in both workspaces. Non-success results need interpretation; they are not automatically attacks.
SigninLogs
Keep the client identity attached to every result. Similar private IP addresses, usernames, or hostnames across customers do not establish a shared incident.
Scheduled cross-workspace analytics rules have different constraints from interactive hunting: they support up to 20 workspaces per query, with five or fewer recommended for performance. Sentinel must be enabled on each referenced workspace, and alerts are created only in the rule’s home workspace.
For a common detection that should operate independently for each customer, deploying the rule into each eligible client workspace is usually easier to govern.
An MSSP needs to understand both Azure consumption and the work required to deliver the service.
Track costs at the agreed workspace, resource, subscription, or billing scope. Separate Microsoft charges from SOC fees, engineering work, and shared platform allocations.
Sentinel’s analytics tier offers pay-as-you-go and commitment pricing. Other capabilities have their own meters, so ingestion volume alone does not describe the full bill.
Use the Usage table to investigate consumption trends and Azure Cost Management and billing records to reconcile charges. A cross-workspace Usage query can help identify which client and table contributed to growth, but its output is not an invoice.
Usage
Review spending alongside coverage. An increase may come from a newly monitored system, a connector error, repeated events, or duplicate collection. Decide what changed before filtering data.
Lighthouse delegation does not automatically pool unrelated clients into one commitment tier. Size commitments against their actual billing scope, and account for the 31-day restriction on reducing a commitment tier.
Common arrangements include a service fee with Azure billed separately, a bundled CSP service, or per-user or per-device pricing with defined consumption assumptions.
Whichever model you use, specify covered technologies, monitoring hours, investigation depth, response actions, and responsibility for material cost changes. Measure analyst effort as well as gigabytes: a small, complex client can require substantial operational work.
Assign a named owner to spend alerts and cost reviews. For detailed filtering, routing, retention, and pricing decisions, see Microsoft Sentinel Cost Optimization.
Start with a pilot client and prove the complete service before making the deployment pattern standard.
Agree the tenants, systems, sources, coverage hours, retention, response authority, and escalation contacts. Identify who approves source consent, spending changes, and containment.
Record the security scenarios the service must cover and any known gaps.
Confirm tenant, subscription, region, billing arrangement, and required workspaces. Establish the intended primary workspace where Defender XDR integration applies.
Verify Microsoft.SecurityInsights and Microsoft.OperationalInsights registration in the client subscriptions and at least one subscription in the provider tenant, as required by Microsoft’s MSSP guidance.
Microsoft.SecurityInsights
Microsoft.OperationalInsights
Deploy Lighthouse at the agreed scope and configure the supported Defender and directory access paths.
Test the production analyst and service identities. Connector setup can require additional tenant-side permissions or consent; Lighthouse alone is not sufficient for every connector.
Confirm actual events, entity identifiers, latency, and source scope. Compare the observed data with the agreed coverage matrix.
Test collection failures as well as successful collection so the team knows how a silent source will be detected and assigned.
Apply approved content and client parameters. Validate dependencies, rule health, alert quality, playbook identities, and downstream actions.
Record the deployed version and any exceptions.
Map incidents to the correct ticket board, escalation contacts, client portal, and reporting schedule.
Use tenant, workspace, and incident identifiers together when synchronizing records. Display names and incident numbers alone are insufficient across clients.
Generate an agreed event on a test asset. Follow it through detection, investigation, ticket synchronization, escalation, and an authorized response.
Verify tenant and asset identity at every step.
Confirm what is covered, which gaps remain, and who owns them. Capture ingestion, cost, and alert baselines.
Schedule an early service review to assess noise, investigation effort, source health, and actual costs. Use what you learn to improve the shared onboarding pattern.
A multitenant console reduces navigation between environments. Delivering 24x7 coverage still requires qualified people, working response paths, and reliable handovers.
Define monitoring, investigation, approval, and containment availability separately. State what happens when the client’s primary contact cannot be reached and who can authorize urgent action.
AI can assist with evidence gathering, triage, and investigation. Introduce it gradually: begin with investigation support, review findings, and authorize specific actions as the workflow proves reliable. Keep client context, access, evidence, and approvals attached to each case.
For implementation detail, see Agentic SOC on Microsoft Sentinel. For service options, see Managed SOC for MSPs and MSSPs.
Client-owned workspaces make continuity easier, but the service may still depend on provider credentials, central rules, playbooks, repositories, or ticket integrations.
Use the service inventory to plan the transition:
Coordinate access removal with validation of cross-tenant rules. Their continued operation can depend on the creating identity’s permissions in other subscriptions or tenants.
Agree retention and disposal for provider-held case records and exports. Removing delegation does not remove copies already created outside the workspace.
ThreatDefence helps MSPs and MSSPs build managed security services around Microsoft Sentinel and the wider client environment.
Keep client Sentinel workspaces in place and add an AI SOC platform with 24x7 SOC support. AI agents gather evidence and investigate activity across connected Microsoft and non-Microsoft sources, while analysts validate findings and coordinate response within each client’s approved limits.
Your team can work with ThreatDefence through shared cases, defined escalation paths, and client-specific procedures. White-label options bring the portal, reports, and notifications under your brand, with ticket synchronization for ConnectWise, Autotask, HaloPSA, or ServiceNow.
Extend coverage where the client’s security program needs it, including attack surface management, brand protection, and network detection. Choose fully managed, after-hours, or co-managed support according to your delivery model.
Start with a Microsoft Sentinel cost and coverage review to identify missing evidence, detection gaps, and unnecessary consumption. The review provides a practical basis for improving the service before expanding it across more clients.
event.action:"New-InboxRule" AND forward*
Explore AI SOC for MSSPs Request a Sentinel cost and coverage review
See how ThreatDefence supports Microsoft Sentinel operations across multiple clients, from AI investigation and shared cases to branded reporting and 24x7 SOC delivery.
CountryAustraliaUnited StatesNew ZealandUnited KingdomCanadaSingaporeOtherI'm an MSP, MSSP, or reseller
Δ
Yes. Sentinel supports client workspaces across tenants, delegated Azure management, cross-workspace queries, and operations through Defender multitenant management. The MSSP still needs a repeatable approach to detection content, access, response, cost reporting, and service delivery.
Usually, at least one workspace per client Entra tenant. This supports native connector boundaries and separate configuration. Some clients need additional workspaces for geography or operational requirements. A provider-hosted workspace requires source-by-source validation.
No. Lighthouse delegates supported Azure resource operations. B2B, GDAP, and tenant governance relationships address other access requirements. Your service may need more than one method to support Azure management, Defender investigations, connector consent, and response.
Microsoft’s Defender multitenant setup guidance states that GDAP does not provide Sentinel data access. It supports eligible Defender workloads and administration. Microsoft separately documents tenant governance relationships for Sentinel permissions. Validate the access method for each operation.
Not necessarily. Sentinel can collect data from supported Microsoft and third-party sources. Whether the SOC can investigate and respond through the existing EDR depends on connector support, available telemetry, licensing, API permissions, and the service design.
No. Defender XDR correlates supported security signals across Microsoft workloads. Sentinel adds SIEM capabilities and broader log collection and analysis. They can work together in the Defender portal, with integration behavior determined partly by the primary workspace.
No. The portal brings operational views together while Sentinel workspaces remain distinct. Primary and secondary workspaces retain different correlation and synchronization behavior. Treat portal onboarding as a configuration change and test affected integrations.
Across clients they are authorized to query. Defender multitenant hunting and Lighthouse-based workspace queries use different execution patterns. Defender multitenant advanced hunting has a 50,000-record total limit divided across selected tenants, so check completion and result limits before drawing conclusions.
Yes, through an MSSP service model and supporting platform. Define which portal, reports, notifications, and workflows carry your brand, and how client Sentinel workspaces connect to the service. Azure delegation alone does not create a branded client experience.
The client can pay Azure directly, or the provider can supply Azure through a CSP arrangement. The contract should state whether consumption is included in the SOC fee, billed separately, or subject to agreed allowances.
The workspace location establishes an important storage boundary, but central tickets, exports, reports, and external AI processing can create additional copies. Microsoft also documents processing exceptions for some Sentinel capabilities. Assess the complete data flow against the client’s requirements.
Yes. Clients can revoke Lighthouse delegation, but a complete offboarding process must also address separate guest accounts, application grants, direct roles, and other access relationships. Replace operational dependencies before withdrawing essential monitoring or response.
What Is a White-Label SOC?
White Label SIEM for MSSPs
SOC Automation for MSSPs
Agentic SOC on Microsoft Sentinel
Microsoft Sentinel Cost Optimization
Expand Microsoft Sentinel Coverage