Azure Connect your data

       We summarize the setup process on Azure to connect your data to the Tenyks platform.


Before you start

📣 Please make sure you read the following points before continuing.

1. Expected folder structure

Here's the expected folder structure based on the option you choose:

read-only

Container name: {your_tenyks_data_container}

Images Directory: {your_tenyks_data_container}/{your_dataset_name}/{images_directory_name}/img_n.png

Predictions File (in COCO Format): {your_tenyks_data_container}/{your_dataset_name}/predictions.json

Annotations File (in COCO Format): {your_tenyks_data_container}/{your_dataset_name}/annotations.json

Metadata Directory: We will set this up for you! ⭐

For the read-write option, follow the same structure as in read-only but since your metadata remains in your own cloud, please add a Metadata Directory:

{your_tenyks_data_container}/{your_dataset_name}/{metadata_directory_name} (see Section 3.2)

2. Setting up Azure containers

Figure 1 shows an example of a container named tenyks-datasets inside a storage account named tenyksapi.

If you haven't set them up, this guide shows you how to create a storage account, and this one how to create a container.

We assume you have set up a folder structure in your container(s) as described on Section 1.


3. Access Policies


🔗

Connection String or Blob SAS URL

Choose one of the two following options to access your container:

For blob sas url:

⚠️ blob sas url should have a format similar to the following:

JSON

"https://tenyksdatasets.blob.core.windows.net/dataset?sp=racwdl&st=2021-02-02T17:40:59Z&se=2024-02-03T01:40:59Z&spr=https&sv=2022-11-02&sr=c&sig=E2PVl...aIgaHGY%3D"


For connection string


⚠️ connection string should have a format similar to the following:

JSON

"DefaultEndpointsProtocol=https;AccountName=tenyks;AccountKey=q1F...==;EndpointSuffix=core.windows.net"


🚨 Note that blob sas url (or connection string) is expected to be copied and pasted as the value of credentials in the request body of the endpoints.

4. Metadata bucket CORS settings

In case you are storing metadata on your own cloud, to use functionalities like the Embedding Viewer, please configure the CORS settings for your storage account.

Refer to Figure 4 below for more information.

5. Summary

We successfully created the following: