AristoContosoIllustrative · read-only
Perspective
ExecutiveFinanceIT & SecurityTeam leadRaw
Illustrative · read-only
Settings · make the numbers yours

Every seat dollar in your reports uses $30 a seat until you set your real price.

Your Copilot seat price

What you pay Microsoft per seat per month, from your order form.
assumption until saved

Who may see the organization's numbers

Sponsors see every report. Everyone else sees only their own page.
When you save, every seat dollar in the three reports and the Traffic Lights is re-priced the same minute, and the "assumption" marks turn into "counted". Reports already frozen, decks already exported and cards already delivered keep the figures they were made with.

4 of 12 dials set by your organization

counted from your saved settings
set by your organization 4still the platform default 8

Every answer, narrative, skill and agent draft runs on Aristo-hosted Azure OpenAI.

AI model

The model behind every answer, narrative, skill and agent draft — Aristo-hosted, or your own Azure OpenAI.

Aristo-hosted
Running now
Aristo-hosted · gpt-5
assumption
Aristo-hosted (Azure OpenAI)

Azure OpenAI in Aristo's own Azure subscription. Nothing to set up, included in your plan.

A backup model answers only if your organization has asked for it and the first model fails: the prompt then goes to Anthropic's model through Microsoft Foundry, and Anthropic operates the model and processes the prompt. With the switch off, nothing crosses to the other vendor; a pinned organization never crosses, even with the switch on.

Models on Aristo's Azure: gpt-5, gpt-5-mini, gpt-5-nano.

Bring your own Azure OpenAI

Your Azure subscription pays for chat; add an embeddings deployment to bill embeddings there too, otherwise they stay on Aristo's Azure as platform-metered usage. Every deployment is checked before saving.

What you would enter: the endpoint from your resource's Keys and Endpoint page, the chat deployment name, an optional embeddings deployment, and the key — which is checked and sealed, never shown again.

This is the illustrative organization — it is never written to, so there is nothing here to set. In your own tenant this control writes the same field the classic settings screen writes, records the same audit action, and every surface that reads the setting moves with it.

Other vendors or private models are arranged through your Aristo contact at your organization's request.

One model choice, one history — whichever settings screen it is saved on. Whichever model runs, Aristo shows aggregates by default and names a person only where your organization has turned on named recognition and that person has agreed.

This is the illustrative organization, so nothing here is saved — in your own tenant each of these saves right here, in place, and the History tab keeps who changed it and when.

GitHub Copilot — is it yours?
Aristo cannot infer a GitHub Copilot seat from Microsoft 365. Your organization declares the answer; it is attributed and audited.
Read-only in the example organization. Recording a declaration here would write to a tenant that is not yours, so the choices are shown but cannot write. Connect your own tenant to record the declaration.
Aristo cannot see GitHub Copilot from here. Your Microsoft 365 licenses say nothing about it — it is a separate seat on a separate system we do not connect to — so we are not going to guess either way. If you have it, this route is open to you; if you are not sure, your GitHub admin knows.
Recording is local, but the recorder’s Analyze step sends frames, window titles, URLs and your narration to GitHub’s cloud — so never record credentials, secrets or tenant-sensitive screens. Aristo only ever receives the SKILL.md you bring back.
Only a leader can set this, it applies to your whole organization, and every change is written to your audit trail with your name on it.