Bug with connect Azure Service Connection Authentication in Azure DevOps? Stuck on Blank Callback Page

Question

I am trying to create a Service Connection in Azure DevOps using Docker Registry and Azure Resource Manager. After selecting my subscription and completing the 2FA authentication, I get redirected to a link ending with ***/completecallbackbyauthcode, but instead of proceeding, I see a blank white screen.

I have attempted different approaches, including using different browsers and clearing cache, but the issue persists.

After restarting my machine, the issue changed to a 404 error, and I am still unable to add the Service Connection.

Due to this issue, I cannot deploy my three projects, and I am also encountering errors when configuring a job in the release pipeline.

I have reached out to support multiple times, submitted a bug report, and even subscribed to a paid plan just to be able to post this question. Yet, I still have not received any response. Could someone please address this issue? We need urgent assistance in resolving this issue, as it is critical for our use of your service. Please respond here or contact me as soon as possible!!!

Answer 1

Hi Max,

I’m sorry to hear about the issue you’re facing with the Azure Service Connection in Azure DevOps. The blank callback page or 404 error during authentication is often related to browser settings, network configurations, or temporary service issues. Here are a few steps you can try to resolve this:

Check Browser Settings:

• Ensure that third-party cookies and pop-ups are allowed in your browser.
• Try using an incognito/private browsing window to avoid cache-related issues.

Network Configuration:

• Verify that your network or firewall is not blocking the callback URL.
• If you’re using a VPN, try disabling it temporarily.

Alternative Authentication Method:

• Instead of using the interactive login, try using a Service Principal for authentication. You can create a Service Principal in Azure and use its credentials to set up the Service Connection.
• Documentation: Create a Service Principal

Azure DevOps Status:

• Check the Azure DevOps Status Page to see if there are any ongoing service issues.

Manual Configuration:

• If the UI is not working, you can manually configure the Service Connection using the Azure CLI or REST API.

If none of these steps resolve the issue, I recommend escalating this to Azure DevOps support again, as this might require deeper investigation. Since you’ve already submitted a bug report, you can also try reaching out via the Azure DevOps Community Forum for additional visibility.

rgds,

Alex

p.s. Kindly consider accepting the answer if the information provided is helpful. This can assist other community members in resolving similar issues.