Skip to content

Microsoft 365 Copilot

The most constrained provider in the set, and documented as such rather than papered over.

streaming structured output (prompt-only) tool calls health (deliberately no-op) discovery

Setup

pip install "anyinfer[azure]"

client = ai.Client([
    ai.ProviderSettings.of(
        "m365-copilot",
        options={"tenant_id": "...", "client_id": "..."},
    ),
])
result = client.generate(prompt, target="m365-copilot:m365-copilot")

Alias: m365.

Interactive authentication only

There is no client-credential or daemon flow for this API. Sign-in opens a browser.

Consequences, stated plainly:

  • It cannot run headless, in CI, or in a container without a human present.
  • It is exempt from live conformance testing.
  • health() deliberately does not trigger a sign-in — a health probe that opens a browser window would be a hostile surprise, and the router calls it speculatively.

If you already hold a token, supply it and skip the interactive flow:

ai.ProviderSettings.of("m365-copilot", api_key="env://M365_TOKEN")

This is the only workable path for automated use.

What it supports

Behavior Support
Streaming No — a whole response, emitted as one delta
Structured output Prompt-injected only
Tools No
Sampling controls Ignored by the service
Usage Generally absent

Ignored parameters are reported

Temperature, top-p, max tokens, stop sequences, tools, and reasoning effort are declared on the descriptor as ignored, so requesting them emits a ParameterDropped telemetry event rather than silently doing nothing:

class Watch:
    def on_event(self, event):
        if isinstance(event, ai.ParameterDropped):
            log.warning("%s ignored %s", event.target, event.parameter)

This is the whole point of that event: a temperature=0 that had no effect is otherwise indistinguishable from one that worked.

Notes

  • Citations and attributions are retained on result.raw rather than normalized — build the client with retain_raw=True to keep them, since raw payloads are discarded by default. v1 has no typed model for them, and inventing one would freeze a shape before it is understood.
  • A 401/403 hints at both re-authentication and the tenant licensing and admin-consent requirements, because those are the usual real causes.

When to use something else

If you need automation, streaming, tools, or sampling control, use another provider. This adapter exists so that applications with a genuine M365 Copilot requirement can reach it through the same interface — not because it is a good default.

Wire contract

For the exact request/response fields this adapter depends on, see contracts/m365-copilot.md.