Hi @Eduardo Dalmasso ,
Welcome to MS Q&A platform.
Access service connections in project settings from Azure DevOps.
Check whether the Azure Secondary Resource Manager (ARM) Service Connection is associated with the appropriate subscription.
If not, then proceed to make a new Service Connection with valid credentials.
Choose Azure Resource Manager.
Select either Service Principal (Automatic) Authentication, or Manual Authentication. Then, select the appropriate subscription.
In the Azure portal, navigate to subscriptions and then access control (IAM). You should ensure a service principal is used in Azure DevOps with the role of:
Contributor or Owner to the subscription/resource level.
Managed Identity privileges, if applicable.
This happens due to a rate restriction which occurs while updating service connections and the system goes through multiple tries to accomplish the reconnecting of service connections.
So instead, wait 5-10 minutes before trying again. Try using another Azure DevOps user when creating the new service connection.
If the problem is still there try creating the service connection with the Azure command line interface.
az devops service-endpoint create --service-endpoint-configuration <config-file>
If the subscription was recently migrated, be sure to edit the references on the pipeline. Look through the pipeline YAML files for the unused service connection names. If you use the Classic UI, change the Azure Subscription on the pipeline settings.
If you are using a self-hosted agent, restart it,
./svc.sh stop
./svc.sh start
ref:
https://learn.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops
https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal
https://learn.microsoft.com/en-us/azure/devops/pipelines/library/connect-to-azure?view=azure-devops
Let me know if you have any further assistances.