Skip to content

Commit 07e5dc9

Browse files
Merge pull request #259581 from j0tr/patch-23
Update edit-devops-connector.md
2 parents 38ab046 + 9d4777b commit 07e5dc9

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/defender-for-cloud/edit-devops-connector.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,8 @@ After onboarding your Azure DevOps, GitHub, or GitLab environments to Microsoft
2828
1. Navigate to **Configure access**. Here you can perform token exchange, change the organizations/groups onboarded, or toggle autodiscovery.
2929

3030
> [!NOTE]
31-
> IF you are the owner of the connector, re-authorizing your environment to make changes is **optional**. For a user trying to take ownership of the connector, you must re-authorize using your access token. This change is irreversible as soon as you select 'Re-authorize'.
31+
> If you are the owner of the connector, re-authorizing your environment to make changes is **optional**.
32+
> If you are trying to take ownership of the connector, you must re-authorize using your access token. This change is irreversible as soon as you select 'Re-authorize'.
3233
3334
1. Use **Edit connector account** component to make changes to onboarded inventory. If an organization/group is greyed out, please ensure that you have proper permissions to the environment and the scope is not onboarded elsewhere in the Tenant.
3435

@@ -38,4 +39,4 @@ After onboarding your Azure DevOps, GitHub, or GitLab environments to Microsoft
3839

3940
## Next steps
4041

41-
- Learn more about [DevOps security in Defender for Cloud](defender-for-devops-introduction.md).
42+
- Learn more about [DevOps security in Defender for Cloud](defender-for-devops-introduction.md).

0 commit comments

Comments
 (0)