---
product: Chilkat
product_version: 11.7.0
language: powerbuilder
language_label: PowerBuilder
class: AuthAzureStorage
license: bundle
deprecated: false
reference_html: https://www.chilkatsoft.com/refdoc/powerbuilder_AuthAzureStorageRef.html
---
# Chilkat AuthAzureStorage — PowerBuilder — v11.7.0

> Chilkat 11.7.0 · language=powerbuilder · class=AuthAzureStorage
> Other versions: replace `11.7.0` in this URL. Other languages: `https://www.chilkatsoft.com/ai-docs/v/11.7.0/<lang>/classes/AuthAzureStorage.md`.
> Language-wide rules (install, unlock, error model, strings/bytes): `https://www.chilkatsoft.com/ai-docs/v/11.7.0/powerbuilder/guide.md`.

## Purpose

**Authenticate Azure Storage REST requests with account-key Shared Key signing.**

`Chilkat.AuthAzureStorage` is a credential object for Azure Storage Services authentication. It stores the storage account name, Base64 account access key, Azure Storage service type, authentication scheme, and `x-ms-version` API version used when signing REST requests for Blob, Queue, File, or Table storage.

**Azure Storage credentials**

Hold the storage account name and Base64 account access key used to sign Azure Storage REST requests.

**Shared Key signing**

Configure Azure Storage authentication using `SharedKey` or `SharedKeyLite`, depending on the service and request style.

**Service targeting**

Specify the Azure Storage service being accessed, such as `Blob`, `Queue`, `File`, or `Table`.

**API version header**

Set the `x-ms-version` value required by the Azure Storage REST API version being used.

**REST integration**

Use the configured object with `Chilkat.Rest` so requests are signed automatically before being sent.

**Low-level control**

Pair this authentication object with manually constructed REST requests when application code needs direct control over Azure Storage operations.

**Common pattern:** Create an `AuthAzureStorage` object, set the storage `Account`, Base64 `AccessKey`, `Service`, `Scheme`, and `XMsVersion`, then attach it to a `Chilkat.Rest` request workflow. Use `AuthAzureStorage` for Shared Key authorization headers; use `Chilkat.AuthAzureSAS` when the request should be authorized with a SAS query token instead.

