MSP-level variables
Nerdio Manager allows you to manage MSP-level secure and inherited variables.
Notes:
Secure and inherited variables can be used with both types of scripted actions: Windows scripts and Azure runbooks.
See Account-level variables for details about account-level variables.
See Overview of Scripted Actions for details about Nerdio-provided, pre-populated variables that can be used in the script code.
Secure variables
This feature is especially helpful if you want to pass sensitive information to a scripted action without passing it via clear text. Secure variables have the following key features:
Stored in the Key Vault.
Can be passed to MSP-level scripted actions using the $SecureVars.Variable_Name variable name.
Only available for scripted actions.
Inherited variables
Inherited variables limitations
The following are the limitations of inherited variables.
Variable names
20-character limit
Alphanumeric characters are allowed
Hyphens - are allowed
Underscores _ are not allowed
Special characters and punctuation are not allowed (for example, ~!@#$%^&*()[]{},.<>/?\|`)
Variable malues
Alphanumeric, special characters, punctuation, underscores, and hyphens are all allowed
Inherited variables have the following features:
Stored in the Nerdio Manager database.
Can be passed to MSP-level scripted actions, policies, and global apps using the $InheritedVars.Variable_Name variable name.
Environmental variables
Environmental variables are retrieved from the customer environment.
Can be passed to MSP-level scripted actions and policies using the $EnvironmentalVars.Variable_Name variable name.
Environmental variables are retrieved from your customer environment, so you can't modify them here.
Manage MSP-level secure and inherited variables
MSP-level secure and inherited variables define values that flow down to customer accounts. Managing them at the MSP level ensures consistency across environments while allowing account-level overrides where needed.
To manage MSP-level secure and inherited variables:
-
At the MSP level, navigate to Settings > Integrations.
-
In the Secure and Inherited variables for scripted actions tile, select the action (add, edit, or remove) you wish to perform.
-
To add or edit a global secure variable, enter the following information:
-
Name: Type the name of the variable.
Note: The variable name must be between 1 and 20 alphanumeric characters.
Value: Type the variable's value.
Variable type: Select the variable type.
Windows scripts: Optionally, from the drop-down list, select which Windows scripted action(s) the variable is passed to.
Azure runbooks: Optionally, from the drop-down list, select which Azure Runbook(s) the variable is passed to.
-
When you have entered the desired information, select OK.
To copy MSP-level variable names for Scripted actions or policy configuration:
At the MSP level, navigate to Settings > Integrations.
-
Locate the variable you wish to copy.
-
Select the copy icon on the left side to copy the variable name for scripted actions.
-
Select the copy icon on the right side to copy the variable name for policy configuration.
Comments (0 comments)