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(230.39999999999998, 20%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello,
I've been advised by Azure support to raise this issue, although it seems obvious what the issue is from the error message --> "Error: The name "<redacted>-<Redacted>-functions-app" used for the Function App needs to be globally unique and isn't available: Hostname '<redacted>-<Redacted>-functions-app' already exists. Please select a different name."
For context, we have a suite of services that are deployed multiple times a day/week using terraform as our automation tool of choice. Since yesterday one of our test services is no longer deployable because the app name is no longer unique. I understand that the name has to be unique, which is accepted. What is puzzling is that our automation destroys and creates the function-app in what is only a few seconds, so its strange that the app has been registered elsewhere, in addition the name is quite unique so that makes this a bit more puzzling.
For reference this isn't just an issue in terraform, it's not possible to create the function app with the same name via the Azure portal. It's also not possible to reach that addressable name via ping or http. Azure support have advised that they did some cache busting behind the scenes, but it has now been over 24hrs since the app was originally destroyed
Is it possible that the app has not been destroyed fully and is still lurking around in the backend of Azure somewhere?
Thanks
![](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)
anonymous user-7645 Thank you for the question. I will review and get back to you at the earliest.
anonymous user-7645 I would be needing few more details such as name of the function app service, time of the issue, logs/ call stack( if any), runtime stack of the function and the support ticket/incident number etc.
Please refer to : https://github.com/Azure/azure-functions-host/wiki/Sharing-Your-Function-App-name-privately
I can also take it up offline for a closer look and provide a quick and specialized assistance, please send an email with subject line “Attn:Jaya” to AzCommunity[at]Microsoft[dot]com referencing this thread along with the required details: name of the function app service, time of the issue, logs/ call stack( if any), runtime stack of the function and the support ticket/incident number etc.
anonymous user-7645 I haven't heard from you yet. Please share the required information with us. Send an email with subject line “Attn:Jaya” to AzCommunity[at]Microsoft[dot]com referencing this thread along with the required details: name of the function app service, time of the issue, logs/ call stack( if any), runtime stack of the function and the support ticket/incident number etc.
Hello,
I have sent the required email...
Please look for an email that is marked for your attention datetime sent: Mon 14/09/2020 18:17
anonymous user-7645 Thread has been updated with how the issue has been resolved. However, I haven't heard from you. If the answer provided reflects the correct explanation of the resolution, please "accept the answer" and "up-vote" so that it helps others in the community.
anonymous user-7645 We have taken it up offline and checked that the name of the function app was not available even after deleting the site as the request was stuck at our Geo master level. We have internally performed necessary actions to resolve the issue. In similar cases, please reach out to MS support at the earliest.