Overview
The TechWolf Analyst Agent is reached through Microsoft 365 Copilot. This page explains how that integration connects a user in Copilot to the agent. For what the agent itself does, see What is the TechWolf Analyst Agent?. Copilot is a delivery surface: it changes where a user reaches the agent, not what the agent is, what data it reasons over, or where that data is processed. The integration has three parts:- A delivery surface, Microsoft 365 Copilot, through which the user reaches the agent.
- A thin integration layer at TechWolf that authenticates the user, routes them to their region, and relays the conversation. It holds no business logic and does not interpret or store agent content.
- The Microsoft transport that carries Copilot messages to TechWolf (Microsoft Azure Bot Service), operating over TLS 1.2+ in both directions.
Architecture
A Copilot turn travels through the following path: The only component in your Microsoft 365 tenant is Copilot itself, where the user works. The Microsoft transport that carries the turn (the Entra SSO app, Azure Bot Service, and Azure Front Door) runs in TechWolf’s own Azure tenant, not yours. TechWolf operates backends in two regions, EU and US. Azure Front Door is the only cross-cloud hop: keyed on the tenant identifier, it routes each turn to the correct regional backend. Everything from the integration layer onward is TechWolf on AWS, in the single region your tenant is bound to.What each hop does, and what it holds
No agent content or business logic is stored outside the region your tenant is
bound to.
Identity and access
Two independent checks gate every turn. The integration does not broaden what any user can see.- Microsoft authentication. Every turn carries a verified Entra identity. The inbound message is cryptographically validated before any processing; no anonymous or unauthenticated request reaches the agent.
- TechWolf authorization. The verified user is resolved through TechWolf’s central identity and access service to a canonical TechWolf user and their access scopes, the same roles and entity-level grants that already govern that user’s TechWolf access today. The customer tenant is resolved from the Entra tenant identifier.
- The existing data filter still applies. The agent’s per-user, entity-scope data filtering runs downstream on every turn, regardless of how the user reaches the agent. Reaching the agent through Copilot grants no additional access.
Restricting access to data sources
Dataset entitlements are enforced server-side on every endpoint, default-deny and applied per tenant. A tenant scoped to Market Intelligence receives only Market Intelligence; a request for a dataset outside the subscription returns an explanation of what is not covered rather than a partial answer. Access is read-only by construction: the agent cannot execute actions in any HR system.Restricting specific user groups within a tenant to a subset of data
sources is a roadmap item rather than a capability available today.
Entitlements are applied at the tenant level.
Data residency and data flow
TechWolf operates regional backends in the EU and the US. Each tenant is bound to a single region, keyed on its verified Entra tenant identifier, and every turn from that tenant is served there, with model inference served by the in-region Amazon Bedrock inference profile. What crosses the Microsoft boundary:- Inbound: the user’s message text and their verified identity (email address and Entra tenant identifier).
- Outbound: the agent’s response, as the user reads it in Copilot.
Security and data-isolation controls
The integration’s controls fail closed. When a precondition cannot be safely met, the turn is blocked rather than allowed to proceed in a degraded state. Each control is enforced on every turn.- Tenant isolation. Every turn carries the verified per-user identity, and the entity-scope data filter applies downstream. Cross-tenant data retrieval is architecturally prevented.
- Regional data residency. Routing is keyed on the verified Entra tenant identifier. A request that cannot be mapped to a configured region is rejected, never defaulted.
- Verified identity on every turn. No request is processed with an unresolved or elevated identity.
- Scoped access. Bounded by Microsoft SSO combined with TechWolf’s tenant and entity-level scoping, the access model that already governs the user’s TechWolf access.
- Availability and continuity. Connectivity is per-turn and stateless, and conversation continuity is preserved via a stable conversation identifier. The runtime runs across multiple availability zones and restarts automatically.