Integrate your Azure Repos with CloudDefense.AI to ensure robust security directly within your development workflow.
Pre-requisites:
You should be signed in with CloudDefense.ai. If not, please refer to our guide on creating a CloudDefense.ai account. ( Note: Only one superAdmin will create the account access and invite other team admins/members)
Access to an Azure DevOps Account.
Step 1: Select Azure Repos Server Integration
From your CloudDefense dashboard, navigate to the Integration tab in the navigation bar.
Click on Azure Repos under the Source Control section.
Step 2: Provide required credentials
Username, Organization name and Project name:
Username: Retrieve your username from your Azure DevOps profile.
Organization Name: Choose any specific organization from the left sidebar.
Project Name: Select a project within that organization.
Access Token
Navigate to the User Icon on the top right corner of the Azure DevOps dashboard, and in the dropdown, find Personal Access Tokens to generate a new token with your custom configurations.
Important: Make sure to copy and store the token, since you wont be able to see it again.
Step 3: Configure and Integrate the Account
Once getting above credentials head back to Azure Repos Server tab where you'll find the following fields available:
Azure Username
Azure token
Azure organization name
Azure project name
Now fill up the form with all the required information, click the green Configure button.
By following these steps, you'll successfully integrate Azure Repos with CloudDefense, enabling advanced security measures and seamless workflow integration.
After setting up your Azure Repos integration, you're ready to scan your repositories. For comprehensive instructions on how to initiate scans and view results, please refer to our Scan Repos Documentation. This guide will help you effectively manage and analyze the security of your repositories.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article