Skip to main content
Community Hub
TL;DR

Connect Atlan to an SAP ECC application server over Azure Private Link, so RFC traffic stays on the Azure network.

Your AI can read this via Docs MCPcurl -fsSL "https://docs.atlan.com/install-docs-mcp" | bashConnect

Set up Azure private network link to SAP ECC

Connect Atlan to an SAP ECC application server over Azure Private Link, so RFC traffic stays on the Azure network. The setup runs in five phases. For who owns each phase and how long it takes, see Private network link FAQ.

How Atlan connects to SAP ECC

Before you set up a private link, read How Atlan connects to SAP ECC. It compares the connectivity methods, lists the connection options each supports, and explains how private connectivity works.

Prerequisites​

  • Chosen a private link as your connectivity method. See How Atlan connects to SAP ECC.
  • Your Azure administrator available to complete most of these steps, and your SAP Basis team available to confirm the application server details.
  • Your Atlan tenant hosted on Azure. For an Atlan tenant on AWS, see Set up AWS private network link to SAP ECC.
  • An SAP ECC application server in an Azure VNet that you control. A private link connects to an application server, so you crawl with Connection Type set to Application Server. For every method's options, see Supported connection options.
  • Your SAP system number (NN). The connector derives the gateway port 33NN from the system number, so the load balancer must listen on that same port number.
  • Someone with Contributor or Owner on the resource group, who can create load balancers and Private Link Services.
  • From Atlan, through a support request: your tenant's Azure region and Atlan's Azure subscription ID.
Ports in this guide

This guide uses 33NN, where NN is your SAP system number. For system number 00, that's port 3300.

Phase 1: Publish application server​

Owner: Your cloud/network team

Azure Private Link Service requires a Standard SKU load balancer. The load balancer, the Private Link Service, and the application server's VNet must be in the same region.

Create internal load balancer​

  1. In the Azure portal, go to Load balancers and click Create.
  2. Set SKU to Standard and Type to Internal, in the application server's VNet and region.
  3. Add a frontend IP configuration with a static private IP.
  4. Under Back-end pools, add the application server's NIC or IP address.
  5. Under Health probes, add a probe with protocol TCP and port 33NN.
  6. Under Load balancing rules, add a rule with protocol TCP, frontend port 33NN, backend port 33NN, your back-end pool and health probe, and Floating IP set to Disabled.
  7. Confirm the health probe shows the application server as Healthy before you continue.
  1. Go to Private Link Center > Private link services and click Create.
  2. Select the resource group, then select your load balancer and its frontend IP configuration.
  3. Choose a subnet for the service's NAT IP addresses. Disable private link service network policies on that subnet if Azure prompts you to.
  4. Optionally, add Atlan's subscription ID under Visibility and Auto approval. Azure then approves Atlan's connection without a manual step.
  5. Click Review + create, then Create.
  6. Open the Private Link Service and copy its Alias, in the format <pls-name>.<guid>.<region>.azure.privatelinkservice.

Azure translates incoming private link traffic to the Private Link Service's NAT IP addresses. On the application server's network security group, add an inbound rule that permits TCP 33NN from the NAT subnet you chose. If the application server runs a host firewall, permit the same range there.

Phase 2: Share details with Atlan​

Owner: You

Raise a support request and include everything in one message:

  • Your Atlan tenant URL.
  • That the link is for SAP ECC.
  • The Private Link Service alias.
  • The Azure region of the Private Link Service.
  • The gateway port, 33NN.
  • The role on your side that approves the connection.

Phase 3: Atlan builds its endpoint​

Owner: Atlan support

Atlan creates a private endpoint in its subscription that targets your Private Link Service alias. This usually takes one to two business days. Atlan support tells you when the connection is waiting for your approval, and the name of the private endpoint to look for.

Phase 4: Approve connection​

Owner: Your cloud/network team

  1. Go to Private Link Center > Private link services and open your service. If you added Atlan's subscription under Auto approval, the connection is already approved.
  2. Click Private endpoint connections, select the pending connection whose name matches the one from Atlan support, and click Approve.
  3. Confirm the connection state changes to Approved, then reply on your support request.

Atlan support then sends you the endpoint hostname to use in the crawler.

Phase 5: Connect and verify​

Owner: You, in Atlan

When you crawl SAP ECC, choose the Direct extraction method and set:

  • SAP Host Name: The endpoint hostname from Atlan support. Don't use the Private Link Service alias or the application server's own hostname.
  • Connection Type: Application Server.
  • SAP System Number: Your SAP system number. The connector derives port 33NN from it.

Then click Test Authentication.

Success checklist​

  • The private endpoint connection shows Approved.
  • The load balancer health probe shows the application server as Healthy.
  • Test Authentication passes in Atlan.
  • Preflight checks pass.
  • A crawl scoped to one small component completes.
  • A full crawl completes.

Troubleshooting​

If the connection fails, see Troubleshooting SAP ECC private network link for each error, its cause, and its solution.

See also​