Microsoft Security Exposure Management
Developer and APICreate Azure Devops Connector
In brief
The instructions now direct administrators to Agentic code scanning management, select Add another beside Source code environment, and choose Azure DevOps to open the connector flow.
What Defender admins need to know
Administrators following the setup guide should use the updated navigation steps.
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.
SelectInCreateAgentic code scanning management, next to Source code environment, select Add another, andManage connectors.then select Azure DevOps.You'll be redirected to theCloud Security Connectorspage.On theConnectorstab, select theAzure DevOpsconnectorfrom the list.flow.- Optionally, enter a connector name. If you leave it blank, a default name is assigned automatically.
- Select Next.
@@ -78,8 +78,7 @@ If the tenant hasn't used Cloud Security in the Defender portal:
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.
-- On the **Connectors** tab, select the Azure DevOps connector from the list.
+- 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**.