Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
After onboarding your Azure DevOps, GitHub, or GitLab environments to Microsoft Defender for Cloud, you might need to change the authorization token for a connector. You might also need to add or remove onboarded organizations or groups, or install the GitHub application to another scope. This article shows how to update those connector settings.
Prerequisites
Before you edit a DevOps connector, make sure you have the following:
- An Azure account with Defender for Cloud onboarded. If you don't already have an Azure account, create one for free.
- An onboarded DevOps environment. For onboarding guidance, see Onboard Azure DevOps, Onboard GitHub, or Onboard GitLab.
Make edits to your DevOps connector
To edit a DevOps connector in Defender for Cloud:
Sign in to the Azure portal.
Go to Microsoft Defender for Cloud > Environment settings.
Identify the connector you want to change.
Select Edit settings for the connector.
Go to Configure access. Here you can exchange tokens, change onboarded organizations or groups, or toggle autodiscovery.
Note
If you're the owner of the connector, reauthorizing your environment to make changes is optional. If you're trying to take ownership of the connector, you must reauthorize by using your access token. This change is irreversible as soon as you select Reauthorize.
Use Edit connector account to update onboarded inventory. If an organization or group is grayed out, verify that you have permissions to that environment and that the scope isn't onboarded elsewhere in the tenant.
To save inventory changes, select Next: Review and generate > and then select Update. If you skip Update, Defender for Cloud doesn't save your inventory changes.
