---
title: "Augure vs Azure OpenAI in Canada East: residency beyond storage"
description: "For Canadian teams weighing Azure OpenAI in Canada East against Augure: where prompts are processed, who runs the service, CAD prices, and a migration guide."
competitor: "Azure OpenAI in Canada East"
vendor: "Microsoft"
category: "cloud"
canonical: "https://augureai.ca/compare/azure-openai"
updated: "2026-10-27"
summary: "Azure OpenAI in Canada East keeps data at rest in Canada and offers OpenAI's model catalogue inside the Microsoft ecosystem; Augure is a Canadian company with no US parent, stores customer data in Canada, never routes inference to US providers, bills in CAD, and needs no cloud subscription."
faqs:
  - q: "Does Azure OpenAI in Canada East keep my prompts in Canada?"
    a: "It depends on the deployment type. Per Microsoft's documentation as of October 2026, data at rest stays in the Azure geography, but Global deployments may process prompts in any Azure region and Data Zone deployments cover only the US, EU and Asia Pacific zones. Only Standard (regional) and Regional Provisioned deployments process prompts within the Canada geography, and those carry the smallest model list."
  - q: "Which OpenAI models can I run regionally in Canada East?"
    a: "As of Microsoft's region availability page checked 2026-10-27, Standard (regional) deployments in Canada East list gpt-4.1-mini, gpt-4o (2024-11-20) and three embedding models. Regional Provisioned adds gpt-4o, gpt-4o-mini, gpt-5, gpt-5-mini, gpt-5.1, gpt-5.2 and o3-mini. GPT-5.4 and newer appear in Canada only as Global Standard, which processes anywhere."
  - q: "Is Augure a drop-in replacement for the AzureOpenAI client?"
    a: "Mostly. Augure exposes an OpenAI-compatible chat completions API at https://api.augureai.ca/v1, so you switch from the AzureOpenAI class to the plain OpenAI class, drop api_version and the deployment name, and pass an Augure model id. Tools, streaming, images, PDFs and response_format use the standard OpenAI request shape."
---

# Augure vs Azure OpenAI in Canada East: residency beyond storage

Azure OpenAI is Microsoft's hosted version of OpenAI's models, sold as part of Microsoft Foundry and deployable in the Canada East and Canada Central regions. It suits organisations already standardised on Azure, Entra ID and enterprise agreements. Augure is a Canadian AI platform and OpenAI-compatible API built for regulated Canadian work, with customer data stored in Canada and inference never routed to providers in the United States. The biggest difference is not where data sits at rest; both can keep that in Canada. It is who operates the service, where prompts are processed, and how much cloud plumbing you take on. This page is for privacy officers, CTOs and developers choosing between the two.

## At a glance

| | Augure | Azure OpenAI in Canada East |
|---|---|---|
| Company and jurisdiction | Canadian company, no US parent or investors. | Microsoft. Processing governed by the Microsoft Products and Services Data Protection Addendum, per its data-privacy page. |
| Where customer data is stored | Canada. | Data at rest stays in the designated Azure geography (Canada for a Canada East or Canada Central resource), per Microsoft's deployment types page. |
| Where inference runs | Canadian infrastructure (Ontario) and vetted EU partners under zero-data-retention; never US providers. | Depends on deployment type: Standard and Regional Provisioned process within the Canada geography; Global may process in any Azure region; Data Zone covers US, EU and APAC zones only. |
| Your data used for training | Never. | Not used to train foundation models without permission, and not available to OpenAI, per Microsoft. |
| Canadian residency option | Storage always in Canada. Accounts can be set Canada-only: requests then stay in Canada or fail with `503 residency_unavailable`, never served elsewhere. tofino-3 and the Augure Open models never leave Canada. | Choose a Standard or Regional Provisioned deployment in Canada East or Canada Central. No Canadian data zone exists as of October 2026. |
| Prompt retention for abuse monitoring | Prompts never logged by Augure. | Flagged prompts and completions may be stored for review in the resource's geography; eligible customers can apply for modified abuse monitoring. |
| API | OpenAI-compatible, https://api.augureai.ca/v1 | OpenAI SDK with `AzureOpenAI` client or an `/openai/v1/` base URL; model parameter is a deployment name. |
| Models | ossington-5 (256K), rosedale-1 (up to 1M), tofino-3, Augure Open (GLM-5.3, Qwen3.8-Flash-Next) | OpenAI catalogue from GPT-4o to GPT-6.1; regional Canadian list is far shorter (see below). |
| Context and output | 256K input (rosedale-1 up to 1M); 32,768 output tokens (tofino-3: 16,384). | GPT-5: 400K context, 128K output. GPT-6.1: 1,050,000 context, 128K output, per Microsoft's model page. |
| Tools, images, PDFs | Function calling, streaming, image and PDF input, `response_format` json_schema. | Function calling, structured outputs, text and image input, per Microsoft's model page. |
| Identity and network | API keys; SSO on Enterprise. | Microsoft Entra ID, Azure Key Vault, private endpoints, Azure Policy. |
| Languages | English and Quebec French natively. | Multilingual models; Quebec French not addressed on the Microsoft pages checked for this comparison. |
| Billing currency | CAD. | Prices calculated in US dollars and converted monthly; CAD display available. |
| Best fit | Canadian organisations that want Canadian operation and jurisdiction without running a cloud. | Azure-first enterprises that need the OpenAI catalogue and Microsoft governance tooling. |

