Carry existing Default Domain to a new Container App

Question

We have a app currently deployed as Azure App Service (web app), and we plan to move it to Container App instead in the near future.

However, one of our concern is:- there are some client applications connecting to our app using the Default Domain (xxxx.azurewebsites.net). Those client applications are deployed everywhere and not under our full control. Hence it's a big challenge for a transition with minimal impact to our clients, its impossible for us to update those clients' target URL all at the same time.

We are exploring that, is it possible the Default Domain used by the current App Service, will be switchover to the new Container App? By then the client apps don't have to update the target URL, and able to connect to our app deployed as Container App.

Please advise.

Answer 1

Hi @John Wong Yek Hon Greetings! Thank you for posting this question here.

Azure container app lets you assign a custom domain name to the app instance. However, during the set up of a custom domain, you most likely would not be able to use the default domain name of the Web app. The domain name xxxx.azurewebsites.net is managed by Azure and is tied to the specific Azure App Service instance. This cannot be set as a custom domain on container app.

You would have to change the end points to configure to the new container app end point.

Going forward, consider using an Azure API instance as you change the architecture. Following this approach, you can have the client applications to hit the end point managed by APIM instance and let APIM forward the request to Container App. If you decide to change the backend, you would not have to change the client applications. Please refer the documentation Import an Azure Container App as an API