Azure Functions sync from remote to local

[jamemoriaty]

[Enter feedback here] My hard disc has crashed. Azure functions were written using Visual Studio Code and deployed to the Azure Functions.

However, right now although I can see all the codes but, I am unable to sync it to my new system in Visual Studio Code.

I am using Consumption Plan, Python in Linux OS.

"Download App Content" is disabled in my account.

Please help me to edit it

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 542c2bdc-5868-71d5-1d1a-a2c6d61744b0
• Version Independent ID: 1bba15a0-227a-8137-a023-90b8df19881b
• Content: Create a Python function using Visual Studio Code - Azure Functions
• Content Source: articles/azure-functions/create-first-function-vs-code-python.md
• Service: azure-functions
• GitHub Login: @ggailey777
• Microsoft Alias: glenga

[RamanathanChinnappan-MSFT]

@jamemoriaty Thanks for your feedback! We will investigate and update as appropriate.

[mike-urnun-msft]

Hello @jamemoriaty - Thanks again for sharing your feedback. The "Download App Content" is disabled likely because the functions were deployed via VS Code, please refer to Download your function app files.

Taking into account Linux on Consumption SKU and assuming that you have opted for the default deployment method in VS Code, which is Zip Deploy, your Python app artifacts are packaged in a .zip file and uploaded to the scm-releases blob container of the storage account that's linked to your function app. Once you navigate accordingly and locate the .zip file, you should be able to download and extract it locally to retrieve your application files. If you run into any issues when trying this out, feel free to make a new post on the MS Q&A channel with the relevant details and we'd be happy to help you there!

Since we didn't determine any changes to this documentation upon reviewing this feedback, we will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.