Microsoft Security Exposure Management
Developer and APICreate Github Connector
In brief
The guide now instructs administrators to select GitHub under Source code environment, rather than Azure DevOps, and proceed to the GitHub connector flow.
What Defender admins need to know
Use the updated selection when configuring a GitHub connector.
Summaries are generated from the documentation change itself.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
- In the Defender portal, go to MDASH Initiative > Settings. For information about accessing the MDASH Initiative, see Entry points.
- In Agentic code scanning management, next to Source code environment, select Add another, and then select
Azure DevOps.GitHub.You'll be redirected to theAzure DevOpsGitHubconnector flow. - Optionally, enter a connector name. If you leave it blank, a default name is assigned automatically.
- Select Next.
@@ -71,7 +71,7 @@ If the tenant hasn't used Cloud Security in the Defender portal:
1. In the Defender portal, go to MDASH Initiative > **Settings**. For information about accessing the MDASH Initiative, see [Entry points](/en-us/security-exposure-management/ai-code-security-onboarding).
-- In **Agentic code scanning management**, next to **Source code environment**, select **Add another**, and then select **Azure DevOps.***You'll be redirected to the***Azure DevOps*****connector flow.***
+- In **Agentic code scanning management**, next to **Source code environment**, select **Add another**, and then select **GitHub.***You'll be redirected to the***GitHub*****connector flow.***
- Optionally, enter a connector name. If you leave it blank, a default name is assigned automatically.
- Select **Next**.