Deploy content as code with ISOC in Microsoft Defender - Microsoft Defender XDR | Microsoft Learn
In brief
The documentation now describes repository connections that deploy content to ISOC or Microsoft Sentinel workspaces, or supported Defender content to Microsoft Defender XDR at tenant scope. Tenant targets support Defender workbooks and custom detections, and don't require a workspace.
What Defender admins need to know
Review deployment targets, supported content formats, and licensing prerequisites when planning CI/CD connections. No required administrator action is stated.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Deploy content as code from your repository for anwith ISOC workspacein Microsoft Defender - Microsoft Defender XDR | Microsoft Learn
Use repositories with Integrated Security Operations Center (ISOC) in Microsoft Defender to manage and deploy custom security content to your ISOC workspace by using CI/CD.continuous integration and continuous delivery (CI/CD).
Repository connections support a target-based deployment model. Depending on your tenant configuration, you can deploy content to a workspace, either ISOC or Microsoft Sentinel, or deploy supported Defender-level content to Microsoft Defender XDR at tenant scope.
Workspace-targeted connections support existing workspace content types and supported Defender-level content. Tenant-targeted connections support Defender workbooks and custom detections.
You can manage content from the Microsoft Defender portal or ana supported external GitHub or Azure DevOpssource control repository. Managing contentUpdates made in an externalyour repository lets you update content outside of Microsoft Defender andare automatically deploy those updatesdeployed to your ISOC workspace.
The CI/CD experience and supported content types for an ISOC workspace are the same as the existing Microsoft Sentinel repository experience.
Note
This feature is in preview. Capabilities and availability might change during the preview period.selected target.
Prerequisites
Before you begin, make sure the following requirements are met:
- Your tenant is eligible for ISOC.
YouFor workspace-targeted connections, you have an ISOC workspace or an existing Microsoft Sentinel workspace in a resource group where you have the Owner role. A workspace isn't required for tenant-targeted connections.- You have the Global Administrator role in Microsoft Entra ID for the initial CI/CD setup.
- Custom content files that you want to deploy
to your workspaceare in a supportedformat.format for the selected deployment target. For supported formats, see Plan your repository content. - The account you use to create the connection is in your home tenant. External identities such as B2B guest accounts and delegated access aren't supported.
- (Custom
detection rules only)detections and Defender workbooks) You havea Microsoft 365 E5an ISOC-eligible license or an equivalent license that includes Microsoft Defender XDR. For more information, see Deploy custom detection rules as code.
GitHub prerequisites
- You have Collaborator access to your GitHub repository.
- GitHub Actions is enabled.
Azure DevOps prerequisites (workspace only)
Before connecting to Azure DevOps, make sure that:
For more information about deployable content types, see Plan your repository content.
Supported deployment targets and content types
When you create a repository connection, select the target where you want to deploy content.
| Deployment target | Supported content |
|---|---|
| Workspace | Existing supported Microsoft Sentinel workspace content, custom detections, and Defender workbooks |
| Defender XDR | Custom detections and Defender workbooks |
The available content types are filtered based on the selected deployment target and tenant eligibility.
Workspace-targeted connections
Use a workspace-targeted connection to deploy content to an ISOC workspace or an existing Microsoft Sentinel workspace.
Workspace-targeted connections support existing Microsoft Sentinel repository content types and Defender-level content.
Tenant-targeted connections
Use a Defender XDR target to deploy supported content at tenant scope.
Tenant-targeted connections support Defender workbooks and custom detections. An ISOC or Microsoft Sentinel workspace isn't required for this deployment target.
For eligible tenants without a workspace, Defender XDR is the only available deployment target.
Connect a repository
Use this procedure to connectcreate a GitHubrepository connection for a workspace or Azure DevOps repository toMicrosoft Defender XDR deployment target. The available targets depend on your ISOC workspace.tenant configuration.
Each connection can deploy the content types supported by its selected target. Workspace-targeted connections support multiple types of custom content,existing workspace content types, including analytics rules, automation rules, custom detection rules, hunting queries, parsers, playbooks, and workbooks. Tenant-targeted connections support Defender workbooks and custom detections.
For more information, see About Microsoft Sentinel content and solutions.
You can't create duplicate connections with the same repository and branch in a single ISOC workspace.
- Sign in to the Microsoft Defender portal.
- Make sure that you're signed in to your source control application with the credentials you want to use for the connection.
- In the Defender portal, select
Microsoft Sentinel>Content management > Repositories. - Select Add new.
- On the Create new deployment connection page, enter a name for the connection.
- Enter a description for the connection.
In GitHub, select the repository where you want to install the Azure-Sentinel app.
Install the Azure-Sentinel app.
Return to the Create new deployment connection page.
From Branch, select the branch that you want to
connectconnect.From Target, select the deployment target:
- Workspace to deploy content to an ISOC or Microsoft Sentinel workspace.
- Defender XDR to deploy supported Defender-level content at tenant scope.
If your tenant doesn't have an ISOC
workspace.or Microsoft Sentinel workspace, only the Defender XDR target is available, provided your tenant is eligible for ISOC.From Content Types, select the types of content that you want to deploy. Available content types are filtered based on the selected target.
Both parsers and hunting queries use the Saved Searches API to deploy content. If you select one of these content types and your branch contains the other type, both content types are deployed.
For other content types, only the content types that you select are deployed.
Select Create.
For example:

Azure DevOps (workspace only)
Azure DevOps automatically authorizes you by using your current Azure credentials.
1. Make sure that you're authorized to the same Azure DevOps tenant that you're connecting to from Microsoft Defender.
After you create the connection, a new workflow or pipeline is generated in your repository. TheSupported content stored infrom your repository is deployed to your ISOC workspace.the selected workspace or Defender XDR tenant-level target.
Deployment time might vary depending on the amount of content that you're deploying.
After deployment is complete:
TheWorkspace-level contentstoredappears inyour repository appears onthe corresponding Microsoft Sentinelpagesexperiences in the Defender portal.- Defender-level content appears in the corresponding Microsoft Defender experiences.
- The connection details on the Repositories page show
thedeployment status, time of the last deployment, and a link tothedeployment logs.
The Repositories page provides a unified view of repository deployment status for workspaces you have access to. You can review deployment status without selecting each workspace separately.
For example:
Delete content
Deleting content from your repository doesn't automatically delete it from your ISOC workspace.content previously deployed to the selected target.
To remove content that was deployed through a repository:
- Delete the content from your repository.
- Delete the corresponding deployed content from the relevant Microsoft Sentinel
in theor Microsoft Defenderportal.experience.
You can filter content by its source name to help identify content deployed from repositories.
Remove a repository connection
Removing a repository connection stops future content deployments. Content that was previouslydeployments to the selected target. Previously deployed content remains in your ISOC workspace.at its deployment target.
To use Bicep files, your repository connection must be newer than November 1, 2024. Remove and recreate an older connection to update it.
To remove a repository connection:
- Sign in to the Microsoft Defender portal.
- Select
Microsoft Sentinel>Content management > Repositories. - Select the connection that you want to remove.
- Select Delete.
- Select Yes to confirm the deletion.
After you remove the connection, content previously deployed through the connectioncontent remains in your ISOC workspace.the corresponding workspace or Microsoft Defender experience. Content added to the repository after you remove the connection isn't deployed.
If you encounter an error when removing a connection, check your source control repository and confirm that the associated GitHub workflow or Azure DevOps pipeline is deleted.
@@ -1,6 +1,6 @@ --- layout: Conceptual-title: Deploy content as code from your repository for an ISOC workspace - Microsoft Defender XDR | Microsoft Learn+title: Deploy content as code with ISOC in Microsoft Defender - Microsoft Defender XDR | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/defender-xdr/deploy-content-integrated-security-operations breadcrumb_path: /defender-xdr/breadcrumb/toc.json permissioned-type: public@@ -8,20 +8,20 @@ feedback_system: Standard feedback_product_url: https://techcommunity.microsoft.com/t5/microsoft-365-defender/bd-p/MicrosoftThreatProtection uhfHeaderId: MSDocsHeader-MicrosoftDefender manager: orspodek-description: Learn how to connect an ISOC workspace to a GitHub or Azure DevOps repository to manage and deploy security content by using CI/CD.+description: Learn how to use repository connections to deploy security content to workspaces or Microsoft Defender XDR at tenant scope by using CI/CD. author: mberdugo ms.author: monaberdugo ms.localizationpriority: high ms.topic: how-to ms.service: microsoft-sentinel-ms.date: 2026-09-14T00:00:00.0000000Z+ms.date: 2026-11-15T00:00:00.0000000Z ms.collection: - m365-security - tier1 - usx-security - msftsolution-secops ai-usage: ai-assisted-ms.custom: msecd-doc-authoring-1014+ms.custom: msecd-doc-authoring-1032 locale: en-us document_id: 96b39cb0-55c2-44c8-aeda-c7cc4072cdce document_version_independent_id: 96b39cb0-55c2-44c8-aeda-c7cc4072cdce@@ -38,38 +38,36 @@ monikers: [] item_type: Content source_path: defender-xdr/deploy-content-integrated-security-operations.md cmProducts:-- https://authoring-docs-microsoft.poolparty.biz/devrel/9bdc1705-9b40-49d6-8377-caa0b71fda66-- https://authoring-docs-microsoft.poolparty.biz/devrel/5bd2b3fa-c186-4b92-a3c8-09f22a249d37 - https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/c671beaa-a830-4c9f-aceb-97379ee031ca+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/1577a46d-8446-40bd-bfae-0578362f4d94+- https://authoring-docs-microsoft.poolparty.biz/devrel/8a94907f-2511-4271-b5ca-ec7f2e75067c spProducts:-- https://authoring-docs-microsoft.poolparty.biz/devrel/686ed158-d915-41e9-9760-efa46ba88f6d-- https://authoring-docs-microsoft.poolparty.biz/devrel/7eba7926-b7b2-4a7a-bf89-e6ac53b3e7f6 - https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/8921374c-4dbe-4ed0-b011-a39e18bfbd98+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/cdf3f22d-5420-4d59-a2bf-66d6b3d9c828+- https://authoring-docs-microsoft.poolparty.biz/devrel/bffa8e88-f633-409d-a24d-083bdbc68872 platformId: 10132765-3845-3159-f177-45eabfa4d0cb --- -# Deploy content as code from your repository for an ISOC workspace - Microsoft Defender XDR | Microsoft Learn+# Deploy content as code with ISOC in Microsoft Defender - Microsoft Defender XDR | Microsoft Learn -Use repositories with Integrated Security Operations Center (ISOC) in Microsoft Defender to manage and deploy custom security content to your ISOC workspace by using CI/CD.
+Use repositories with Integrated Security Operations Center (ISOC) in Microsoft Defender to manage and deploy security content by using continuous integration and continuous delivery (CI/CD).
-You can manage content from the Microsoft Defender portal or an external GitHub or Azure DevOps repository. Managing content in an external repository lets you update content outside of Microsoft Defender and automatically deploy those updates to your ISOC workspace.
+Repository connections support a target-based deployment model. Depending on your tenant configuration, you can deploy content to a workspace, either ISOC or Microsoft Sentinel, or deploy supported Defender-level content to Microsoft Defender XDR at tenant scope.
-The CI/CD experience and supported content types for an ISOC workspace are the same as the existing Microsoft Sentinel repository experience.
+Workspace-targeted connections support existing workspace content types and supported Defender-level content. Tenant-targeted connections support Defender workbooks and custom detections.
-Note
-
-This feature is in preview. Capabilities and availability might change during the preview period.
+You can manage content from the Microsoft Defender portal or a supported external source control repository. Updates made in your repository are automatically deployed to the selected target.
## Prerequisites
Before you begin, make sure the following requirements are met:
- Your tenant is [eligible for ISOC](isoc-overview).
-- You have an [ISOC workspace](onboard-isoc-workspace) in a resource group where you have the **Owner** role.
+- For workspace-targeted connections, you have an [ISOC workspace](onboard-isoc-workspace) or an existing Microsoft Sentinel workspace in a resource group where you have the **Owner** role. A workspace isn't required for tenant-targeted connections.
- You have the **Global Administrator** role in Microsoft Entra ID for the initial CI/CD setup.
-- Custom content files that you want to deploy to your workspace are in a supported format. For supported formats, see [Plan your repository content](/en-us/azure/sentinel/ci-cd-custom-content#plan-your-repository-content).
+- Custom content files that you want to deploy are in a supported format for the selected deployment target. For supported formats, see [Plan your repository content](/en-us/azure/sentinel/ci-cd-custom-content#plan-your-repository-content).
- The account you use to create the connection is in your home tenant. External identities such as B2B guest accounts and delegated access aren't supported.
-- **(Custom detection rules only)** You have a Microsoft 365 E5 license or an equivalent license that includes Microsoft Defender XDR. For more information, see [Deploy custom detection rules as code](/en-us/azure/sentinel/ci-cd-custom-content#deploy-custom-detection-rules-as-code-preview).
+- **(Custom detections and Defender workbooks)** You have an ISOC-eligible license or an equivalent license that includes Microsoft Defender XDR. For more information, see [Deploy custom detection rules as code](/en-us/azure/sentinel/ci-cd-custom-content#deploy-custom-detection-rules-as-code-preview).
### GitHub prerequisites
@@ -78,7 +76,7 @@ Before connecting to GitHub, make sure that: - You have **Collaborator** access to your GitHub repository.
- GitHub Actions is enabled.
-### Azure DevOps prerequisites
+### Azure DevOps prerequisites (workspace only)
Before connecting to Azure DevOps, make sure that:
@@ -88,17 +86,44 @@ Before connecting to Azure DevOps, make sure that:
For more information about deployable content types, see [Plan your repository content](/en-us/azure/sentinel/ci-cd-custom-content#plan-your-repository-content).
+## Supported deployment targets and content types
+
+When you create a repository connection, select the target where you want to deploy content.
+
+| Deployment target | Supported content |
+| --- | --- |
+| **Workspace** | Existing supported Microsoft Sentinel workspace content, custom detections, and Defender workbooks |
+| **Defender XDR** | Custom detections and Defender workbooks |
+
+The available content types are filtered based on the selected deployment target and tenant eligibility.
+
+### Workspace-targeted connections
+
+Use a workspace-targeted connection to deploy content to an ISOC workspace or an existing Microsoft Sentinel workspace.
+
+Workspace-targeted connections support existing Microsoft Sentinel repository content types and Defender-level content.
+
+### Tenant-targeted connections
+
+Use a Defender XDR target to deploy supported content at tenant scope.
+
+Tenant-targeted connections support Defender workbooks and custom detections. An ISOC or Microsoft Sentinel workspace isn't required for this deployment target.
+
+For eligible tenants without a workspace, Defender XDR is the only available deployment target.
+
## Connect a repository
-Use this procedure to connect a GitHub or Azure DevOps repository to your ISOC workspace.
+Use this procedure to create a repository connection for a workspace or Microsoft Defender XDR deployment target. The available targets depend on your tenant configuration.
-Each connection can support multiple types of custom content, including analytics rules, automation rules, custom detection rules, hunting queries, parsers, playbooks, and workbooks. For more information, see [About Microsoft Sentinel content and solutions](/en-us/azure/sentinel/sentinel-solutions).
+Each connection can deploy the content types supported by its selected target. Workspace-targeted connections support existing workspace content types, including analytics rules, automation rules, custom detection rules, hunting queries, parsers, playbooks, and workbooks. Tenant-targeted connections support Defender workbooks and custom detections.
-You can't create duplicate connections with the same repository and branch in a single ISOC workspace.
+For more information, see [About Microsoft Sentinel content and solutions](/en-us/azure/sentinel/sentinel-solutions).
+
+You can't create duplicate connections with the same repository and branch in a single workspace.
1. Sign in to the [Microsoft Defender portal](https://security.microsoft.com/).
2. Make sure that you're signed in to your source control application with the credentials you want to use for the connection.
-3. In the Defender portal, select **Microsoft Sentinel** > **Content management** > **Repositories**.
+3. In the Defender portal, select **Content management** > **Repositories**.
4. Select **Add new**.
5. On the **Create new deployment connection** page, enter a name for the connection.
6. Enter a description for the connection.
@@ -117,19 +142,25 @@ You can't create duplicate connections with the same repository and branch in a 4. In GitHub, select the repository where you want to install the **Azure-Sentinel** app.
5. Install the **Azure-Sentinel** app.
6. Return to the **Create new deployment connection** page.
- 7. From **Branch**, select the branch that you want to connect to your ISOC workspace.
- 8. From **Content Types**, select the content that you want to deploy.
+ 7. From **Branch**, select the branch that you want to connect.
+ 8. From **Target**, select the deployment target:
+
+ - **Workspace** to deploy content to an ISOC or Microsoft Sentinel workspace.
+ - **Defender XDR** to deploy supported Defender-level content at tenant scope.
+
+ If your tenant doesn't have an ISOC or Microsoft Sentinel workspace, only the Defender XDR target is available, provided your tenant is eligible for ISOC.
+ 9. From **Content Types**, select the types of content that you want to deploy. Available content types are filtered based on the selected target.
Both parsers and hunting queries use the **Saved Searches** API to deploy content. If you select one of these content types and your branch contains the other type, both content types are deployed.
For other content types, only the content types that you select are deployed.
- 9. Select **Create**.
+ 10. Select **Create**.
For example:

-# [Azure DevOps](#tab/azure-devops)
+# [Azure DevOps (workspace only)](#tab/azure-devops)
Azure DevOps automatically authorizes you by using your current Azure credentials.
1. Make sure that you're authorized to the same Azure DevOps tenant that you're connecting to from Microsoft Defender.
@@ -150,7 +181,7 @@ Azure DevOps automatically authorizes you by using your current Azure credential
---
-After you create the connection, a new workflow or pipeline is generated in your repository. The content stored in your repository is deployed to your ISOC workspace.
+After you create the connection, a new workflow or pipeline is generated in your repository. Supported content from your repository is deployed to the selected workspace or Defender XDR tenant-level target.
Deployment time might vary depending on the amount of content that you're deploying.
@@ -169,8 +200,11 @@ To view the deployment status in Azure DevOps:
After deployment is complete:
-- The content stored in your repository appears on the corresponding Microsoft Sentinel pages in the Defender portal.
-- The connection details on the **Repositories** page show the deployment status, time of the last deployment, and a link to the deployment logs.
+- Workspace-level content appears in the corresponding Microsoft Sentinel experiences in the Defender portal.
+- Defender-level content appears in the corresponding Microsoft Defender experiences.
+- The connection details on the **Repositories** page show deployment status, time of the last deployment, and a link to deployment logs.
+
+The Repositories page provides a unified view of repository deployment status for workspaces you have access to. You can review deployment status without selecting each workspace separately.
For example:
@@ -188,12 +222,12 @@ If you edit deployed content in Microsoft Defender, export the updated content b
## Delete content
-Deleting content from your repository doesn't delete it from your ISOC workspace.
+Deleting content from your repository doesn't automatically delete content previously deployed to the selected target.
To remove content that was deployed through a repository:
1. Delete the content from your repository.
-2. Delete the corresponding content from Microsoft Sentinel in the Defender portal.
+2. Delete the corresponding deployed content from the relevant Microsoft Sentinel or Microsoft Defender experience.
You can filter content by its source name to help identify content deployed from repositories.
@@ -201,19 +235,19 @@ You can filter content by its source name to help identify content deployed from
## Remove a repository connection
-Removing a repository connection stops future content deployments. Content that was previously deployed remains in your ISOC workspace.
+Removing a repository connection stops future content deployments to the selected target. Previously deployed content remains at its deployment target.
To use Bicep files, your repository connection must be newer than November 1, 2024. Remove and recreate an older connection to update it.
To remove a repository connection:
1. Sign in to the [Microsoft Defender portal](https://security.microsoft.com/).
-2. Select **Microsoft Sentinel** > **Content management** > **Repositories**.
+2. Select **Content management** > **Repositories**.
3. Select the connection that you want to remove.
4. Select **Delete**.
5. Select **Yes** to confirm the deletion.
-After you remove the connection, content previously deployed through the connection remains in your ISOC workspace. Content added to the repository after you remove the connection isn't deployed.
+After you remove the connection, previously deployed content remains in the corresponding workspace or Microsoft Defender experience. Content added to the repository after you remove the connection isn't deployed.
If you encounter an error when removing a connection, check your source control repository and confirm that the associated GitHub workflow or Azure DevOps pipeline is deleted.
