> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/integrations/builtin/credentials/azurestorage.md).

# Set up Azure Storage credentials in Duaer

Store Azure Storage connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.
## Choose an Azure Storage credential type <a href="#choose-a-credential-type" id="choose-a-credential-type"></a>

The Duaer Azure Storage node supports two credentials:

- Azure Storage Shared Key API: in the Azure portal, open the storage account’s Access keys. Put the storage account name in Account and key1 in Key. Pick Azure Cloud for your cloud.
- Azure Storage OAuth2 API: register an app in Microsoft Entra, add the Duaer OAuth Redirect URL as a Web Redirect URI, and give your account a data role such as Storage Blob Data Contributor on the storage account. With Authentication set to Client Secret, fill in the secret; with Certificate, fill in the certificate and its private key. Put the storage account name in Account, then click Connect my account.

With Azure Cloud set to Custom, fill in Endpoint with the account name in the hostname, and an instance admin must set DUAER_AZURE_STORAGE_CUSTOM_ENDPOINTS_ENABLED=true.

## Azure Storage OAuth2 API <a href="#azure-storage-oauth2-api" id="azure-storage-oauth2-api"></a>

In Duaer, choose Azure Storage OAuth2 API when you create a credential, then fill in these fields:

- Authorization URL: Default: a preset value.
- Access Token URL: Default: https://login.microsoftonline.com/common/oauth2/v2.0/token.
- Client ID (required)
- Authentication: How Duaer authenticates to Microsoft Entra when exchanging and refreshing tokens. Certificate signs a client assertion (private_key_jwt) instead of sending a client secret. Default: Client Secret. Options: Client Secret, Certificate.
- Client Secret (required, secret): Shown when Authentication is Client Secret.
- Private Key (required, secret): PEM-encoded RSA private key paired with the certificate uploaded to the Entra app registration. Use the multiline editor, in standard PEM format: -----BEGIN PRIVATE KEY----- KEY DATA GOES HERE -----END PRIVATE KEY-----. Shown when Authentication is Certificate.
- Certificate (required, secret): PEM-encoded public certificate registered on the Entra app registration (Certificates & secrets). Used to derive the x5t thumbprint that tells Entra which key verifies the assertion. Shown when Authentication is Certificate.
- Account
- Custom Scopes: Define custom scopes. Default: off.
- Enabled Scopes: Scopes that should be enabled. Default: https://storage.azure.com/.default. Shown when Custom Scopes is on.

Duaer uses the OAuth2 Authorization Code grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

By default, Duaer requests these scopes: https://storage.azure.com/.default.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under [OAuth2 API](/integrations/builtin/credentials/httprequest.md#oauth2-api).

Duaer nodes that use it: [Azure Storage](/integrations/builtin/app-nodes/duaer-nodes-base.azurestorage.md).

## Azure Storage Shared Key API <a href="#azure-storage-shared-key-api" id="azure-storage-shared-key-api"></a>

In Duaer, choose Azure Storage Shared Key API when you create a credential, then fill in these fields:

- Account: Account name.
- Key (secret): Account key.
- Azure Cloud: Default: Azure Public Cloud. Options: Azure Public Cloud, Azure US Government, Azure China, Custom.
- Endpoint (required): The https:// URL of the storage endpoint. The account name must be in the hostname. An administrator must set DUAER_AZURE_STORAGE_CUSTOM_ENDPOINTS_ENABLED=true on this Duaer instance. Endpoints with the account name in the path, such as Azurite, do not work. Shown when Azure Cloud is Custom.

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: [Azure Storage](/integrations/builtin/app-nodes/duaer-nodes-base.azurestorage.md).

## Save the connection in Duaer

Open Credentials and create Azure Storage. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under [the related node](/integrations/builtin/app-nodes/duaer-nodes-base.azurestorage.md).

## Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.
## Questions

### Do Azure Storage secret values appear in Duaer node parameters?

No. In Duaer, Azure Storage secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

### What usually stops a Azure Storage credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Azure Storage expects, then confirm you can create credentials in that project.

