Azure Blob Storage connection

Overview

Storage account and container

Create or select an existing Azure Blob Storage storage account to use for input/output data.

Storage account name

The container name can be anything, but if possible please include your company/team name.

Example (if your company name is ABC): abcbillingdata

Container name

The container name can be anything, but if possible please include your company/team name.

If you are using separate containers for input/output, please include input or output in the container name as appropriate.

Storage account settings

Disable soft delete. This is counterintuitive, but it is required due to quirks of the Azure Blob Storage API.

• Storage account settings > Data protection
  • Uncheck "Enable soft delete for blobs"
  • Uncheck "Enable soft delete for containers"

Permissions

Access is provided to Greenpixie through a Local App Registration (residing in the customer environment).

The Local App Registration is granted roles on the storage account and container.

Greenpixie uses the client/secret from the Local App Registration for access.

Local App Registration

In Azure AD, create a new Local App Registration.

On the storage container (Storage Account > Containers > [container name] > Access Control (IAM) > Role assignments) grant the following roles to the Local App Registration, as appropriate:

• Storage Blob Data Reader
• Storage Blob Data Contributor

If your container is only input data, you can omit the Storage Blob Data Contributor role.

Next steps

Provide the following details to your Greenpixie contact:

• Storage account name
• Container name
• Local App Registration client ID
• Local App Registration client secret
• Tenant ID

Next, format and place your billing data in the bucket. Or, create more connections with other storage platforms.

When you're ready, please send your bucket name to your contact at Greenpixie.

---