> 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/deployment/microsoft-azure/basics.md).
# Basics
In this section, you will configure the basic details for the Inforiver deployment.
* Under **Basics**, fill in all the project details and instance details.
* Choose the appropriate subscription that you want this deployment to be part of.
* Choose the resource group that you created or assigned for this.
* Choose the required region for your deployment instance.
* Provide a solution name. Make sure that it doesn't contain any space or special characters.
* Provide a container registry token and confirm the same in the next field.
* Provide the image version that needs to be deployed.
* Choose the required background processor (ACI/AKS/ACA).
* If the background processor is AKS, the AKS node pools are configured with a dedicated system node pool containing one node and a user node pool with autoscaling enabled from 2 to 3 nodes based on workload demand.
* If the background processor is ACA, configure the minimum and maximum dedicated D4 VM count based on your workload requirements.
* If the background processor is ACI or ACA, select the required product type, and then select **Next**.
{% hint style="info" %}
For a smooth deployment, ensure that there are no spaces or special characters in the solution name.
{% endhint %}
Basic steps
---
# 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/deployment/microsoft-azure/basics.md?ask=&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.
