All pages
Powered by GitBook
1 of 1

Manage Azure Blob data storage

Before you proceed to this article, make sure you understand data storage management basics.

Update Azure Blob Storage Credentials

In Settings > Management Tab, add or edit the required credentials: CLIENT_ID, CLIENT_SECRET, TENANT_ID, and ACCOUNT_URL.

See the table below to learn where to look for them in your Azure account.

Emedgene Setting
Corresponidng client (Azure) Setting

CLIENT_ID

application_id.

Format: ########-####-####-####-############

(letters/numbers)

CLIENT_SECRET

Value of the client_secret tuple (Value, Secret ID).

Format: #####-#######-######-######

(letters/digits/special chars)

TENANT_ID

ID of the tenant.

Format: ########-####-####-####-############

(letters/numbers)

ACCOUNT_NAME

An arbitrary name that the customer must supply to define the ACCOUNT_URL.

Format: string

CONTAINER_NAME

An arbitrary name that the customer must supply to define the ACCOUNT_URL.

Format: string

ACCOUNT_URL

The account_url of the Azure account.

Format: https://account_name.blob.core.windows.net/container_name

Blob Integration Setup

Create an App registration

  1. In Microsoft Entra ID, click on App registrations.

  1. Select New registration.

  2. Fill the name of the application & press "register."

  3. You got to the registered app page: (CLIENT_ID / TENANT_ID) From this you can retrieve: Application ID and Tenant ID. Both are marked in the screenshot.

  1. Press "Certificates & secrets"

  2. Press on "New Client secret"

  1. Fill the "Description" and change expires to 12 months. (or according to your organization policy), than press "Add"

8. Get the CLIENT_SECRET from this page.

  1. Give this App registration roles and read access to the relevant Blob.

Azure Blob configuration

  1. Go to Azure Storage accounts

  1. Get into the relevant Storage account

  1. Press on "containers"

  1. Press on the relevant container

  2. Press on "Properties"

  3. Copy the ACCOUNT_URL\

For Internal support:

Errors for bad connections can be found in CloudWatch on particular FRY log stream

Search for: BlobApi, BlobFs, azure.