.png?sv=2019-07-07&sig=7rPxD7%2FCer2O9Yi4zbKPktuLvh3STnwpCIDmeZS9skY%3D&spr=https%2Chttp&st=2023-03-25T11%3A01%3A34Z&se=2023-03-25T11%3A11%3A34Z&srt=o&ss=b&sp=r){kind=logo}
Microsoft Azure - Send CSV to Azure Storage
- 16 Mar 2023
- 4 Minutes to read
-
Print
-
DarkLight
-
PDF
Microsoft Azure - Send CSV to Azure Storage
- Updated on 16 Mar 2023
- 4 Minutes to read
-
Print
-
DarkLight
-
PDF
Microsoft Azure - Send CSV to Azure Storage creates a CSV file with the assets that match the results of the selected saved query, and match the Enforcement Action Conditions if defined, or assets selected on the relevant asset page and sends the CSV to Azure Storage.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonious. You can change the name according to your needs.
- Add description (optional) - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs and Adapter Fetch History Modules
- Action name - The name of the Main action. A default value is added by Axonious. You can change the name according to your needs.
- Configure Action Conditions - Toggle on to enter a condition statement. See Configuring Enforcement Action Conditions to learn more about condition statement syntax.
Required Fields
These fields must be configured to run the Enforcement Set.
Click to view required fields
- Data storage - Select the type of data storage:
- File share - Saves the CSV file to a standard file share. When File shares is selected, the following required fields appear:
- File share and File name - The file share and file name under the storage account.
- Blob containers - Saves the CSV file to a blob container. When selected, the following required fields appear:
- Blob container - The name of the blob container.
- Blob name - The name of the specific blob.
- Blob type - Select the blob type: Block blob (default) or Append blob.
- File share - Saves the CSV file to a standard file share. When File shares is selected, the following required fields appear:
- SAS token (required) - SAS token associated with a user account that has the Required Permissions to create a file.
- Storage account (required) - The storage account name.
- Instance Name - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
Click to view additional fields
* **Directory path** - Specify the directory path. When no path is specified, the file will be created under the file share directly. This field is not available when Blob storage is being used.
Additional CSV Settings
- Split by asset entities - Select to create a CSV file where each asset on a device is shown as a separate row. This separates each asset as the 'expand' option in the application. It separates each asset by its entity. For example, you will be able to know which values were fetched from each adapter connection.
a. If supplied, each value on a device or user is shown as a separate row.
b. If not supplied all values on a device are in the same cell on the CSV file. - Split by field values - Choose field value - For complex fields and lists you can create a CSV file where the values of complex fields and lists are represented as separate rows in the file. From the drop-down box select the value that you want to display in the file, 'Tags' for instance. Only fields that have been discovered are available. For example, if you export by Installed Software, you will be able to see each installed Software name and its version.
- Don't split complex objects into columns - When selected, complex objects appear in a single column in JSON format. By default, each field in a complex object is split into a separate column in the CSV file.
- Export CSV delimiter to use for multi-value fields (default: Export CSV delimiter to use for multi-value fields field under the System Settings section in the GUI Settings) - Specify a delimiter to separate between values within the same field of an exported CSV file, otherwise the delimiter defined in Export CSV delimiter to use for multi-value fields is used.
- Maximum rows (default: 1048500) - Specify the maximum number of rows to be included in the CSV file. When you set a value here the generated CSV file will include the top x rows, based on the specified values. Otherwise, the generated CSV file will include the default maximum rows, set as 1048500.
APIs
Required Permissions
Click to view Required Permissions
The value supplied in SAS token must be associated with a user account that has the Required Permissions to create a file.
To create a SAS token:
- Connect to your storage account.
- From the left navigation menu, select Shared access signature.
- Configure the access signature:
- Allowed services - select File.
- Allowed permissions - select: Read, Write, Create
- Click Generate SAS and connection string to generate a SAS token.
For details on creating a SAS token, see Grant limited access to Azure Storage resources using shared access signatures (SAS).
For more details about other Enforcement Actions available, see Action Library.