Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
The most likely cause is that the Bitbucket authorization or stored repository metadata in App Service Deployment Center has become invalid, so the backend can no longer list branches and shows “Failed to fetch”. A similar issue is documented for Azure Repos where the stored repo URL/authorization became invalid and re‑authorizing fixed it.
Use these steps to recover:
- In the Web App → Deployment → Deployment Center → Settings page, disconnect the existing Bitbucket configuration completely (remove the source control connection rather than just changing the branch).
- Save the Web App configuration.
- In the same Deployment Center blade, configure the source again:
- Choose Bitbucket as the source.
- When prompted, re‑authorize Bitbucket access (OAuth). Ensure the account has access to the organization and repository.
- Re‑select the organization and repository; the branch list should now populate correctly.
- If the problem persists for this app only, delete and recreate the Deployment Center configuration again after some time to clear any stale metadata.
- If multiple apps are affected or re‑authorization does not help, configure CI/CD from Azure DevOps Pipelines (using a Bitbucket service connection) instead of Deployment Center, because Deployment Center can keep stale repo URL metadata and fail to read branches.
If none of the above resolves the issue, open a support ticket so that the backend configuration for the Deployment Center can be checked for an invalid or corrupted repo URL.
References: