cant deploy to web apps using bit bucket

Hello Virtual Watt Admin,

Greetings! Thanks for raising this question in Q&A forum.

I understand this is blocking your deployment. Based on your description, the most likely cause is an OAuth callback or redirect URI mismatch between the Azure App Service deployment configuration and the Bitbucket/Atlassian authentication flow, which can result in a continuous sign-in loop.

1. In your Azure Web App, remove the existing Bitbucket deployment connection if it was previously configured.
2. Verify that the callback/redirect URL registered in Bitbucket (Atlassian) exactly matches the URL expected by Azure App Service deployment settings.
3. Clear the browser cache or test the authorization flow in an InPrivate/Incognito session to eliminate any cached authentication tokens.
4. Review the Deployment Center logs and App Service Activity Log for any callback, authorization, or token exchange errors.
5. If the callback continues to fail after validating the redirect URL, open an Azure support request. This typically requires backend log review to determine whether the failure is occurring within the deployment integration workflow.

The next action is with you to validate the redirect URI and collect the deployment logs. If the issue persists, the Azure support team will need to review the authentication and deployment backend logs to identify the exact failure point.

If this answer helps you kindly accept the answer which will help others who have similar questions

Best Regards,

Jerald Felix.

RCA:

Bitbucket continuous deployment — Azure App Service Deployment Center UX

Since 00:01 UTC on 5 August 2026, customers configuring Bitbucket CI/CD in Deployment Center have been unable to complete the Bitbucket sign-in step. Authorization on the Bitbucket consent page succeeds, but the redirect back to Azure returns an HTTP 404 instead of returning you to the portal.

The cause is a defect in our web server configuration that caused the authorization request's query string to be counted twice against a maximum-length limit, effectively halving it. The defect was latent and harmless until 5 August, when the format of the authorization code issued by Bitbucket changed and grew roughly fourfold, pushing most callbacks past that limit. No change was made on the Azure side that day. Other deployment sources, including GitHub and Azure Repos, are unaffected, and Bitbucket deployments that are already configured continue to build and deploy normally — only new setup and re-authorization are blocked.

We have identified the root cause, developed a fix, and confirmed it in testing. It is currently rolling out to production regions. In the meantime, manual deployment remains available and unaffected.