For an extended overview, see [AuthAzureStorage Class Overview](https://www.chilkatsoft.com/authazurestorage_class_overview.asp).

## Object creation, unlocking and error handling

**Object Creation**

```powerbuilder
oleobject loo_AuthAzureStorage
integer li_rc

loo_AuthAzureStorage = create oleobject
li_rc = loo_AuthAzureStorage.ConnectToNewObject("Chilkat.AuthAzureStorage")
if li_rc < 0 then
    destroy loo_AuthAzureStorage
    MessageBox("Error","Connecting to COM object failed")
    return
end if

// ... use loo_AuthAzureStorage ...

destroy loo_AuthAzureStorage
```

PowerBuilder uses the Chilkat ActiveX through an `oleobject`: declare the variable, `create` it, connect it to the Chilkat class with `ConnectToNewObject`, and `destroy` it when finished. A negative return code from `ConnectToNewObject` means the ActiveX is not registered, or the registered ActiveX does not match the bitness (32-bit or 64-bit) of the PowerBuilder target.

Objects returned by methods (such as an `HttpResponse` or `JsonObject`) are also `oleobject` variables and must likewise be destroyed. A method that fails to return an object returns `null`; test with `IsNull()`. In the signatures on this page, the Chilkat class name identifies which object is expected or returned; the PowerBuilder variable type is always `oleobject`.

To bind to a specific major version of Chilkat, append the major version number to the ProgID, such as `ConnectToNewObject("Chilkat.AuthAzureStorage.11")` for Chilkat v11.\*.\*.

Members typed `blob` exchange binary data as a Variant byte array. The PowerBuilder examples instead use the `BinData`-based alternatives (methods ending in *Bd*), which keep binary data inside Chilkat objects.

Call `Global.UnlockBundle` once at the start of the program, before using this or any other Chilkat class. Any string unlocks a fully functional 30-day trial; a purchased unlock code is used in production. See `guide.md` for the exact code in PowerBuilder.

How failure is reported depends on the method's return type and is stated in the note under each method below. In every case the diagnostic text is in the `LastErrorText` property of the object whose method was called.

## Members common to every Chilkat class

Documented once per language in `common-members.md`; listed here so this page is self-contained.

| Property | Signature | Access | Meaning |
|---|---|---|---|
| `DebugLogFilePath` | `string DebugLogFilePath` | read/write | If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. |
| `LastBinaryResult` | `blob LastBinaryResult (read-only)` | read-only | This property is mainly used in SQL Server stored procedures to retrieve binary data from the last method call that returned binary data. |
| `LastErrorHtml` | `string LastErrorHtml (read-only)` | read-only | Provides HTML-formatted information about the last called method or property. |
| `LastErrorText` | `string LastErrorText (read-only)` | read-only | Provides plain text information about the last called method or property. |
| `LastErrorXml` | `string LastErrorXml (read-only)` | read-only | Provides XML-formatted information about the last called method or property. |
| `LastMethodSuccess` | `long LastMethodSuccess` | read/write | Indicates the success or failure of the most recent method call: `1` means success, `0` means failure. |
| `LastStringResult` | `string LastStringResult (read-only)` | read-only | In SQL Server stored procedures, this property holds the string return value of the most recent method call that returns a string. |
| `LastStringResultLen` | `long LastStringResultLen (read-only)` | read-only | The length, in characters, of the string contained in the LastStringResult property. |
| `VerboseLogging` | `long VerboseLogging` | read/write | If set to `1`, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. |
| `Version` | `string Version (read-only)` | read-only | Version of the component/library, such as "10.1.0" |

## Member index

| Member | Kind | Signature |
|---|---|---|
| `AccessKey` | property, read/write | `string AccessKey` |
| `Account` | property, read/write | `string Account` |
| `Scheme` | property, read/write | `string Scheme` |
| `Service` | property, read/write | `string Service` |
| `XMsVersion` | property, read/write | `string XMsVersion` |

## Properties

### AuthAzureStorage.AccessKey

`Chilkat 11.7.0 · powerbuilder · AuthAzureStorage · AccessKey · property · read/write · since 9.5.0.58`

```powerbuilder
string AccessKey
```

A valid base64 access key for the Azure storage account.

### AuthAzureStorage.Account

`Chilkat 11.7.0 · powerbuilder · AuthAzureStorage · Account · property · read/write · since 9.5.0.58`

```powerbuilder
string Account
```

The Azure storage account name. (A storage account can contain zero or more containers. A container contains properties, metadata, and zero or more blobs. A blob is any single entity comprised of binary data, properties, and metadata. )

### AuthAzureStorage.Scheme

`Chilkat 11.7.0 · powerbuilder · AuthAzureStorage · Scheme · property · read/write · since 9.5.0.58`

```powerbuilder
string Scheme
```

Can be `SharedKey` or `SharedKeyLite`. The default value is `SharedKey`.

### AuthAzureStorage.Service

`Chilkat 11.7.0 · powerbuilder · AuthAzureStorage · Service · property · read/write · since 9.5.0.58`

```powerbuilder
string Service
```

Can be `Blob`, `Queue`, `File`, or `Table`. The default is `Blob`.

**Note:** Authentication for the `Table` service did not work in versions prior to v9.5.0.83.

### AuthAzureStorage.XMsVersion

`Chilkat 11.7.0 · powerbuilder · AuthAzureStorage · XMsVersion · property · read/write · since 9.5.0.58`

```powerbuilder
string XMsVersion
```

If set, automatically adds the `x-ms-version` HTTP request header to Azure Storage requests. The default value is `2014-02-14`.

