FAQ

Which links should I bookmark?

Am I able to maintain my own software packages and updates?

RealmJoin contains an internal application store compatible with Intunewin (Microsoft Endpoint Manager / Intune Package Format), with over 1000 existing applications. RealmJoin offers packaging-as-a-service to provide any missing applications.

As RealmJoin directly leverages Microsoft Endpoint Manager, it is possible to offer additional applications which are maintained independently by your organization next to applications sourced through our application store.

Am I able to maintain my own runbooks?

RealmJoin offers a public repository of runbooks. These runbooks are improved and updated continuously and build the foundation of what we think are everyday routine tasks in a modern workplace environment. As such, these runbooks are automatically synced into a RealmJoin environment as part of our service.

RealmJoin leverages standard Azure Automation features to host these shared runbooks. They will be stored using a rjgit- prefix in your Azure Automation Account. You can simply add custom runbooks without this prefix to the same Azure Automation account. If the runbooks adhere to our naming scheme, RealmJoin Portal will present your custom runbooks in the same way as our shared ones.

See Runbook naming scheme

What cost to expect from Azure Resources?

RealmJoin utilises the customers Azure instance for Log Analytics and Key Vault. Microsoft bills the cost for traffic directly to the customer, currently 2.8€ per GB.

From our experience over several customers, we estimate it takes 250 to 500 tenant users to reach 1 GB, translating to 2-4 cents/user per month.

We will monitor the traffic numbers in the future and update our estimation regularly if necessary.

Does RealmJoin work with White-Glove?

The compatibility of RealmJoin with White-Glove (Autopilot Pre-Provisioning) varies based on the deployment method employed:

  1. Intune-Driven Deployment for Apps:

    • Compatibility: Generally supported.

    • Considerations: Manual intervention may be necessary to ensure that deployed applications remain up to date. This involves regularly checking for updates and applying them to maintain the integrity and functionality of the applications.

  2. RealmJoin Agent-Driven App Deployment:

    • Compatibility: Not supported.

    • Recommendation: In this scenario, it is advisable to use a Temporary Access Pass (TAP). This method provides a secure and efficient way to grant temporary access for the user profile to an admin, ensuring that they can perform necessary tasks without compromising security.

  3. Alternative Option:

    • Device Assigned Applications: Depending on the specific use case, this method can be utilized as an alternative. This approach allows for applications to be assigned directly to devices, ensuring that the necessary software is available and up to date on each device. Suitable for devices that are used by more than the primary user only.

By understanding these nuances, you can select the most appropriate deployment method for your requirements, ensuring a smooth and efficient integration with White-Glove.

Last updated

Was this helpful?