Share via

Error when configuring CD in Deployment Center of Web App ("Expected https or SSH format...")

Magnus 20 Reputation points
2025-11-18T12:59:19.99+00:00

I have a Dotnetcore - 8.0 web app running that I've been building from an Azure DevOps repo through the CD option in the Deployment Center. It is in a production slot and there is a warning that this is not recommended but it has nevertheless been working well. That is, until yesterday when the following error started consistently showing up, regardless of which branch of the repo I choose to base it on:

Failed to set up deployment: Repository 'UpdateSiteSourceControl' operation failed with Invalid RepoUrl format. Expected https or SSH format..

Just so there's absolutely no misunderstanding, this configuration lives here:

Web App -> Deployment -> Deployment Center -> Settings -> Source -> Azure Repos

And then when I choose whatever branch of the repo, which has worked every time before, it returns the error above. Even for branches that haven't been changed at all for a long time.

If anyone has any insight, I'd be very grateful.

Azure App Service
Azure App Service

Azure App Service is a service used to create and deploy scalable, mission-critical web apps.


Answer recommended by moderator

  1. Alex Burlachenko 20,665 Reputation points MVP Volunteer Moderator
    2026-02-16T08:32:45.1833333+00:00

    hi,

    this error usually appears when the repo url stored in deployment center becomes invalid or corrupted even if u are selecting azure repos from the ui. The message expected https or ssh format means the backend api is receiving a repo url that is empty malformed or not in a recognised format like https://dev.azure.com/... or ******@ssh.dev.azure.com:... and app service refuses to save it.

    this was working before and suddenly fails without branch changes it is often caused by a change in the devops project permissions token scope or service connection rather than the branch itself.

    go to deployment center and completely disconnect the source control instead of just changing the branch, save it, reconnect fresh to azure repos and reauthorise access when prompted so the repo url and token are regenerated. is the devops repo was renamed moved to another project or the organisation url changed coz even subtle changes like switching from visualstudio.com to dev.azure.com format can break the stored repo url. if the issue persists try configuring cd using a service connection through azure devops pipeline instead of deployment center because deployment center sometimes keeps stale repo metadata in the site config.

    this is almost always a repo url metadata issue or expired authorisation rather than a dotnet or slot problem.

    rgds,

    Alex

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.