Azure
Azure Functions Core Tools does not support this deployment path. Please configure the app to deploy from a remote package using the steps here: https://aka.ms/deployfromurl
Version
Azure Functions Core Tools does not support this deployment path. Please configure the app to deploy from a remote package using the steps here: https://aka.ms/deployfromurl
python runtime
Suddenly im having a brand new bug! As every azure function bug, almost impossible to debug! NOT a single metion to how to fix this bug in the docs!
keep doing this grat job team, 10% gain, 90% pain !!!!
Description
Azure Functions Core Tools does not support this deployment path. Please configure the app to deploy from a remote package using the steps here: https://aka.ms/deployfromurl
Suddenly im having a brand new bug! As every azure function bug, almost impossible to debug! NOT a single metion to how to fix this bug in the docs!
keep doing this grat job team, 10% gain, 90% pain !!!!
Steps to reproduce
Azure Functions Core Tools does not support this deployment path. Please configure the app to deploy from a remote package using the steps here: https://aka.ms/deployfromurl
Suddenly im having a brand new bug! As every azure function bug, almost impossible to debug! NOT a single metion to how to fix this bug in the docs!
keep doing this grat job team, 10% gain, 90% pain !!!!
Thanks god we now have "Ask Learn"!!!!
how i fix this? Azure Functions Core Tools does not support this deployment path. Please configure the app to deploy from a remote package using the steps here: https://aka.ms/deployfromurl
Ask Learn AI-generated content may be incorrect Sorry, I can’t help with this. Please make a new request or share your feedback.
Oh, but luckly, we have the visual studio extension!
2:42:07 PM integracion-meli: You can report issues at https://github.com/Microsoft/Oryx/issues 2:42:07 PM integracion-meli: Oryx Version: 0.2.20230210.1, Commit: a49c8f6b8abbe95b4356552c4c884dea7fd0d86e, ReleaseTagName: 20230210.1 2:42:07 PM integracion-meli: Build Operation ID: 9d26fc97c4003694 2:42:07 PM integracion-meli: Repository Commit : afe969f9-15cd-481f-87de-c705f998c947 2:42:07 PM integracion-meli: OS Type : bullseye 2:42:07 PM integracion-meli: Image Type : githubactions 2:42:07 PM integracion-meli: Detecting platforms... 2:42:07 PM integracion-meli: Detected following platforms: 2:42:07 PM integracion-meli: python: 3.12.11 2:42:08 PM integracion-meli: Version '3.12.11' of platform 'python' is not installed. Generating script to install it... 2:42:08 PM integracion-meli: Source directory : /tmp/zipdeploy/extracted 2:42:08 PM integracion-meli: Destination directory: /home/site/wwwroot 2:42:08 PM integracion-meli: Downloading and extracting 'python' version '3.12.11' to '/tmp/oryx/platforms/python/3.12.11'... 2:42:08 PM integracion-meli: Detected image debian flavor: bullseye. 2:42:20 PM integracion-meli: Syncing triggers... 2:42:23 PM integracion-meli: Querying triggers... 2:42:27 PM integracion-meli: No HTTP triggers found.
and if you think this error is beacuse the code is failing on startup, this is te default template created with the extension....
Solved.
First, normal consumption plan wont work with funcapp publish, it would be nice if you add support to it.
Second, in some tenants, or some suscriptions, i dont know, the storage account and the file share to store the azurefunction code, is not created automatically. So env vars corresponding to that storage account are missing, resulting in:
2:42:20 PM integracion-meli: Syncing triggers... 2:42:23 PM integracion-meli: Querying triggers... 2:42:27 PM integracion-meli: No HTTP triggers found.
So, IT WOULD BE SO DIFFUCLT TO ADD 1 LINE LOG PLEASE?
2:42:20 PM integracion-meli: Syncing triggers... 2:42:23 PM integracion-meli: Querying triggers... 2:42:27 PM integracion-meli: No HTTP triggers found. 2:42:27 PM integracion-meli: MAKE SURE YOU HAVE A F*** STORAGE ACCOUNT BEACUSE WE FOUND ... MISSING VARIABLES
I'm glad to hear you found and resolved your issue. It appears this was caused by missing environment variables to the underlying storage account in your Azure Function App deployment.
While the CLI itself can’t detect what’s missing in the deployed app (we just use az cli under the covers), we could add a log if there is a deployment error to let you to check for things like a missing environment/storage. This should hopefully make it easier to debug problems like this. We’ll keep this issue open to track that logging improvement.
My friend, the issue is not even close to beeing solved. Im currently having the SAME ISSUE AGAIN, this time, environment variables wont fix it. I tried to deploy with my bicep template, where i had all the environment variables that the functionapp needs. (This same is deploy is working on 3 azure different tenants) The deploy fails saying that the subscription has no Dynamic VMs cuota available. using the new dynamics functions sku, THAT I SPEND A WEEK MIGRATING ALL MY CLIENTS TO, BECAUSE YOU DEPRECEATED THE CONSUMPTION PLAN. so, i have created the function manually in the portal. all variables set.
Host status: {"id":"dafb12ca38fb5aaf7ce63eb7f44ca007","state":"Running","version":"4.1044.300.0","versionDetails":"4.1044.300-dev.0.0+a9abdf3664d00a7b7c4bc9e5b20ba7af07c9f201","platformVersion":"","instanceId":"0--3c33fb82-36e8-4763-9189-151c89e2b43f","computerName":"","processUptime":3237280,"functionAppContentEditingState":"NotAllowed","extensionBundle":{"id":"Microsoft.Azure.Functions.ExtensionBundle","version":"4.28.0"}} [2025-10-28T14:27:28.590Z] The deployment was successful! Functions in meli-integration-func-tqla:
On Thu, Oct 23, 2025 at 8:11 PM Lilian Kasem @.***> wrote:
liliankasem left a comment (Azure/azure-functions-core-tools#4617) https://github.com/Azure/azure-functions-core-tools/issues/4617#issuecomment-3439658653
I'm glad to hear you found and resolved your issue. It appears this was caused by missing environment variables to the underlying storage account in your Azure Function App deployment.
While the CLI itself can’t detect what’s missing in the deployed app (we just use az cli under the covers), we could add a log if there is a deployment error to let you to check for things like a missing environment/storage. This should hopefully make it easier to debug problems like this. We’ll keep this issue open to track that logging improvement.
— Reply to this email directly, view it on GitHub https://github.com/Azure/azure-functions-core-tools/issues/4617#issuecomment-3439658653, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCKMLKYV6J6DVYUQFOASWVD3ZFOB7AVCNFSM6AAAAACEYKVEACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMZZGY2TQNRVGM . You are receiving this because you authored the thread.Message ID: @.***>
Hi, @TomasCaruso10, your comment violates the Microsoft Open Source Code of Conduct, which requires all participants to engage respectfully and constructively. Profanity and aggressive language are not acceptable in the repositories we manage.
We value feedback and understand the frustration, but communication must remain professional and focused on improving the product. This issue will be removed due to the inappropriate language. I'm redacting and locking the issue. Please review the Code of Conduct before participating further.
Thank you for understanding.
