Quinzee Cloud

Connect an Azure application

Keep familiar client libraries and make the local environment explicit.

Use the supported SDK contract

Quinzee supports specific Azure SDK operations and API versions, not every operation exposed by every client library. The product compatibility application locks its tested package versions. Review those versions with each release.

Application credentials

For service-to-service code, use a local tenant, application/client ID and client secret. The current implementation also supports browser PKCE/device sign-in and managed identities. ARM and Service Bus enforce supported scoped roles; other data planes have their own documented limits.

The following is an illustrative SDK pattern. Obtain credentials and endpoint settings from your local environment; do not use a real Azure tenant for a local test.

var credential = new ClientSecretCredential(
    tenantId, clientId, clientSecret,
    new ClientSecretCredentialOptions {
        AuthorityHost = new Uri(localAuthority)
    });

var blobs = new BlobServiceClient(
    new Uri(localBlobEndpoint), credential);

Trust and name resolution

A prepared client container resolves supported Azure-style service names locally and trusts the development CA. TLS peer and hostname verification stay enabled. Do not work around connection failures by disabling certificate verification.