> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/inforiver-enterprise-on-prem/how-to-guides/private-app-service.md).

# Private App Service

By default, the app service would be accessible from public network. But some organization would like to make this app service as private so that it would be accessible only from the local private network.

To make the app service follow the steps below.

* Go to the Networking section of App service and select the option ‘Private Endpoints’

<figure><img src="https://4102771481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftn9fmavAcyzaE7MAMP2U%2Fuploads%2FOARR6McHWGrmFHar3Lxn%2Fprivate1.png?alt=media&amp;token=fd830296-8fc0-404d-aedb-7d89bee5d39d" alt=""><figcaption></figcaption></figure>

* In the Private Endpoint connections page, click on ‘Add’ and select ‘Express’

<figure><img src="https://4102771481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftn9fmavAcyzaE7MAMP2U%2Fuploads%2FOVOONyLPYP925Y8SPcfz%2Fprivate2.png?alt=media&amp;token=955173d2-98e0-4c11-be6a-630b82e9dddd" alt=""><figcaption></figcaption></figure>

* Give a name for the endpoint and select the private subnet information from the dropdowns and make sure to keep the option Yes for Integrating with private DNS zone.

<figure><img src="https://4102771481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftn9fmavAcyzaE7MAMP2U%2Fuploads%2Fk2WH8LJYNo20jm4Whmwk%2Fprivate3.png?alt=media&amp;token=ae74ca08-dcbf-46e8-8f50-0eb7d549e1d0" alt=""><figcaption></figcaption></figure>

* Once the Private Endpoint is created the public inbound IP will be replaced by a private IP and you may use this IP to map to a custom domain in your local DNS server or use the private FQDN *(\<appname>.azurewebsites.net*) to access the app service within your extended private network.

<figure><img src="https://4102771481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftn9fmavAcyzaE7MAMP2U%2Fuploads%2Fts1Q0suc3QH2gpwzx2Hb%2Fprivate4.png?alt=media&amp;token=ed30ba76-dfaf-4d8e-a0c9-d3a3f8bd6209" alt=""><figcaption></figcaption></figure>


---

# 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.inforiver.com/inforiver-enterprise-on-prem/how-to-guides/private-app-service.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.
