Unclear error message shows when deployment fails due to mismatched TargetPort in “Deploy to Container App with Copilot”

[v-ruizh]

OS: Win 11
Build Version: 20260118.1
Regression: Not a Regression

Repro Steps:

1. Right-click a container app and select "Deploy to Container App with Copilot...".
2. In the Summary view, note that the default Target Port is set to 80 (while the container listens on 3000).
3. Don't change any item and click "Confirm" to start deployment -> Fail to deploy with an error.
4. Check whether the error message is clear or not.

Expect:
The deployment failure should surface a clear and actionable error message, such as “The TargetPort 80 does not match the listening port 3000” in Azure portal.

Actual:
The deployment fails with a generic timeout message.

More Info:
This issue also reproduces when executing "Deploy to Container App..." command.

[MicroFish91]

So we can't do any pre-verification because this is deployment of an existing image, i.e. we have no dockerfile to inspect and there is not any metadata that I'm aware of that allows us to inspect an image to gather this info. The port 80 is likely from the initial quick start image that the container app spins up with.

Normally I would expect us to be able to catch this at the verification step at the end, but for some reason this error is causing our polling for the revision id to time out. This presents us with a good opportunity to see if there's any fallback we can add if our polling logic times out to see if we can still determine the revision id of the latest deployment so we can fetch logs for the user.