Microsoft Security Exposure Management
Developer and APICreate Github Connector
In brief
The instructions now direct administrators to Agentic code scanning management, select Add another under Source code environment, and choose Azure DevOps. Connector naming remains optional.
What Defender admins need to know
Administrators following this setup should use the updated navigation path. No mandatory action is stated.
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.
Select
- In
CreateAgentic code scanning management, next to Source code environment, select Add another, andManage connectors.then select Azure DevOps.You'll be redirected to theAzure DevOpsCloud Security Connectorsconnector flow.page. On theConnectorstab, select the GitHub connector from the list.Optionally, enter a connector name. If you leave it blank, a default name is assigned automatically.
Select Next.
Step 3: Configure access and permissions
@@ -71,10 +71,9 @@ 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).
- *Select **Create and Manage connectors**. You'll be redirected to the **Cloud Security Connectors** page.*
-2. On the **Connectors** tab, select the GitHub connector from the list.
-3. Optionally, enter a connector name. If you leave it blank, a default name is assigned automatically.
-4. Select **Next**.
+- 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.***
+- Optionally, enter a connector name. If you leave it blank, a default name is assigned automatically.
+- Select **Next**.
## Step 3: Configure access and permissions