Cannot create App Service Managed Certificate with error "Only letters and numbers are allowed"

Stewart Rand 71

I am attempting to add a free managed certificate to my app services, but receiving the following error:

Properties.CanonicalName is invalid. Canonical name www-uat.example.com.au includes at least one special character. Only letters and numbers are allowed.

However, I was able to successfully create a certificate in another subscription (same azure region, and naming format [www-prod.example.com.au]) about a week ago, and have previously never had issues requesting certificates with hyphens in the name. I cannot find any documentation or troubleshooting posts mentioning this limitation - has this been changed recently?

The portal shows a green tick when attempting to request, but gives the above error when clicking 'Create'

Hostname eligible for certificate creation. Click Create to create your App Service Managed Certificate.

Deploying via ARM template gives the same error.

Status Message: Properties.CanonicalName is invalid. Canonical name www-uat.example.com.au includes at least one special character. Only letters and numbers are allowed. (Code: BadRequest)

Other variations of this URL format also fail (www-dev.example.com.au, authoring-uat.example.com.au).

Grmacjon-MSFT 18,216 Reputation points

2021-06-15T06:55:06.77+00:00

Thanks for bringing this to our attention @Stewart Rand . This is odd behavior. We will check in with the engineering team to see if there's a fix or a possible workaround for this error and will update this thread

Best,
Grace
06447697 6 Reputation points

2021-06-15T08:45:07.493+00:00

Hi, I'm getting the same issue.
On Friday 11th June (4days ago) I successfully created 6 Webapps with custom domains all with the same format (xxx.dev.xxx-xxx.co.uk) . Yesterday spent all day trying to add another in a slightly different format (extra sub-domain) and kept getting the below error. Finally thought it was something I was doing wrong and rolled it all back but now I cannot re-add the certificate which I added OK on Friday, getting the same error below.

Properties.CanonicalName is invalid. Canonical name xxx.dev.xxx-xxx.co.uk includes at least one special character. Only letters and numbers are allowed.
Grmacjon-MSFT 18,216 Reputation points

2021-06-15T17:21:40.277+00:00

Hello @Stewart Rand and @06447697 I got confirmation from the engineering team that this is a bug. The team is working on a fix but we don't have a sharable ETA at this moment. I will update you as soon as a fix is rolled out. We sincerely apologize for the inconvenience this issue has caused.

We appreciate your patience as we work to resolve this issue.

Thanks,
Grace
Moses Yap 1 Reputation point

2021-06-16T01:02:39.063+00:00

Getting the same error. This seemed to be a rather bad bug since I would guess lots and lots of test URLs would have -dev or -int on them.
Grmacjon-MSFT 18,216 Reputation points

2021-06-16T04:26:59.7+00:00

Hi @Moses Yap ,

We apologize for the inconvenience this issue has caused. The App Service Managed Certificate team is working internally to fix this issue. Thanks for your patience.

-Grace
Anand Srivastava 1 Reputation point

2021-06-16T07:58:40.987+00:00

Even i am getting this issue when trying to create the certificate from "Create App Service Managed Certificates"
Bjarki Heiðar 1 Reputation point

2021-06-16T10:33:56.277+00:00

We are having the same issue. We will be monitoring this issue.
Rob Weber 1 Reputation point

2021-06-16T11:37:16.723+00:00

Hi - we are experiencing an issue with this as well, and has a big impact on us. Please escalate / remedy ASAP.
thanks,
Rob
Klautke Philipp 1 Reputation point

2021-06-16T13:52:54.31+00:00

We also have this error. Please find solution quickly!
R2DHart 1 Reputation point

2021-06-16T15:54:11.13+00:00

Same here. I assumed it was due to a lack of knowledge on my part.
Robert Simmons 11 Reputation points

2021-06-16T20:51:39.673+00:00

Just ran into this as well. Following for updates - we have customers waiting on their SSL certificates.
Shibendra Das 1 Reputation point

2021-06-17T12:00:03.683+00:00

I am not able to create resource group. I am following this link to create a deployment. but got error :
Weblink : https://learn.microsoft.com/en-us/learn/modules/azure-architecture-fundamentals/exercise-create-website

After i reached the template i was using resource group id : learn-d7aa4692-58b0-4850-8636-e3d381b16668

Now i am trying to create resource group it is asking me to register

Can anyone help?
ajkuma 26,216 Reputation points Microsoft Employee

2021-06-18T07:48:57.583+00:00

@Shibendra Das , The issue you posted is not the same as the original issue on this thread, so we request you to create a new forum thread.
// @Grmacjon-MSFT
giovanni.fleres 6 Reputation points

2021-06-18T13:06:19.773+00:00

I also got the same issue since a couple of days
Katrin Dubois 1 Reputation point

2021-06-22T18:58:50.99+00:00

Hello, we have the same problem, Germany West. Can you please let us know when its fixed?
Katrin Dubois 1 Reputation point

2021-06-22T18:59:04.503+00:00

Hello, we have the same problem, Germany West. Can you please let us know when its fixed?
Rich Williams 6 Reputation points

2021-09-01T14:55:37.957+00:00

Hello

1st September 2021

We are also getting this issue with the German umlaut character ü. App service in Germany West Central

Any help will be appreciated

Accepted answer

Grmacjon-MSFT 18,216 Reputation points

2021-06-23T22:33:10.61+00:00

Hello everyone,

This issue is now resolved. The fix has been deployed to every region. Thank you so much for your patience!

