Skip to content

Commit d22a409

Browse files
Update articles/sentinel/extend-sentinel-across-workspaces-tenants.md
Co-authored-by: Yechiel Levin <[email protected]>
1 parent bd89cb3 commit d22a409

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sentinel/extend-sentinel-across-workspaces-tenants.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ Cross-workspace hunting capabilities enable your threat hunters to create new hu
120120

121121
To configure and manage multiple Microsoft Sentinel workspaces, you will need to automate the use of the Microsoft Sentinel management API. For more information on how to automate the deployment of Microsoft Sentinel resources, including alert rules, hunting queries, workbooks and playbooks, see [Extending Microsoft Sentinel: APIs, Integration and management automation](https://techcommunity.microsoft.com/t5/azure-sentinel/extending-azure-sentinel-apis-integration-and-management/ba-p/1116885).
122122

123-
See also [Deploy Custom Content from your Repository](https://aka.ms/repositories) for a consolidated methodology for managing Microsoft Sentinel as code and for deploying and configuring resources from a private Azure DevOps and GitHub repository.
123+
See also [Deploy Custom Content from your Repository](ci-cd.md) for a consolidated methodology for managing Microsoft Sentinel as code and for deploying and configuring resources from a private Azure DevOps and GitHub repository.
124124

125125
## Managing workspaces across tenants using Azure Lighthouse
126126

0 commit comments

Comments
 (0)