Skip to content

Commit 1b6e0a9

Browse files
authored
Update ci-cd-custom-deploy.md
------- cc: @austinmccollum
1 parent c22a5fe commit 1b6e0a9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sentinel/ci-cd-custom-deploy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ There are two primary ways to customize the deployment of your repository conten
2727
Microsoft Sentinel currently supports connections to GitHub and Azure DevOps repositories. Before connecting your Microsoft Sentinel workspace to your source control repository, make sure that you have:
2828

2929
- An **Owner** role in the resource group that contains your Microsoft Sentinel workspace *or* a combination of **User Access Administrator** and **Sentinel Contributor** roles to create the connection
30-
- Contributor access to your GitHub or Azure DevOps repository
30+
- Collaborator access to your GitHub repository or Project Administrator access to your Azure DevOps repository
3131
- Actions enabled for GitHub and Pipelines enabled for Azure DevOps
3232
- Ensure custom content files you want to deploy to your workspaces are in relevant [Azure Resource Manager (ARM) templates](../azure-resource-manager/templates/index.yml).
3333

0 commit comments

Comments
 (0)