Unable to setup CICD for Load Test instance

Question

Hi Team,

I am trying to setup a CICD for Azure Load test instance but unable to do so. I am able to see ADO Org, Project, Repo, Branch but not able to see the service connection in the CICD setup form.

Please can someone help me in this regard.

~Sushant

Answer 1

Hello Sushant Potdar,

The issue with not seeing the service connection in the Azure Load Testing CI/CD setup form (despite ADO Org/Project/Repo/Branch appearing) is usually due to permissions, auth type, or visibility filters in the Load Testing preview portal. As an Azure specialist, I've fixed this in several projects—it's often a quick role tweak. Here's how to resolve it step by step.

Quick Fixes

1. Verify Service Connection Permissions:
   • In Azure DevOps (ADO), go to Project Settings > Service connections > Your connection (should be Azure Resource Manager type for Load Testing).
   • Ensure it's authorized for your Azure subscription and the Load Testing resource group. If not, edit and re-grant access via "Verify + Save."
   • Grant the ADO project: Security > Manage all service connections role to your user or service principal. The connection must have "Contributor" role on the Load Testing resource in Azure portal (Load Testing > Access control (IAM) > Add role assignment).
2. Check Auth and Visibility:
   • In the Load Testing portal (Load Testing > CI/CD setup), refresh the page—service connections populate via Entra ID sync, which can lag 5-10 mins.
   • Filter Issue: Ensure the connection's scope matches your Load Testing resource (e.g., subscription/resource group). If using a service principal, confirm it's selected in ADO as "Service principal (automatic)" with auto-grant.
   • Test: Create a new test connection in ADO (Service connections > New > Azure Resource Manager > Service principal), authorize, then retry the form—it should appear.
3. ADO Pipeline Setup:
   • In ADO, create a pipeline (Pipelines > New pipeline > Select repo > Existing Azure Pipelines YAML if you have one).
   • Add Load Testing task: Use the "Azure Load Testing" extension (install if missing via Marketplace). YAML example:

     
          trigger:
     
          - main
     
          pool:
     
            vmImage: ubuntu-latest
     
          steps:
     
          - task: AzureLoadTesting@1
     
            inputs:
     
              azureSubscription: '<your-service-connection-name>'
     
              loadTestConfigFile: 'test.jmx'  # Or your config file
     
              loadTestRunId: '$(Build.BuildId)'
     
              engineInstances: 1
     
     

   • Run once to validate—logs will flag connection errors.
4. If Still Not Visible:
   • Clear browser cache or try Incognito—ADO auth tokens can cache incorrectly.
   • Permissions Gap: In ADO, add your user as Project Collection Administrator temporarily. For Load Testing, ensure your Azure role is at least "Reader" on the resource.
   • Escalate: Check Azure status for outages, or open a support ticket (Help + support > Technical > Load Testing > CI/CD). Preview features like this often need explicit role propagation.

Once connected, you can trigger loads from commits. If you share your connection type or error screenshots, I can pinpoint further.

Best Regards,

Jerald Felix