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
  • RealmJoin Runbook Management
  • Azure Resource Permissions

Was this helpful?

Edit on GitHub
  1. Automation
  2. Connecting Azure Automation

Required Permissions

This page describes the permissions needed for RealmJoin to interact with Azure Automation / Runbooks.

See Requirements to see which permissions need to be granted to Azure Automation for the runbooks to be useful in your environment.

RealmJoin Runbook Management

RealmJoin will create an Application Registration called RealmJoin Runbook Management which is used to update the Azure Automation Runbooks in your tenant based on RealmJoin's shared runbook repository.

This app also will be used by RealmJoin Portal to trigger runbook execution after filtering requests through RealmJoin's RBAC and Runbook Permissions.

As this app is created individually for your tenant, there is no globally known Application ID as with RealmJoin Portal's apps.

This app will not have any API permissions.

Azure Resource Permissions

The RealmJoin Runbook Management app will need to be at least Contributor on the Azure Resource Group hosting your Azure Automation Account. Using our onboarding process will make sure this permission is given.

Last updated 11 months ago

Was this helpful?