Clarify Databricks networking restrictions vs Private Link guidance

[aboitreaud]

What does this PR do? What is the motivation?

We rolled out a Databricks private link support solution and realized that there was an incorrect API IP allowlisting required un our docs page.
This PR refreshes the guidelines for Databricks Private Link and Databricks network restrictions.

• for private link send to the private link Private Action Runner tab of step 1
• for network restrictions, only the webhooks ips are required

Merge instructions

Merge readiness:

• Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

AI assistance

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/adrien.boitreaud/cleanup-ip-allowlist-wording/data_observability/jobs_monitoring/databricks/