Microsoft has expanded the public preview of Integrated Security Operations Center, or ISOC, in Microsoft Defender. The November 18, 2026 announcement highlights broader SIEM functionality, longer included retention for Defender data, and an opt-in route for existing Microsoft Sentinel customers.
For security partners, the significant point is not simply that more features are available. The update creates a reason to reassess how customers combine threat protection, security analytics, and managed operations—without assuming that an existing Sentinel deployment should automatically move.
What changed in the preview
Microsoft says the expanded preview now includes the full breadth of SIEM capabilities. Specifically named additions are content hub, SOC optimization, and CI/CD repositories, alongside case management, workbooks, and automation.
Included Defender data retention increases from 30 days to 90 days. This can give analysts a longer investigation window for activity that is only recognized as suspicious after the initial event. It also provides more historical context for threat hunting.
The scope of that retention statement matters: the announcement refers to Defender data. It should not be interpreted as a promise of free 90-day retention for every third-party log source or every category of security data. Validate data-specific retention and charging rules before presenting a cost model.
Existing Sentinel customers also gain a route to opt in. Microsoft explicitly says the move is not automatic.
Licensing and default behavior
ISOC is not described as a separate standalone product. Microsoft identifies it as a feature benefit for eligible Microsoft 365 E5 and Microsoft 365 E7 customers.
The word “eligible” deserves attention. A partner should verify the customer’s specific entitlement and the applicable technical prerequisites rather than treating a plan name alone as proof that every capability is ready to use.
The expansion remains in public preview. This announcement does not establish general availability, a mandatory migration deadline, or an automatic transition for Sentinel customers. The appropriate default is therefore assessment, not a blanket migration project.
Partners should also check preview terms and support expectations against their own service commitments. A managed service may depend on repeatable operational behavior, escalation paths, and agreed investigation workflows that need validation before a customer changes platforms or operating models.
Customers without Sentinel: start with the security outcomes
For a customer without an existing Sentinel deployment, Microsoft suggests putting the SIEM and XDR capabilities in Defender to work and connecting relevant non-Microsoft data.
A sensible engagement begins with an inventory of the incidents the customer needs to detect and investigate. Identify the data required for those use cases, the teams responsible for responding, and the automation that can safely reduce manual work.
Avoid treating access to the capability as a completed implementation. Data onboarding, detection tuning, access control, and response procedures remain partner work. A focused initial deployment with clear acceptance criteria is more useful than connecting every available source without an operational plan.
Potential criteria include successful ingestion of the agreed data sources, validated detections for selected scenarios, and an analyst workflow that can take a case from triage through closure.
Existing Sentinel customers: compare before moving
For a Sentinel customer, the assessment should begin with what already works. Catalogue detections, workbooks, automation, connected data sources, and operational dependencies. Identify which elements need migration or adaptation and which require additional testing.
Microsoft specifically recommends comparing projected costs. Build that comparison from the customer’s expected workload rather than a generic assertion that the new arrangement is cheaper.
Useful inputs include:
- Current data volumes and the sources expected to remain in scope.
- Retention requirements for each relevant data category.
- The customer’s confirmed licensing and benefit eligibility.
- Implementation, testing, and ongoing service delivery effort.
- Any operational changes affecting analyst workload or existing integrations.
Where commercial or technical rules are unclear, record them as assumptions requiring confirmation. The announcement does not provide enough detail to calculate a reliable customer-specific saving on its own.
For customers that choose to opt in, agree on a transition plan with explicit validation checkpoints. Preserve an inventory of existing security content and confirm how investigation continuity will be maintained. Do not assume the announcement itself guarantees a particular rollback mechanism; establish the supported options before making changes.
MSSPs and MDR providers: make content deployment repeatable
The addition of CI/CD repositories is especially relevant to partners operating across multiple customer tenants. Microsoft points to repositories as a way to deploy consistent security content.
Consistency should not mean ignoring customer differences. Partners still need a method for separating shared detection logic from tenant-specific settings, documenting changes, reviewing deployments, and testing updates before wider release.
A useful internal pilot would assess whether content can be deployed predictably, whether failures are visible, and whether the service team can maintain an auditable change history. These are recommended evaluation steps, not additional product guarantees in the announcement.
The commercial service catalogue may also need adjustment. Distinguish readiness assessment, onboarding, content migration, and recurring operations so customers understand what is included in the managed service and what remains project work.
Partner next steps
Review the ISOC technical documentation, updated partner guide, and partner FAQ before changing customer proposals.
Then select a suitable evaluation customer, confirm eligibility, and test the workflows that matter most to the service. Keep the decision evidence-based: security coverage, operating effort, support expectations, and projected costs should all be visible.
Bottom line
The expanded ISOC preview creates a broader foundation for security services in Defender. It does not make migration automatic or remove the need for customer-specific design. Partners can add value by validating eligibility, retention scope, costs, and operational readiness before recommending whether—and when—a customer should opt in.