# Re-route Azure App Service and AKS monitoring data to a new SaaS tenant without reinstallation and App downtime

**URL:** <https://community.dynatrace.com/t/re-route-azure-app-service-and-aks-monitoring-data-to-a-new-saas-tenant-without-reinstallation-and-app-downtime/51182>\
**Category:** Cloud platforms\
**Tags:** installation, azure, oneagent, kubernetes\
**Created:** [April 11, 2025, 7:34am UTC](https://community.dynatrace.com/t/re-route-azure-app-service-and-aks-monitoring-data-to-a-new-saas-tenant-without-reinstallation-and-app-downtime/51182 "2025-04-11T07:34:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DynaQ](https://avatars.discourse-cdn.com/v4/letter/d/96bed5/32.png) [@DynaQ](https://community.dynatrace.com/u/DynaQ)\
**Post date:** [April 11, 2025, 7:34am UTC](https://community.dynatrace.com/t/re-route-azure-app-service-and-aks-monitoring-data-to-a-new-saas-tenant-without-reinstallation-and-app-downtime/51182/1 "2025-04-11T07:34:41Z")

</div>

Hello,

We have integrated Dynatrace SaaS with a Linux-based App Service and an Azure Kubernetes cluster (Dynatrace Operator), and we had a requirement to move the workloads to a totally new SaaS tenant.

Do we have an option to reconfigure the OneAgent change the target tenant and tokens without the need to uninstall and reinstall the OneAgent/Operator and restart the applications? Does the oneagentctl command work with App Services and AKS?

Thanks,

DynaQ

---

<div class="post-metadata">

**Author:** ![yanezza](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/yanezza/32/5036_2.png) [@yanezza](https://community.dynatrace.com/u/yanezza)\
**Post date:** [April 12, 2025, 5:01pm UTC](https://community.dynatrace.com/t/re-route-azure-app-service-and-aks-monitoring-data-to-a-new-saas-tenant-without-reinstallation-and-app-downtime/51182/2 "2025-04-12T17:01:22Z")

</div>

Hi,

In AKS, you need to remove and re-apply the Dynakube with the proper&nbsp;apiUrl&nbsp;and token (and remove secret too - [here](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/guides/migration/migrate-dto-to-tenant) the guide).  
This will restart the OneAgents, and you will also need to restart your monitored application pods to allow the new tenant’s OneAgent modules to be injected.

In Azure App Services, you need to change the startup script/commands to point to the new tenant. You can find more information here: [Integrate OneAgent on Web App for Containers. After that, you need to restart your app service.](https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-appservice/integrate-oneagent-on-web-app-for-containers#install--built-in-image)

oneagentctl will not works in these two scenario.