## Where Azure OpenAI wins

- Model breadth. Microsoft's catalogue lists GPT-5, GPT-5.x, GPT-6 and GPT-6.1 families, o-series reasoning models, gpt-oss, embeddings, image, audio and video models. Global Standard deployments in Canada East cover most of the chat models; Canada Central covers GPT-5.1 and newer.
- Microsoft ecosystem. Entra ID and Azure Key Vault are Microsoft's recommended authentication path, private endpoints can take the resource off the public internet, and Azure Policy can block deployment types you do not allow.
- Enterprise commercial terms. Azure OpenAI sits under existing Microsoft agreements, with Provisioned Throughput Units for reserved capacity and a Batch API at 50 percent off Global Standard pricing.
- Context and output limits. GPT-6.1 accepts a 1,050,000-token context with 128,000 output tokens; GPT-5 accepts 400,000 input and 128,000 output. Augure caps output at 32,768 tokens.
- Compliance documentation. Microsoft publishes Azure compliance offerings and the Data Protection Addendum that governs data processing for the service.

## Where Augure wins

- Canadian company and jurisdiction. Augure has no US corporate parent and no US investors. Customer conversations, documents and AI inference are never handled by US-jurisdiction providers, so the CLOUD Act's reach over US-controlled providers does not extend to customer content.
- Processing, not only storage. Inference runs on Canadian infrastructure and with vetted EU partners under zero-data-retention agreements, never US providers. A Canada-only account fails closed instead of serving elsewhere.
- No prompt logging. Prompts are encrypted in transit, never logged by Augure and never used for training. There is no abuse-monitoring data store to apply out of.
- Quebec French. Models are built for Canadian law and Quebec regulatory context, with native Quebec French and English.
- CAD pricing and no cloud account. ossington-5 is C$1.50 input and C$3.00 output per million tokens; tofino-3 is C$0.60 and C$2.00. Plans run C$0, C$20 and C$80 per month. Keys are self-serve; there is no subscription, resource group, quota request or deployment to manage.

## Switch from Azure OpenAI to Augure

1. Create a key at https://augureai.ca/developers. Keys look like `aug_sk_live_...` and are shown once.
2. Change the client. Replace `AzureOpenAI` with `OpenAI`, set `base_url` to `https://api.augureai.ca/v1`, and drop `api_version` and `azure_endpoint`.
3. Map deployment names to Augure model ids. Azure requires a deployment name in the `model` field; Augure takes the model id directly.

| Azure deployment (model) | Augure model | Why |
|---|---|---|
| gpt-5, gpt-5.x, gpt-6 family | `ossington-5` | Reasoning tier, 256K context, fastest of Augure's reasoning models. |
| gpt-4.1 with long inputs | `rosedale-1` | Up to 1M context on every developer key. |
| o-series in agent loops | `rosedale-1` with `reasoning_effort: "low"` | Augure's recommended model for reliable tool calling. |
| gpt-4o-mini, gpt-4.1-mini, gpt-4.1-nano | `tofino-3` | Fast tier, thinking off, served in Canada with no failover outside Canada. |
| gpt-4o, gpt-4 | `ossington-4` or alias `gpt-4o` | Augure serves the `gpt-4o` and `gpt-4` aliases with `ossington-4`. |
| Unsure | `auto` | The gateway picks per request. |

4. Before and after in Python.

