# Install netdata on an azure web app instance

**URL:** <https://community.netdata.cloud/t/install-netdata-on-an-azure-web-app-instance/3607>\
**Category:** Help\
**Tags:** cloud, installation, agent\
**Created:** [December 6, 2022, 10:25am UTC](https://community.netdata.cloud/t/install-netdata-on-an-azure-web-app-instance/3607 "2022-12-06T10:25:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nifle](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Nifle](https://community.netdata.cloud/u/Nifle)\
**Post date:** [December 6, 2022, 10:25am UTC](https://community.netdata.cloud/t/install-netdata-on-an-azure-web-app-instance/3607/1 "2022-12-06T10:25:26Z")

</div>

## Problem/Question

I would like to install netdata on an Azure Web App instance but as soon as i restart the web app, netdata disappears because only the /home dir is persistant.

## Environment/Browser/Agent’s version etc

I’m using a linux Web App.

## What I want to happen

I would like to know how to install everything needed for netdata and netdata itself in the home folder so that it remains where it is and it remains the same node.

---

<div class="post-metadata">

**Author:** ![Christopher\_Akritid1](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/christopher_akritid1/32/419_2.png) [@Christopher\_Akritid1](https://community.netdata.cloud/u/Christopher_Akritid1)\
**Post date:** [December 7, 2022, 4:17pm UTC](https://community.netdata.cloud/t/install-netdata-on-an-azure-web-app-instance/3607/2 "2022-12-07T16:17:34Z")

</div>

Hi @Nifle and welcome to the community!

Try running kickstart with `--build-only --install-prefix "/home"`. Please let us know if it does solve the issue, as we’ll need to update the docs if it does, to make it clear.

---

<div class="post-metadata">

**Author:** ![Nifle](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Nifle](https://community.netdata.cloud/u/Nifle)\
**Post date:** [December 7, 2022, 5:05pm UTC](https://community.netdata.cloud/t/install-netdata-on-an-azure-web-app-instance/3607/3 "2022-12-07T17:05:41Z")

</div>

I get this error even after doing it again as it says

 ![image](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/2X/d/d225b6a7e084053d8424dc1a0f26da7d09a93031.png)

---

<div class="post-metadata">

**Author:** ![Christopher\_Akritid1](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/christopher_akritid1/32/419_2.png) [@Christopher\_Akritid1](https://community.netdata.cloud/u/Christopher_Akritid1)\
**Post date:** [December 8, 2022, 4:57pm UTC](https://community.netdata.cloud/t/install-netdata-on-an-azure-web-app-instance/3607/4 "2022-12-08T16:57:37Z")

</div>

Looks like you can’t directly connect agents running on Azure Web Apps to cloud, so you’ll need to run kickstart with `--disable-cloud`.

Not to worry though, you can have a parent Netdata on some other node and have the Netdata instances running on the ephemeral webapps act as children, streaming their data to that parent. It’s best practice anyway, see [Why is data replication important? | Netdata Blog](https://blog.netdata.cloud/why-is-data-replication-important/)  
Then you can claim just the parent and not have to worry about persistence in the children, as the parent will have its own persistent storage.

Someone will check if there’s anything we can do from our side to allow the agent-cloud link (ACLK) to work there as well, but the error doesn’t look promising.

---

<div class="post-metadata">

**Author:** ![Nifle](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Nifle](https://community.netdata.cloud/u/Nifle)\
**Post date:** [December 8, 2022, 6:48pm UTC](https://community.netdata.cloud/t/install-netdata-on-an-azure-web-app-instance/3607/5 "2022-12-08T18:48:26Z")

</div>

ok thanks for helping
