Secure variables are always encrypted, both when they are in memory and when they are stored. This increased level of security ensures that your sensitive data cannot be accessed or viewed by unauthorized personnel.
To create a secure variable, you can choose ‘Secure’ from the ‘Variable type’ dropdown in the ‘Variable Manager’. The secure variable created can then be used in your desktop flow just like any other variable.
II. Configuring Secure Variables in Desktop Flows
Secure variables can be used in the Power Automate desktop application in a number of different ways. Here is a step-by-step guide on how to configure a secure variable:
- Launch the Power Automate Desktop and click on ‘Create a flow’.
- Click on ‘Variable Manager’ on the top right-hand side of the screen.
- This will open the ‘Variable Manager’ window. Click on ‘+Add’.
- In the ‘Add Variable’ window, you must give your secure variable a name. Make sure it is meaningful and unambiguous about its function.
- From the ‘Variable type’, select ‘Secure’, then click ‘OK’.
III. Setting up Secure Variable Values
The value for a secure variable can be set in three different ways:
- Directly in the desktop app when designing the flow.
- Setting the value dynamically at the start of a flow.
- Configuring the value at the cloud flow level, in case the desktop flow is summoned by a cloud flow.
IV. Examples of Using Secure Variables
EXAMPLE 1:
Directly in the Desktop App
Here is how you can use a secure variable for storing a password directly at design time:
- In the ‘Actions Pane’, click on ‘Set variable’.
- Double-click on the ‘Set variable’ action that appears in your flow to assign a secure string to it.
EXAMPLE 2:
Setting the Value Dynamically at the Start of a Flow
Secure variables can also be configured to accept values dynamically during the desktop flow execution. Here’s how to do it:
- When creating the variable, uncheck the ‘Initial value is mandatory’ checkbox.
- Use the ‘Input’ action to prompt the user to enter a value during the flow execution.
V. Conclusion
Using secure variables in Power Automate Desktop is crucial for maintaining the security and privacy of sensitive data in your flows. They are a powerful feature that every Power Automate RPA Developer should use. While configuring and using them may seem a bit confusing at first, with practice, secure variables can become an essential part of every RPA Developer’s toolkit.
Practice Test
True or False: Secure variables in Power Automate can be used to store sensitive data like passwords and API keys.
- True
- False
Answer: True
Explanation: Secure variables in Power Automate’s desktop flows are used to save and reference credentials securely without exposing sensitive details.
Which of the following type of data can be stored in secure variables of Desktop Flows?
- A. Text
- B. Password
- C. Files
- D. All of the Above
Answer: B. Password
Explanation: Secure variables are typically used to store password or other sensitive data. Text and files are generally not stored in secure variables.
True or False: You cannot create a secure variable in Power Automate’s desktop flow without providing a default value.
- True
- False
Answer: False
Explanation: Providing a default value for secure variables is completely optional.
Secure variables in Power Automate desktop flows can be accessed by:
- A. Any user with access to the flow
- B. Only the creator of the flow
- C. Only those with the necessary permissions
- D. None of the above
Answer: C. Only those with the necessary permissions
Explanation: Access to secure variables is only granted to those users with the requisite permissions, adding an extra layer of security to your sensitive data.
True or False: In desktop flows, the contents of secure variables are automatically encrypted.
- True
- False
Answer: True
Explanation: The content of secure variables is automatically encrypted to further enhance the security and privacy of data stored.
Can we assign a value to secure variables during run time in Power Automate?
- A. Yes
- B. No
Answer: A. Yes
Explanation: A value can be assigned to secure variables both at design time and during run time as per requirements.
True or False: You can view the value of secure variables in plain text after they have been assigned.
- True
- False
Answer: False
Explanation: Secure variable values are encrypted and cannot be viewed in plain text once they are assigned.
Is it mandatory to use secure variables in desktop flows?
- A. Yes
- B. No
Answer: B. No
Explanation: Using secure variables is not mandatory. It depends on whether there is sensitive data that needs to be protected.
The maximum number of secure variables that can be created in a Power Automate Desktop flow is _______.
- A. Unlimited
- B. 10
- C. 50
- D. 100
Answer: A. Unlimited
Explanation: There is no maximum limit set on the number of secure variables that can be created in a desktop flow.
True or False: The values of secure variables can be used in expressions.
- True
- False
Answer: True
Explanation: The values of secure variables can indeed be used in expressions. This allows us to utilize these secure values in a more dynamic way in our automation design.
Interview Questions
What is the primary use of secure variables in desktop flows in Power Automate?
Secure variables in desktop flows are used to store sensitive data like passwords or secret keys that are needed within the flow but should not be exposed.
How can you create a secure variable in a Desktop flow?
Secure variables can be created through the “Variables” panel in the desktop flow editor by clicking the ‘New’ button then selecting the secret check box before defining the variable name.
How are secure variables encrypted in Power Automate Desktop?
Secure variables are encrypted using Windows Data Protection API (DPAPI) and are encrypted at the machine level or at the user level.
Which Power Automate Desktop action allows you to set a secure variable?
The “Set Variable” action allows you to set a value of a secure variable in a Power Automate Desktop flow.
How are secure variables displayed in the Desktop Flow console when they are set or accessed?
Secure variables are masked in the console to retain their secure status. When set or accessed, they appear as asterisks () in the console.
Can secure variables be used across different flows in Power Automate Desktop?
No, secure variables are flow-specific, which means a secure variable defined within a flow is not available to other flows.
Can I use secure variables to store non-sensitive data?
Yes, although it’s designed for sensitive data, it can be used to store any kind of data.
Is it possible to view the value of a secure variable during the runtime of a flow?
No, the actual value of a secure variable is not exposed during runtime to maintain the security of the data.
Are secure variables in Power Automate Desktop are case-sensitive?
Yes, secure variable identifiers are case-sensitive.
Can secure variables in Power Automate Desktop be renamed after their creation?
No, once a secure variable is created, it cannot be renamed.
How can we use secure string in desktop flow UI automation activities?
We can use “{SecureString}” syntax and Power Automate Desktop will automatically substitute with the real secure string during execution.
Are secure variables in Power Automate Desktop available in Power Automate’s web-based flows?
No, secure variables are not available in Power Automate’s web-based flows. They are specific to Power Automate Desktop flows.
Can I log the value of a secure variable?
No, Power Automate Desktop prevents logging the value of secure variables to maintain data security.
What happen when secure variables are exported from a Desktop flow?
The value of a secure variable is not exported with a flow. The user must re-enter the value when the flow is imported and run on a different machine.
Can we make a regular variable to secure variable in desktop flows?
No, once a regular variable is created, it cannot be converted to a secure variable.
extutorials.com