> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/automation/runbooks/runbooks.md).

# Runbook Parameters

RealmJoin runbook parameters such as TenantID and SubscriptionID that connect to Azure Automation and enable process automation.

## Overview

This page allows you to specify the components needed to interact with Azure Automation and enable the use of [Runbooks (Process Automation)](/automation/runbooks.md).

## Parameters

![Runbook Integration Parameters](https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2F0uQyL4KEyI8MZlp8AqZ4%2Fimage.png?alt=media\&token=8ffb3dfd-fc45-49e9-9709-e77ac2c31c49)

### TenantID

Please provide the unique [id of your Entra ID tenant](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/find-tenant-id-domain).

### SubscriptionID

Please provide the unique id of the Azure subscription hosting your Azure Automation Account.

### ResourceGroup

Please provide the name of the Azure ResourceGroup hosting your Azure Automation Account.

### ClientID and ClientSecret

RealmJoin will create an application in your Azure environment called "RealmJoin Runbook Management". This application will be used to interact with the Azure Automation Account. It will import runbooks from RealmJoin's central repository into your Automation Account and it will be used to start runbooks and to read runbook job logs.

Please provide the app's ClientID ("AppId") and ClientSecret, so that RealmJoin can authenticate against Azure Automation.

Make sure, that you securely store the ClientSecret. It will not be readable after saving this dialogue. If you click "Reset Setup", the field will be reset/emptied.

### Branch

RealmJoin maintains a public repository of shared runbooks at <https://github.com/realmjoin/realmjoin-runbooks>

These runbooks are imported when you sync runbooks on the [General Settings](/administration-and-settings/general.md) page.

Currently there are different git branches in this repository.

* **production** - The main branch for production use. These runbooks are thoroughly tested, and we recommend using this branch.
* **master** - Early / Insider versions runbooks. These should be usable at any given time but are less well tested.
* **feature-{...}** - Specific features can be tested ahead of time by using specific features branches as part of a private preview or beta testing. Not recommended for general use.

Specify the name of the branch you want to use. "production" is recommended.

### Location

Specify the Azure Location to use when importing runbooks. This is a drop-down field and needs no typed input.


---

# 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.realmjoin.com/automation/runbooks/runbooks.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.