# SaaS migration PART 2 - Private Links (AZURE, AWS) + encyption (BYOK, CMK)

**URL:** <https://community.dynatrace.com/t/saas-migration-part-2-private-links-azure-aws-encyption-byok-cmk/57156>\
**Category:** Dynatrace Tips\
**Tags:** aws, azure, dynatrace-saas, migration\
**Created:** [October 14, 2026, 3:25pm UTC](https://community.dynatrace.com/t/saas-migration-part-2-private-links-azure-aws-encyption-byok-cmk/57156 "2026-10-14T15:25:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mizso74](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/mizso74/32/41729_2.png) [@mizso74](https://community.dynatrace.com/u/mizso74)\
**Post date:** [October 14, 2026, 3:25pm UTC](https://community.dynatrace.com/t/saas-migration-part-2-private-links-azure-aws-encyption-byok-cmk/57156/1 "2026-10-14T15:25:37Z")

</div>

Hi Folks,

For most organizations (especially financial institutions), security policies mandate the use of private links and the encryption of data using their own keys in the cloud.

Dynatrace offers AWS Private Link (GA) and Azure Private Link (Preview - I hope it will be GA soon).

**AWS Private Link (GA):**

AWS Private Link is well documented:&nbsp;[AWS PrivateLink — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/aws-platform/connect-to-dynatrace-using-aws-privatelink)

**Azure Private Link (Preview):**

Some advantages:

- Monitoring **traffic is always encrypted** — Private Link adds an extra network-isolation layer
- **Reduces your Azure egress traffic costs** since data stays within the Azure backbone
- Provides more stable and predictable connectivity compared to internet-routed traffic

In case of Azure Private Link at the moment you should raise a Support Ticket first with your SaaS tenant ID and your Azure Subscription ID. Official documentation will be published soon and as I saw it is very clear and&nbsp;straitforward. We have already configured it and I can confirm that it is up and running.

High level setps:

Step 1: Support ticket opened → Private Link Service Alias received  
Step 2: Private Endpoint created using the alias  
Step 3: Private DNS Zone configured with A record  
Step 4: DNS resolution verified — private IP confirmed  
Step 5: OneAgent connectivity verified via private endpoint

After the setup your high level route will be in a full Private Link:

OnPremis OA → OnPremis AG → Azure ExpressRoute → Your Azure tenant → Azure Private Link on top of Microsoft Azure backbone → Your Dynatrace SaaS tenant.

OR

AKS OA (in your Azure tenant) → AKS AG&nbsp; (in your Azure tenant) → Azure Private Link on top of Microsoft Azure backbone → Your Dynatrace SaaS tenant.

Here is a high level desgin of an Azure setup:

 ![Mizs_0-1791990825017.png](https://global.discourse-cdn.com/dynatrace/original/3X/b/a/bae8020116685899fc298d3b9446ceecc274601f.jpeg)

Encyption:

**AWS BYOK (GA):**

AWS BYOK is well documented:&nbsp;[Manage AWS encryption keys — Dynatrace Docs](https://docs.dynatrace.com/docs/manage/account-management/settings/encryption-keys)

**Azure BYOK (Planning phase):**

Based on the preliminary information Azure BYOK will be in Preview in 2027 Q2/Q3. IT IS NOT AN OFFICIAL STATEMENT.

I hope with these information you can chose your target platform for the latest Dynatrace.

Best regards,

János

---

<div class="post-metadata">

**Author:** ![fstekelenburg](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/fstekelenburg/32/22029_2.png) [@fstekelenburg](https://community.dynatrace.com/u/fstekelenburg)\
**Post date:** [November 2, 2026, 12:53pm UTC](https://community.dynatrace.com/t/saas-migration-part-2-private-links-azure-aws-encyption-byok-cmk/57156/2 "2026-11-02T12:53:31Z")

</div>

Thank you very much for this valuable information and update.

Question: when setting up Private Link(s) for a customer, does this concern one Private Endpoint or one per Mission Landing Zone (MLZ)?
