LogoLogo
LogoLogo
  • Welcome
    • Navigation
  • RealmJoin Deployment
    • Onboarding
    • Required Permissions
    • Infrastructure Considerations
      • Multi User Devices
    • Migration to RealmJoin vNext
  • User, Group and Device Management
    • Overview
    • User Profile
    • Organization Details
    • User, Group and Device Lists
      • User Details
      • Group Details
      • Device Details
    • User and Group Settings
      • Available RealmJoin Policies
  • App Management
    • Packages
      • Package Store
        • Application Store Details
      • Package Management
      • Package Details
      • Package Assignments
        • Package Migration
      • Package Settings
      • Packaging Requests
        • Organic Packages
    • AVD Templates
  • Automation
    • Connecting Azure Automation
      • Required Permissions
      • Runbook Parameters
    • Runbooks
      • Runbook Customization
      • Runbook Permissions
      • Naming Conventions
      • Runbook Scheduling
      • Runbook Logs
        • Runbook Job Details
      • Runbooks Changelog
    • Requirements
    • Remediation Scripts
  • RealmJoin Agent
    • Features
      • Local Admin Password Solution (LAPS)
        • KeyVault
        • Application Insights
      • Notifications
      • AnyDesk Integration
        • RealmJoin Tasks
        • Customer Tasks
      • App Deployment using the Agent
        • RealmJoin ESP
    • Deploying the Agent
    • User Interface
  • Logs
    • Connecting Azure Log Analytics Workspace
    • Audit Log
  • RealmJoin Settings
    • Overview
    • General
    • Permissions
    • Group Namespaces
    • Workplace Cloud Storage
    • Self Service Forms
    • Custom Roles
      • Available Permissions
  • Developer Reference
    • RealmJoin API
      • Authentication
    • Interacting with Runbooks
    • Simulating a Runbook Environment
    • Local Admin Password Management
  • Other
    • FAQ
      • Security
    • Troubleshooting
      • Package Installation Issues
        • Collecting Logfiles
        • Logfiles Structure
        • Analysing chocolatey.log
        • Troubleshooting failed chocolatey packages
        • Troubleshooting failed craft packages
        • Fixes for common issues
        • Intunewin Debugging
      • LAPS Issues
        • LAPS account passwords cannot be retrieved
        • Requested LAPS Accounts are not being created
    • Changelog
  • Legal
    • Licensing
    • Support
  • RealmJoin Website
Powered by GitBook
On this page
  • Overview
  • Parameters
  • TenantID
  • SubscriptionID
  • ResourceGroup
  • ClientID and ClientSecret
  • Branch
  • Location

Was this helpful?

Edit on GitHub
  1. Automation
  2. Connecting Azure Automation

Runbook Parameters

Last updated 5 months ago

Was this helpful?

Overview

This page allows you to specify the components needed to interact with Azure Automation and enable the use of Runbooks (Process Automation).

Parameters

TenantID

Please provide the unique id of your Entra ID tenant.

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 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.

Runbook Integration Parameters