Best,
Grace
Please sign in to rate this answer.

1 person found this answer helpful.
Robert Simmons 11 Reputation points

2021-06-24T00:09:02.707+00:00

@Grmacjon-MSFT I am still getting this in a central-us resource group. Tried both through the portal and the Azure CLI.

"Properties.CanonicalName is invalid. Canonical name (something with only a hyphen in it) includes at least one special character. Only letters and numbers are allowed."

Yuta Wakita 6 Reputation points

2021-06-24T02:34:39.497+00:00

Ditto to @Robert Simmons
I still got the same error right now in JapanEast if a CN includes a hyphen.

Benjamin Akhtary 11 Reputation points

2021-06-24T08:06:34.483+00:00

we have same issue with centeral-us. as of jun 24th-2021.

drdamour 16 Reputation points

2021-06-24T15:26:12.017+00:00

confirmed NOT WORKING in us west 2, any ETA?

Grmacjon-MSFT 18,216 Reputation points

2021-06-24T23:17:15.57+00:00

Hi All ( @Robert Simmons , @Yuta Wakita , @Benjamin Akhtary , @drdamour )

Apologies for the inconvenience this issue has caused. it looks like there are still a few more regions the fix is being deployed to. We will keep updating this thread daily with any new updates from the engineering team.

Thanks,
-Grace

Sean 11 Reputation points

2021-06-28T14:03:46.047+00:00

Still happening for me in central-us

ajkuma 26,216 Reputation points Microsoft Employee

2021-06-28T18:38:29.067+00:00

@Sean , The deployment is still in progress for central-us. I'm constantly in touch with our engineering team and I'll post back as soon as I hear from them.

Apologies for the inconvenience!

ajkuma 26,216 Reputation points Microsoft Employee

2021-06-28T19:09:40.663+00:00

@Yuta Wakita , Thanks for your patience. Deployment for JapanEast was completed. Please try to recreate an App Service Managed Certificate for your app(s) and confirm that it is working. if you run into any other issues please let us know.

Jack.Lin 1 Reputation point

2021-06-29T09:10:51.377+00:00

Hi Grace,

We still have the same issue in East Asia, need your help, thank you.

ajkuma 26,216 Reputation points Microsoft Employee

2021-06-29T19:20:04.387+00:00

@Jack.Lin , The deployment is still not complete for East Asia. I'm constantly in touch with our engineering team and I'll post back as soon as I hear from them.

I completely understand the concern, we apologies for the inconvenience this issue has caused.

Erik O'Leary 1 Reputation point

2021-06-29T19:42:56.847+00:00

Why not mark this as 'unresolved' until it actually is so we dont have to dig through the comment tree to see where in the process it is?

Kunal Bhambhani 1 Reputation point

2021-06-29T19:58:56.19+00:00

Hi @Grmacjon-MSFT :
I am trying to create an App Service Managed certificate in East US 2 and still getting the same error.
Region : US East 2
Hostname: www-legacy-dev.<companyname>.com
Error: Properties.CanonicalName is invalid. Canonical name www-legacy-dev.<companyname>.com includes at least one special character. Only letters and numbers are allowed.

Yuta Wakita 6 Reputation points

2021-06-30T07:36:04.57+00:00

Hi @ajkuma ,
I finally succeeded to create a managed cert in Japan East!
Thank you for notifying me.

ajkuma 26,216 Reputation points Microsoft Employee

2021-06-30T12:26:56.37+00:00

@Yuta Wakita , Glad you were able to create the certificate fine. Thanks for the update.

R2DHart 1 Reputation point

2021-06-30T12:58:07.027+00:00

Still getting this error in South Central US as well. :(

ajkuma 26,216 Reputation points Microsoft Employee

2021-06-30T13:03:39.063+00:00

@Kunal Bhambhani , The deployment to East US 2 was expected to complete by now. I'll confirm on this and follow-up. Apologies for the delay and all the inconvenience.

Robert Simmons 11 Reputation points

2021-06-30T13:16:41.367+00:00

@Grmacjon-MSFT Central-US is working now too.

Grmacjon-MSFT 18,216 Reputation points

2021-06-30T19:39:48.633+00:00

Thanks for confirming @Robert Simmons !

Grmacjon-MSFT 18,216 Reputation points

2021-06-30T20:01:32.48+00:00

Hi @Kunal Bhambhani , can you please try again? the deployment to East US 2 is now complete.

Thanks,
Grace

Sean 11 Reputation points

2021-06-30T21:11:34.307+00:00

central-us is working. Have created a number of certificates with dash in sub-domain

Jack.Lin 1 Reputation point

2021-07-01T01:41:30.213+00:00

Confirmed it works in East Asia, thank you.

ajkuma 26,216 Reputation points Microsoft Employee

2021-07-01T06:07:38.923+00:00

@Sean , Glad you were able to create the certificate fine. Thanks for the update.

Again, we appreciate your patience through this.

ajkuma 26,216 Reputation points Microsoft Employee

2021-07-06T17:55:41.793+00:00

The deployment was complete in all the regions. In case, anyone is still seeing this issue. Please let us know. We will follow-up with you immediately.

Once again, I completely understand this issue was frustrating and we sincerely apologies for all the inconvenience this has caused.
Please be rest assured we have also relayed the feedback to our product engineering team.
Sign in to comment

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

5 additional answers

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

Cannot create App Service Managed Certificate with error "Only letters and numbers are allowed"

5 additional answers

Your answer