Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Centralizing Azure Storage metadata

Last updated: 5/18/2026

About this task

You can use the Azure Storage metadata wizard provided by Talend Studio to set up quickly a connection to Azure Storage and retrieve the schema of your interested container(s), queue(s), and table(s).

Procedure

  1. In the Repository tree view, expand the Metadata node, right-click the Azure Storage tree node, and select Create Azure Storage from the contextual menu to open the Azure Storage wizard.
    Create Azure Storage option selected by right-clicking.
  2. In the Azure Storage Connection Settings dialog box, specify, or update the connection settings.
    • Name: enter the name for the connection to be created.
    • Account Name: enter the name of the storage account you need to access. A storage account name can be found in the Manage Access Keys dashboard of the Microsoft Azure Storage system to be used.
    • Account Key: enter the key associated with the storage account you need to access. Two keys are available for each account and by default, either of them can be used for this access.
    • Protocol: select the protocol for this connection to be created.
    • Use Azure Shared Access Signature: select this check box to use a shared access signature to access the storage resources without need for the account key. In the Azure Shared Access Signature field displayed, enter your shared access signature between double quotation marks. For more information, see Using Shared Access Signatures (SAS).
  3. Click Test connection to verify the configuration.
    A connection successful dialog box will prompt up if the connection information provided is correct. Then click OK to close the dialog box. The Next button will be available to use.
  4. Click Next and in the Add a new container schema in current connection dialog box displayed, select your interested container(s) whose schema you want to retrieve.
    Add a new container schema in current connection dialog box.
  5. Click Next and in the Add a new queue schema in current connection dialog box displayed, select your interested queue(s) whose schema you want to retrieve.
    Add a new queue schema in current connection dialog box.
  6. Click Next and in the Add a new table schema in current connection dialog box displayed, select your interested table(s) whose schema you want to retrieve.
    Add a new table schema in current connection dialog box.
  7. Click Finish to complete the procedure.
    The newly created Azure Storage connection is displayed under the Azure Storage node in the Repository tree view, along with the schema of your interested container(s), queue(s), and table(s).
    New Azure Storage connection displayed in the Repository tree view.
    You can now add a Azure Storage component onto the design workspace by dragging and dropping the Azure Storage connection created or any container/queue/table retrieved from the Repository view to reuse the connection and/or schema information. For more information about dropping component metadata in the design workspace, see Using centralized metadata in a Job. For more information about the usage of the Azure Storage components, see the related documentation for the Azure Storage components.
    To modify the Azure Storage connection metadata created, right-click the connection node in the Repository tree view and select Edit Azure Storage from the contextual menu to open the metadata setup wizard.
    To edit the schema of an interested container/queue/table, right-click the container/queue/table node in the Repository tree view and select Edit Schema from the contextual menu to open the update schema wizard.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here