Skip to content

Setting up the Microsoft Azure Storage Environment

To work with the Microsoft Azure Storage connector, you need to have a Microsoft Azure account. If you do not have a Microsoft Azure account, you are prompted to create one when you sign up.

Signing Up for Microsoft Azure

To sign up for Microsoft Azure:

  1. Navigate to Microsoft Azure and create a Microsoft Azure account using Start free button.

  2. Follow the online instructions.

Part of the sign-up procedure involves receiving a phone call and entering a verification code using the phone keypad. Microsoft Azure will notify you by email when your account is active and available for you to use.

Create Microsoft Azure Storage account

Follow the steps below to obtain the access credentials from Microsoft Azure Storage account.

  1. Go to Microsoft Azure, and sign in to the created Microsoft Azure account. On the Azure portal menu, select All services. In the list of resources, type Storage Accounts. As you begin typing, the list filters based on your input. Select Storage Accounts.

    MS Azure Home PageMS-azure-storage-select-account.png

  2. Go to the dashboard and click Storage accounts then click Add and fill the required details to create a new storage account.

    Select MS Azure storage account

  3. On the Storage Accounts window that appears, choose Add.

    MS Azure add storage account

  4. Select the subscription in which to create the storage account.

    MS azure storage basic configurations

  5. Under the Resource group field, select Create new. Enter a name for your new resource group.

    Create resource group

  6. Enter a name for your storage account.

  7. Select a location for your storage account, or use the default location.

  8. Leave these fields set to their default values:

    Field Value
    Deployment model Resource Manager
    Performance Standard
    Replication Read-access geo-redundant storage (RA-GRS)
    Access tier Hot

  9. Select Review + Create to review your storage account settings and create the account.

    Review and create

  10. Select Create.

Obtaining the Client credentials

Note

If you are planning to use Access key for authentication, skip this and check Obtaining the access credentials

  1. Create an Azure Active Directory application and service principal. For more information refer Create an Azure Active Directory application.

  2. Assign an Azure role for access to blob data. For more information refer Assign an Azure role and Assign an Azure role for access to blob data.

  3. Obtain the Client ID, client Secret and Tenant ID. For more information refer Create a new application secret and Active Directory tenant ID.

Obtaining the Access Key

Note

If you are planning to use Client credentials for authentication, skip this and check Obtaining the Client credentials

  1. Navigate to the created storage account and click it.

    Select created storage account

  2. Click Access keys under Settings.

    Getting access keys

  3. Obtain the access key.

    Copy access keys

Note: Azure Storage Account does not support HTTP requests. If you are using a storage key to access the storage account, please set Secure transfer required to Disabled in storage account configuration on Azure Portal.
Copy access keys

Setting up the Microsoft Azure Storage Connector

Before you start configuring the Microsoft Azure Storage Connector, you also need the WSO2 integration runtime and we refer to that location as <PRODUCT_HOME>.

Note

If you are using the older connector 1.x.x add only the azure-storage-6.1.0.jar jar to <PRODUCT_HOME>/lib directory and skip the following.

In order to use the Microsoft Azure Storage connector, you need to download the following jars and move them to the <PRODUCT_HOME>/lib directory.

Note

If you are using MI 4.0.0, in addition to the above you need to add netty-codec-http2-4.1.95.Final.jar and netty-handler-proxy-4.1.95.Final.jar to <PRODUCT_HOME>/lib directory.

Note

By default INFO logs are enabled for the Microsoft Azure SDKs, therefore you may need to update the log4j2.properties of the WSO2 integration runtime (MI) accordingly to set the log level. The following configuration will disable the logs printed by the SDK. Eventhough the SDK logs are disabled, MI will print them in case of an error.

  1. Add the following loggers.

    logger.Azure.name = com.azure
logger.Azure.level = OFF

logger.Microsoft.name = com.microsoft
logger.Microsoft.level = OFF

  2. Append Azure and Microsoft to the loggers list.