Skip to main content
Audact
See the offer

Connector · Azure Marketplace

Deploy it from the catalogue you already buy through.

Planned · no date set

For an organisation that buys through Microsoft, procurement is often the longest part of a deployment. A marketplace listing turns that into a transaction you already have a process for: deploy into your own tenant in Frankfurt or West Europe with an ARM template, wrap the Azure OpenAI and AI Foundry workloads you already run, and bill it through the agreement you already signed.

The deployment shape

{
  "$schema": "https://schema.management.azure.com/.../deploymentTemplate.json#",
  "parameters": {
    "region":        { "value": "germanywestcentral" },
    "tenantSlug":    { "value": "acme-eu" },
    "policyPacks":   { "value": ["aia-50", "gdpr"] },
    "evidenceExport": { "value": "eventhub" }
  }
}

Worked example. Acme GmbH and Nova Industries are fictional; no customer data appears here.

The region parameter is the one that matters for a European buyer: primary application hosting is Frankfurt, and the Trust Center lists the subprocessors involved either way.

What the listing will carry

ARM template deployment into your Azure tenant, Frankfurt or West Europe.
Planned
Governance wrapped around Azure OpenAI, AI Foundry and Azure-hosted voice or chat workloads.
Planned
Billing through your existing Microsoft agreement; commitment eligibility planned once listed.
Planned
The governance itself (disclosure, gate, eligibility, receipts) does not depend on the listing; it is In controlled testing (Germany: national policy layer active. Netherlands: in development. Belgium and Austria: planned.).
In controlled testing

Who it is for

When the blocker is the purchase order, not the product.

Enterprises with a Microsoft commitment have a strong reason to buy through it, and a new vendor outside that channel is a procurement project rather than a decision. A listing does not make the software better; it makes the decision smaller.

It also suits ISVs building on Azure who want to embed governance into their own offer rather than ask each customer to contract separately.

Setup

Five steps, once the listing is live.

  1. Find Audact in the Azure Marketplace catalogue.
  2. Deploy via the ARM template: Frankfurt or West Europe.
  3. Connect Audact to Azure OpenAI, AI Foundry or your Azure-hosted voice and chat stack.
  4. Configure the per-jurisdiction policy packs and the evidence export.
  5. Billing runs through your Azure agreement.

Questions

Is Audact listed today?
No. The listing is planned and pre-listing onboarding is what is underway. Until then the product is bought directly, and the software itself is the same either way.
Does spend count towards a Microsoft commitment?
That is planned once the listing exists and it is Microsoft's determination, not ours. This page will state it as a fact when it is one.

The same primitives, without the connector

A connector is a shorter path into one platform. Underneath it are six endpoints that run inside the managed platform, and an evidence chain that is identical either way.

See the API

Related