External Data as System Variables for Apps and Profiles

System Variables are a powerful mechanism in Silverback to configure applications, certificates, and profiles using device, user, or directory information. This works particularly well when the required data is already available within Silverback—for example from managed devices, local users, or directory integrations such as Active Directory. In some scenarios, however, the required information resides in external systems that are not directly accessible to the MDM. Without a way to reference this data, configuration scenarios such as credential injection, identifier‑based app configuration, or certificate personalization become difficult or impossible to automate.

To address this, Silverback 26.1 and newer supports importing external data from CSV files and exposing it as system variables that can be used throughout application and profile configurations. External data can be uploaded and managed via External Data Management, where a CSV file is imported and mapped to a defined identifier that Silverback already knows for a device. Supported matching identifiers include, among others:

• Phone Number
• Username
• Serial Number
• Device ID
• IMEI
• ICCID
• IMSI
• EAS Device Identifier

One of these identifiers must be present in the CSV file and is selected as the matching key during import. Based on this mapping, Silverback associates the external data with the corresponding devices.

Seriennummer,Username,Password
540125290299,mario,Pa$$w0rd
560125290300,luigi,Pa$$w0rd

During schema creation, administrators can define field aliases and mark sensitive fields—such as passwords or secrets—as confidential. These values are stored encrypted and handled securely by the system.

Once imported, Silverback automatically generates system variables from the external data. These variables are visible in the device details and can be used in the same way as native system variables for app configurations, certificate profiles, and other configuration scenarios.

Default System Variables	Extended System Variables based on external source

This enhancement significantly extends the flexibility of system variables, allowing Silverback to consume data from external sources without requiring direct system integrations—unlocking advanced automation and configuration use cases that were previously out of reach.

It is important to note that changes to the external source data do not automatically trigger updates of app configurations or profiles. This behavior is consistent with the existing Silverback configuration model and remains unchanged. System variables derived from external data are resolved and applied at the time a profile or managed app configuration is installed. Subsequent changes to the external data source alone do not cause configurations to be re‑applied to devices.
To propagate updated external data, administrators have several options:

• Remove and reassign the tag that contains the affected profile or application
• Make a (minor) change to the profile or managed app configuration to trigger a new installation
• Reinstall the affected application, which will also result in the managed configuration being applied again with the updated variables
• Import a new or updated external data schema and adjust the referenced variables accordingly. In this case, the updated schema becomes effective once the associated profiles or app configurations are re‑applied.

This behavior aligns with Silverback’s established deployment model and ensures consistent and deterministic configuration updates.