Issue while adding a Service Connection in Azure Devops

Hello Joel Yash,

Thank you for posting your question in the Microsoft Q&A forum. 

This issue typically arises due to permissions, connectivity, or service delays. Below are the primary steps to resolve it: 

• Check Permissions - Ensure your Azure account (or the account used in your pipeline/service connection setup) has the necessary permissions in Azure Active Directory and the target subscription. At a minimum, it should have Reader rights on the subscription to list resource groups. For creating a service connection, it might need Owner or User Access Administrator roles to assign roles (like Contributor) to the service principal. 
• Subscription Selection  - Verify you’ve selected the correct subscription in the Azure Resource Manager service connection dialog. Sometimes, switching subscriptions and switching back can refresh the list. 
• Browser or Portal Issues  - Clear your browser cache or try an incognito window. Alternatively, use a different browser or device to rule out local issues. 
• Azure DevOps Permissions - Ensure you have adequate permissions in Azure DevOps to create service connections (e.g., Project Administrator or equivalent). 
• Manual Entry - If the dropdown doesn’t populate, try typing the resource group name manually (if the UI allows it). Some interfaces support manual input. 
• API Delays or Outages  - Check the Azure Status Dashboard for any ongoing issues with Azure Resource Manager or Azure DevOps that might cause delays in fetching data. 
• Use Existing Service Principal  - Instead of auto-creating a new service principal, try creating one manually in Azure AD (App Registration) and then use the "Manual" option in the service connection setup to provide the App ID, tenant ID, and secret. 
• Alternative Method - Create the service connection using Azure CLI or PowerShell if the UI is unresponsive: 

powershell 

az devops service-endpoint azurerm create --name "MyServiceConnection" --azure-rm-subscription-id "00000000-0000-0000-0000-000000000000" --azure-rm-subscription-name "MySubscription" --azure-rm-tenant-id "00000000-0000-0000-0000-000000000000" --azure-rm-service-principal-id "00000000-0000-0000-0000-000000000000" --azure-rm-service-principal-key "mySecret" 

• Check Network Issues - If you’re on a corporate network, firewalls or proxies might block requests to Azure DevOps or Azure Resource Manager. Try from a different network. 

By addressing these areas, you should be able to resolve the loading issue and create the service connection successfully. If problems persist, contact Azure support for further investigation. 

Please, let me know the response helps answer your question? If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. 🙂