```python
import os

# Before: Azure OpenAI (openai SDK, AzureOpenAI client)
from openai import AzureOpenAI
client = AzureOpenAI(
    api_key=os.environ["AZURE_OPENAI_API_KEY"],
    api_version=os.environ["AZURE_OPENAI_API_VERSION"],
    azure_endpoint="https://my-resource.openai.azure.com",
)
resp = client.chat.completions.create(
    model="my-gpt-5-deployment",  # deployment name, not model name
    messages=[{"role": "user", "content": "Summarise this contract in two lines."}],
)
print(resp.choices[0].message.content)

# After: Augure
from openai import OpenAI
client = OpenAI(base_url="https://api.augureai.ca/v1", api_key=os.environ["AUGURE_API_KEY"])
resp = client.chat.completions.create(
    model="ossington-5",
    messages=[{"role": "user", "content": "Summarise this contract in two lines."}],
)
print(resp.choices[0].message.content)
print(resp.model_extra["_augure"]["inference_region"])
```

If you use Microsoft's newer `/openai/v1/` base URL with the plain `OpenAI` class, the change is only the base URL, the key and the model id.

5. Re-check these settings.
   - `max_tokens`: Augure caps output at 32,768 tokens (tofino-3: 16,384). Omit it on reasoning models so thinking does not starve the answer.
   - `reasoning_effort`: `none` turns thinking off on ossington-5 for mechanical tasks; `low`, `medium` and `high` are accepted. rosedale-1 serves `none` as `low`.
   - `response_format`: json_object and json_schema work. On reasoning models it is enforced by a prompt-level directive, so validate and retry once; do not combine with `tools` on those models.
   - Tool calling: same `tools` and `tool_choice` schema. Pin `rosedale-1` for agent loops rather than `auto`.
   - Streaming: Server-Sent Events, with `stream_options: {"include_usage": true}` for a final usage chunk. Errors mid-stream arrive as an error event.
   - Entra ID and private endpoints do not carry over. Augure uses bearer keys over TLS.
6. Run both for a week. Log `_augure.request_id` and `inference_region` per response, compare outputs on real traffic, then cut over by swapping the environment variables.

## Keep Azure OpenAI if

- You need a specific OpenAI model, GPT-6-class context windows, or 128K output tokens.
- Your identity, networking and audit controls are built on Entra ID, private endpoints and Azure Policy, and your auditors expect them.
- You rely on Provisioned Throughput reservations, the Batch API discount, or pricing under your existing Microsoft agreement.
- Data at rest in Canada is your requirement, and Global processing of prompts is acceptable to your privacy officer.

## Sources

- https://learn.microsoft.com/en-us/azure/foundry/foundry-models/concepts/deployment-types (checked 2026-10-27): data at rest stays in the Azure geography; Global processed in any Azure region; Data Zone limited to US, EU, APAC; Standard and Regional Provisioned processed within the customer-specified geography; Batch 50 percent discount; Azure Policy restriction.
- https://learn.microsoft.com/en-us/azure/foundry/foundry-models/concepts/models-sold-directly-by-azure-region-availability (checked 2026-10-27, page updated 2026-10-19): model availability by deployment type for canadaeast and canadacentral.
- https://learn.microsoft.com/en-us/azure/foundry/foundry-models/concepts/models-sold-directly-by-azure (checked 2026-10-27): model catalogue, GPT-5 and GPT-6.1 context and output limits, tool and image support.
- https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/data-privacy (checked 2026-10-27): no training on prompts, not available to OpenAI, abuse-monitoring data store in the resource geography, modified abuse monitoring, Data Protection Addendum.
- https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/abuse-monitoring (checked 2026-10-27): automated and human review process, Limited Access application.
- https://learn.microsoft.com/en-us/azure/foundry-classic/openai/how-to/switching-endpoints (checked 2026-10-27): Entra ID recommended, deployment name in the model field, `/openai/v1/` base URL form.
- https://learn.microsoft.com/en-us/azure/foundry-classic/openai/how-to/network (checked 2026-10-27): private endpoints and disabling public network access.
- https://azure.microsoft.com/en-us/pricing/details/azure-openai/ (checked 2026-10-27): prices calculated in US dollars and converted monthly; Global, Data Zone (EU or US) and Regional deployment pricing tiers; Batch API discount.
- https://github.com/openai/openai-python (checked 2026-10-27): `AzureOpenAI` client with `api_version` and `azure_endpoint`.
- https://augureai.ca/docs/api, https://augureai.ca/docs/models, https://augureai.ca/docs/agents, https://augureai.ca/docs/integrations/openai-python, https://augureai.ca/llms.txt (Augure facts, prices in CAD).