Let my app name be MyApp. When I invoke my app directly by typing "myApp.AzureWebsites.net", it works. However, when I use my app service domain, e.g., myAppDomainName.com, it does not work. In the DNS record for the above service domain, myApp.AzureWebsites.net was assigned to the CNAME. But when I invoke my app using the service domain name, ie, by typing "myAppDomainName.com", it fails with the following message: 404 Web Site not found. ... Custom domain has not been configured inside Azure ... Clear the cache by running the command ipconfig/flushdns. I already ran ipconfig/flushdns I successfully_. And_ I already assigned myApp.AzureWebsites.net to the CNAME. It used to work in 2022 (last year). I thought a custom domain was a domain name requiring a certificate. The above domain name (myAppDomainName.com) was purchased from Azure directly a few years back, and has no certificate, thus I do not thing it is a custom damain. Am I wrong? Please help, I appreciate very much.

Hi, In portal, please browse to your web app -- Custom domains blade, and make sure that myappdomainname.com is shown there and it has Secured in status column. If it doesn't you need to add domain and binding as needed until it says secured. Once you have it listed there as Secured it should work fine. Please click Accept Answer and upvote if the above was useful. Thanks. -TP

Hi TP, Looks like everything much better today other than that Issuance Pending, which is harmless so far. (1) Up until late yesterday, when I checked the Key Vault status (by going to the certificate page and press Certificate Configuration on the left panel, then click the square for the Step 1: Store , then check the Key Vault status for the Key Vault value I created), I got the error message "Failed to link certificate with the selected key vault value. ... The parameter KeyVaultCsmid has an invalid value ". But today, it works. It accepts the Key Vault value I created, and displays the certificate subscription ID. (2) Going to the page for MyApp --> Certificates, pressing the Details gives the matching Subscription ID of mine. Thanks so much for your continuous and persistent help, Gwan

My App Service Domain Name Does Not Work

Accepted answer

TP 100.1K Reputation points

2023-10-30T01:00:34.6466667+00:00

Hi,

In portal, please browse to your web app -- Custom domains blade, and make sure that myappdomainname.com is shown there and it has Secured in status column. If it doesn't you need to add domain and binding as needed until it says secured. Once you have it listed there as Secured it should work fine.

Please click Accept Answer and upvote if the above was useful.

Thanks.

-TP
Please sign in to rate this answer.

1 person found this answer helpful.
Gwan Lie 20 Reputation points

2023-10-30T03:16:42.0533333+00:00

Hi TP,

Thanks for your answer. I followed your advice:

(1) Buy a TSL/SSL certificate for the custom domain,

(2) Add the custom domain name to my app.

However, after waiting for a while, the certificate status is still "Pending Issuance", so it has not worked yet.

I will let you know as soon as it works.

Appreciate your help,

Gwan

Gwan Lie 20 Reputation points

2023-10-30T03:34:21.4833333+00:00

Hi TP,

My TSL/SSL status is still "Pending Issuance". However, I expect your answer to work.

So I contingently clicked "Accept answer".

Thanks,

Gwan

TP 100.1K Reputation points

2023-10-30T05:14:03.2566667+00:00

@Gwan Lie If it still says Pending Issuance it may be waiting for you to verify domain ownership. Please see article below:

https://learn.microsoft.com/en-us/azure/app-service/configure-ssl-app-service-certificate

Gwan Lie 20 Reputation points

2023-10-30T23:49:36.06+00:00

Hi TP,

Thanks again for your additional suggestion.

However, problems remain:

(1) I created Key Vault value for the certificate (By going to the certificate page and press Certificate Configuration on the left panel, then click the square for the Step 1: Store. Then I check the Key Vault status for the Key Vault value I created, and got the error message "Failed to link certificate with the selected key vault value. ... The parameter KeyVaultCsmid has an invalid value". But I did not specify the KeyVaultCsmid. I only chose a name for the key valult which was accepted.

(2) However, by this time, although my certificate status was still "Issuance Pending", when I went to the page for MyApp and click "Add Custom Domain", MyAppDomainName.com was shown already "Secured".

(3) Encouraged, I did the Step 2 Verify for the certificate. I clicked "Domain Verification" and MyAppDomainName.com was there. I also clicked "Manual Verification" (What is this for? Should I do this?), and followed the suggestion of adding a TXT name value pair (@ as the name and a given value) to the root domain. I added this name value pair to MyApp page. (My understanding is MyApp is the root domain?) This seems has no effect.

(4) I did the Step 3 Assign for the certificate. On the page for MyApp and clicked Settings:

(a) Clicked Custom domains and found MyAppDomainName.com was already secured and binding,

(b) Clicked certificates and found MyAppDomainName.com was there with the status "No action needed".

All seems well but why my certificate status is still Issuance Pending?

Appreciate your great help,

Gwan

TP 100.1K Reputation points

2023-10-31T03:55:31.06+00:00

Hi Gwan,

I suspect you are using free App Service Managed certificate for you web app, which is fine for many cases, however, my guess is additionally you purchased a certificate (which you may not need), and that is what is "Pending Issuance".

Please confirm:

If you browse to your myappdomainname.com site using Chrome/Edge, does it display fine with lock symbol to indicate it is using https?

In portal, navigate to your web app, Certificates blade -- Managed certificates tab. Do you see certificate listed with myappdomainname.com domain? If yes, make a note of precise Certificate Name shown. Now click on Custom domains blade. Next to myappdomainname.com click on Actions context menu and select Update binding. Check what it says for Certificate, does this precisely match the Certificate Name that was on the Certificates blade? If yes, this means you are using free app service managed certificate. Click Cancel button to exit the Update binding screen.

If you are unsure about something I wrote above let me know and I'll explain more and/or provide screenshot.

Thanks.

-TP

Gwan Lie 20 Reputation points

2023-10-31T04:50:27.9133333+00:00

Hi TP,

Many thanks for continuously helping.

(1) Does it display lock symbol? Yes, it does.

(2) Going to MyApp certificate blade, the listed certificate name is the concanetation of MyAppDomainName.com and MyApp connected by a hyphen (-), ie, MyAppDomainName.com-MyApp.

Going to MyApp Custom domain blade and click on Action context menu, after selecting Update Binding, in the dropdown window, the only certificate choice available is the same as above, with an expiration date the same as my purchased certificate (expires in 1 year).

Question: From the expiration date, it looks like the certificated used is the one I purchased, but is it? Why does not it use my certificate name? If the certificate name is not used, what is its name for?

Thanks,

Gwan

TP 100.1K Reputation points

2023-10-31T05:48:01.52+00:00

If expiration date is in 1 year, that is purchased certificate. Free app service managed certificates expire in 6 months.

The certificate name it shows is the "friendly name", which is not the same as the subject or alternative names on the certificate itself.

From your descriptions it sounds like things are configured properly, however, if it still says "pending issuance" over on your app service certificate I don't know why that is.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

My App Service Domain Name Does Not Work

1 additional answer

Your answer