This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 13%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESV%3C/text%3E%3C/svg%3E)
In the azure portal , when creating a function app with 60 characters in it's name, the creation wizard allows it to be deployed, but the deployment fails with the error:
"There was a conflict. The remote server returned an error: (400) Bad Request.".
I understand that the limit is maximum 59 characters. When you put 59 characters in the function app name, it deploys successfully. When you put in 61 or more characters, the Wizard disallows the deployment with the error: "The name must be fewer than 60 chars".
This issue seems to be specifically with 60 character function app names being allowed through the wizard's verification process, but failing to deploy. It should probably just display the same error as 61+ chars, and disallow deployment.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 68%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Hello @Steven Vernon , Welcome to QnA.
Please confirm : Whenever you are trying to deploy the function with 60 chars you are getting the error "There was a conflict. The remote server returned an error: (400) Bad Request"? or it was just one time?
Is your main concern the error-message verbatim?
@JayaC-MSFT In a way, yes it is the verbatim, but more importantly, the issue is the function creation wizard (for lack of better term) does not disallow the deployment of 60 character names, as it does with function apps with 61 or more characters. You get the "bad request" error every time you attempt to deploy with 60 characters, but not with 61 or more characters, because the deployment cannot be started with 61 or more characters.
If the function app name must be limited to less than 60 characters, then the creation wizard should disallow deployments of 60 character function app names with the same message it uses for 61 or more characters: "The name must be fewer than 60 chars". The error for 60 characters makes it seem like the issue is something other than a naming convention issue, because azure attempts to deploy and fails with the "bad request" error.
You can reproduce the following:
Create Function app with 61+ char name: fails to verify and wont deploy. - "The name must be fewer than 60 characters"
Create Function app with 60 char name: allows deploy but deployment fails with 400 error:"There was a conflict. The remote server returned an error: (400) Bad Request." Create Function app with 59- char name: Deploys successfully as expected.
Hello @Steven Vernon , Apologies for the delay. I had replicated the issue and highlighted the issue to our core product team. However, I would encourage you to provide a feedback to User Voice and upvote it so that this gets traction.
If this answer helped, please "Accept the answer" and "Up-vote" so that it helps others in the community.