> 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/scaling-up-the-app-service-plan.md). # Scaling Up the App Service Plan There are two workflows for scaling-scale up and scale out. Let us first see the steps to scale up Inforiver app in Azure App Service. ### Scale Up the App Service Plan 1. Select Inforiver Webapp. 2. Click on **Scale up(App Service plan)** on the left-side menu.

3. Choose the desired pricing tier that corresponds to the scale level you want. Then, click **Select.** ### Scale Out the App Service Plan 1. Select Inforiver Webapp. 2. Click on **Scale out (App Service plan)** on the left-side menu.

3. In the Scale out method, choose **Rules Based** and configure **Manage rules based scaling.** You can ignore this if **Automatic** scaling is enabled. 4. Then configure the **Autoscale setting** based on your requirements.

5. Click **Save** to save your settings. #### Other Resources To learn more on scaling up and scaling out, refer this [page](https://learn.microsoft.com/en-us/azure/app-service/manage-scale-up). --- # 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/scaling-up-the-app-service-plan.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.