Articles in this section
Category / Section

Preventing Errors When Disconnecting an Old Repository and Branch in Azure App Service Deployment Center

Published:

This Knowledge Base article provides guidance on avoiding common errors that occur when disconnecting an old repository and branch in the Azure App Service Deployment Center. These errors typically arise if the old deployment source is not fully removed or if remnants of the previous configuration persist, leading to conflicts when setting up a new deployment source.
By following the steps outlined below, you can ensure the old deployment is properly deleted, verify the disconnection through logs, and successfully configure a new repository and branch without encountering issues.

Disconnect the Old Deployment Source

  1. Navigate to your App Service in the Azure portal.
  2. Stop the running app service.
    image.png
  3. Select Deployment Center from the left menu.
  4. On the Settings tab, click Disconnect.
  5. Confirm by selecting OK.

Verify Disconnection and Check Logs

To ensure the old deployment is fully deleted and no conflicts remain:

  1. In the Deployment Center, switch to the Logs tab.
    image.png
  2. Review the deployment history:
    • Look for any active, pending, or failed deployments related to the old repository.
    • If any pending deployment found please manually delete the deployment
      image.png
    • Confirm there are no recent entries indicating ongoing syncs or errors from the old source.
    • If logs show “No deployments” or are empty, this is a good sign that the old source is disconnected, or wait for some time for logs to show “No deployments” or be empty.
      image.png

Configure the New Deployment Source

Once disconnection is verified:

  1. Return to the Deployment Center > Settings tab.
  2. Select your new source (e.g., GitHub, Azure Repos).
  3. Authorize the connection, choose the repository and branch, and save.
    image.png
  4. Trigger a manual sync if needed: On the Logs tab, use the Sync option to deploy from the new source.
  5. Monitor the Logs tab for successful deployment confirmation.
    image.png
  6. Start the app service and access the application.
Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
SJ
Written by Sarulatha Jagadesan
Updated:
Comments (0)
Please  to leave a comment
Access denied
Access denied