> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-azure/azure-privatelink-setup.md).

# Azure PrivateLink Setup

groundcover's BYOC comes with VPC service endpoint (PrivateLink) built in.\
The PrivateLink endpoint lets you ingest data through private network and reduce data transfer costs.

## Setup PrivateLink connection

* Create private endpoint on your network pointing the new private link service
* Create private DNS zone `<backend endpoint>` with a record to the private endpoint IP
* Link the private DNS to the same vNet as the private endpoint

## Troubleshooting

Open shell on the monitored workload on the same VPC

Use nslookup to determine if DNS configured correctly, if the endpoint returns IPs that are not from your VPC CIDRs, double check the DNS configuration

* `nslookup <groundcover backend endpoint>`

Use netcat to test the security groups configured correctly, if you get timeout to the VPC endpoint double check the inboud rules on the VPC endpoint and the outbound rule on the workload security groups

* `nc -vz <groundcover backend endpoint> 443`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-azure/azure-privatelink-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
