Azure File Drop Transmission Delegate supports storing files in Azure Blob Storage. You can send the regulatory submission payload files from Azure Blob Storage to a regulatory agency.

This topic contains the following sections on configuring Azure Blob Storage:

You can store files by configuring Azure Blob Storage using security credentials authentication or MSI authentication.

You can customize the transmit functionality of the Azure File Drop Transmission Delegate. For detailed steps, see Regulatory Transmission Delegate Interface. The following example shows an xconfiguration entry for a AzureDropTransmissionDelegate delegate.

To configure the Azure Blob Storage container to store regulatory submission payload files, set the property regmstr.filedrop.azure.path in azure store container for regulatory submission payload, as shown in the following example:

After the configuration is complete, successful transmission writes the regulatory submission payload file to the configured location with the following structure:

Each type of regulatory submission writes the regulatory submission payload file to a separate directory.

When Azure Storage Account is configured for security credentials authentication using the blob configuration utility, provide the account name of the storage and the key in an encrypted form. Execute the following command to invoke the blob configuration utility.

The encrypted setup enables the File Drop Transmission Delegate to locate the appropriate storage account.

The blob configuration utility also sets up Windchill vault data storage on azure blob containers.

When configuring Azure Storage Account for MSI authentication using the blob configuration utility, the system does not capture the storage account name. To identify the storage account in which the Enterprise System Integration (ESI) response is published, set the property regmstr.filedrop.azure.path using the site.xconf file, as follows: