Comment on page
Automate day to day operations in your environment.
RealmJoin allows you to automate tasks, like
- User lifecycle operations (onboarding/offboarding users)
- Creating Temporary Access Passes (TAPs)
- Reporting M/O365 license usage
- Managing email aliases
Runbooks are scripts, automating tasks that normally have to be executed by a support engineer / operator or administrator. Automating these tasks lowers the risk of manual error and allows better auditing of actions.
You can offer RealmJoin Portal to your support and administration teams to simplify and improve the quality of your day to day operations.
glueckkanja maintains a shared online repository of runbooks. They aim to cover many common operations found in most environments. The runbooks are continuously updated and improved. Of course you can include your own, custom runbooks, too.
RealmJoin Portal allows you to import these runbooks via RealmJoin Runbook Management App into your environment and offers your support and administration staff an easy, non-technical interface to the tasks the runbooks cover.
You can trigger a sync from the shared repository to your Azure Automation account by clicking "Sync runbooks with upstream" at
Trigger a sync of your runbooks
Wait for the "Sync completed" message. Please keep the browser window open while the sync process is running.
As described in the naming convention this will add, update and if needed remove runbooks from the connected Azure Automation Account to be in sync with glueckkanja's shared repository. This ensures that your runbooks are up to date, including improvements, fixes and new features.
You can customize existing an new runbooks to your environment. For example, you can
- Use templates for common pieces of information, like office locations
- Prefill / preconfigure parameters, like to not allowing deleting user object when offboarding
- Hide certain inputs/parameters
Runbooks in RealmJoin Portal are scoped to the different types of objects in your environment. Some runbooks operate on the tenant / organization level, like creating a license report. Some runbooks are scoped on a per user basis, like resetting a password. RealmJoin Portal uses this scoping to offer the right runbooks in the right context.
Access/Permissions to use certain runbooks can be granularly given on either a runbook level. E.g:
- Only allow access to this runbooks to the 3rd level operators
Or limit runbooks usage on certain groups of users:
- Only allow our VIP support crew to change the CEO's email address