Azure Key Vault Data - Create or update a secret

Use the Azure Key Vault Data - Create or update a secret action A tool for building the processes, logic, and direction within workflows. Actions are the steps the workflow performs to complete a process. to create a new secret or update the properties of an existing one. If the name of the secret exists, then Azure Key Vault creates a new version of that secret.

For more information about the Azure Key Vault Data connector, go to Azure Key Vault Data.

Before you begin: 

Jump to:

Configure the Azure Key Vault Data - Create or update a secret action

  1. Add the action to the workflow and open the action configuration panel. For more information, see Add an action to the workflow.

  2. Select a Connection. If you do not have a connection, see Add a connection.
  1. Specify a Secret name for the secret you want to create or update.
  2. Specify the Value for the secret.

Azure Key Vault Data - Create or update a secret action fields and settings

Section

Field

Description

Variable types

(Unlabeled)

Connection Credentials and other settings that enables workflows to communicate with external systems, services, or applications. It's required to pass data between the workflow and the indicated service, which could be a cloud service, business application, or content store.

The Azure Key Vault Data connection to use to create or update the secret.

To refresh the available connections, click .

(n/a)
Secret name The name for the secret. The secret name must be unique within a Key Vault. Text, Decimal, Integer, Boolean, DateTime, Collection
  Value The value for the secret. Text, Decimal, Integer, Boolean, DateTime, Collection
  Content type The content type of the secret. You may specify the content type of a secret to assist in interpreting the secret data when it's retrieved. The maximum length of this field is 255 characters. The suggested usage is as a hint for interpreting the secret data. For instance, an implementation may store both passwords and certificates as secrets, then use this field to differentiate. There are no predefined values. Text, Decimal, Integer, Boolean, DateTime, Collection
  Expiration date

Expiry date in Unix time. This attribute identifies the expiration time on or after which the secret data SHOULD NOT be retrieved.

Unix time (also known as Epoch time, Posix time, seconds since the Epoch, or UNIX Epoch time) is a system for describing a point in time. It is the number of seconds that have elapsed since the Unix epoch, minus leap seconds; the Unix epoch is 00:00:00 UTC on 1 January 1970 (an arbitrary date); leap seconds are ignored, with a leap second having the same Unix time as the second before it, and every day is treated as if it contains exactly 86400 seconds. Unix time is widely used in operating systems and file formats.

The following steps present an example of how to get Unix time from a date in a form input:

  1. In a form, create aDate/time picker control called Target Date.

  2. Add a variable that calculates the TotalSeconds between 1970/1/1 00:00:00 and your target date:

    • dateDiff("TotalSecond", date(1970,1,1,0,0,0), Form.Target Date)
      Unix time

  3. Test the form to make sure that the control is working. For example, selecting 12pm on the 9th of June 2021 should result in a Unix time of 1623240000.

 Integer
  Enable Determines whether the secret is enabled. This attribute specifies whether the secret data can be retrieved. The enabled attribute is used in conjunction with Activation date and Expiration date. When an operation occurs between the two dates, it will only be permitted if enabled is set to true. Boolean
  Activation date

Not before date in Unix time.

Unix time (also known as Epoch time, Posix time, seconds since the Epoch, or UNIX Epoch time) is a system for describing a point in time. It is the number of seconds that have elapsed since the Unix epoch, minus leap seconds; the Unix epoch is 00:00:00 UTC on 1 January 1970 (an arbitrary date); leap seconds are ignored, with a leap second having the same Unix time as the second before it, and every day is treated as if it contains exactly 86400 seconds. Unix time is widely used in operating systems and file formats.

The following steps present an example of how to get Unix time from a date in a form input:

  1. In a form, create aDate/time picker control called Target Date.

  2. Add a variable that calculates the TotalSeconds between 1970/1/1 00:00:00 and your target date:

    • dateDiff("TotalSecond", date(1970,1,1,0,0,0), Form.Target Date)
      Unix time

  3. Test the form to make sure that the control is working. For example, selecting 12pm on the 9th of June 2021 should result in a Unix time of 1623240000.

 Integer
Output Secret

Stores the result of the action as an object. See Azure Key Vault - Create or Update Secret API for information on these values.

The following values are returned:

  • Attributes: (Object)
    • Created date: (Integer)
    • Enabled: (Boolean)
    • Expiration date: (Integer)
    • Activation date: (Integer)
    • Recovery level: (Text)
    • Updated date: (Integer)
  • ID: (Text)
  • Content type: (Text)
  • Value: (Text)
 Object