Eva in Microsoft Teams

At a glance

01What Eva in Teams is

Eva is Evergrowth's AI assistant for revenue teams. The Microsoft Teams app is an additional client for the same Eva your users already have at app.evergrowth.com. It is a different way to reach a system the user is already entitled to use, which means your existing Evergrowth access review continues to govern it.

It is delivered as a standard Microsoft Teams bot on Azure Bot Service. Today it operates in 1:1 personal chat only: the app package declares the personal scope and nothing else, so Eva cannot be added to a team channel or a group chat. Channel support will arrive with the Microsoft Teams Store listing as a new, separately reviewable version of the app.

02What the app can access inside Microsoft 365

The app package requests exactly one Teams permission: identity.

Nothing is written into or retained inside Microsoft Teams beyond the messages of the conversation itself.

03How a person is authorised

Authorisation is anchored to your existing Evergrowth entitlements, in three steps.

1. Tenant binding. A Microsoft 365 tenant is bound to exactly one Evergrowth workspace. The binding is established on first use by a person who is already a member of that workspace, and is retired automatically when the app is removed from the tenant.
2. User matching, on every message. The sender's Microsoft 365 email address is resolved to an existing Evergrowth user within that bound workspace. Where no matching Evergrowth account exists, Eva does not answer; she replies that the person must be added by an Evergrowth administrator. Matching never crosses workspaces and is refused outright where it would be ambiguous.
3. Least privilege. Eva then operates under a per-user access token whose capabilities are derived from that individual's own role and permissions in Evergrowth. Eva in Teams can see and do exactly what that person can see and do when logged into the Evergrowth web application, and nothing more. Revoking or downgrading an Evergrowth account immediately changes what Eva will do for that person in Teams.

This matters for your review: Eva in Teams adds no new access path to your data. It inherits the one you have already approved.

04What Eva accesses on the Evergrowth side

All of it is your own Evergrowth workspace data, subject to the per-user permissions above. Each customer workspace is logically isolated; every record carries a company identifier and access is validated against the requesting organisation before any record is returned.

05Personal data processed

The platform neither requests nor requires payroll, employee, health or payment card data at any point. Personal data processing is limited to business contact and professional profile data for people matching the ICP and buyer personas you approve.

What actually reaches a model is narrower still: the personal data in a prompt is limited to what the qualification decision requires, being name, job title, LinkedIn profile and employer. No profile photograph, no employment history and no special category data is sent to a model.

Two qualification gates run inside the workspace before any external source is called: the company must match the profile you approved, and the person must match a persona you defined. Minimisation is therefore applied at the point of collection rather than afterwards, under Article 5(1)(c), and the reason each contact qualified is recorded at that moment.

06Data flow and transport security

Every inbound request from Microsoft is cryptographically authenticated before it is processed:

• An RS256 JSON Web Token issued by the Bot Framework service, validated against Microsoft's published signing keys.
• Issuer pinned to https://api.botframework.com, and audience pinned to Evergrowth's own bot application ID, so a token minted for a different bot is rejected.
• The token's serviceurl claim must match the service URL on the activity itself, so a captured token cannot be replayed against a different connector.
• Activities are de-duplicated by message ID, so a replayed message is not processed twice.

More broadly, every request into the platform enters through a signed JWT or a service API key carrying the requesting user's organisation identifier, which scopes all downstream access. Users authenticate through a dedicated identity provider, with two-factor authentication available by authenticator app or emailed code.

07AI processing and model providers

Eva's inference is served exclusively by enterprise model endpoints, all operating under contractual terms that prohibit training on your data. There are no consumer endpoints and no providers in non-aligned jurisdictions.

Which endpoint serves a given request depends on the task. Where a customer requires processing pinned to EU regions, that is scoped jointly and recorded as a written amendment to the Data Processing Agreement (see section 8).

Safeguards against AI-specific risks

• Prompt injection. System prompts are authored, peer-reviewed, versioned and loaded server-side from a controlled registry. Third-party content, including web pages, CRM records and search results, enters the model strictly as data inside delimited user-message blocks, never concatenated into the system prompt. Outputs are bound to typed schemas, so an injected directive cannot reach a downstream system as free-form text. Maps to OWASP LLM01 and LLM05.
• Excessive agency. Narrow per-agent tool sets, no code execution, filesystem or shell. Maps to OWASP LLM06.
• Workspace-scoped retrieval. Vector retrieval and embeddings are scoped per workspace and never shared across tenants.
• Traceability. Every agent run produces a structured trace covering prompt version, tool calls, inputs, outputs, latency and token usage, captured in a monitored pipeline.
• EU AI Act. Evergrowth's agents perform B2B research, qualification and copy generation, and do not make decisions in the Annex III high-risk domains. A human reviews any action affecting external parties.

08Hosting, residency and retention

• Infrastructure. Workloads run on AWS with KMS-encrypted secrets and cluster-level audit logging. Persistent stores use managed PostgreSQL with KMS encryption at rest and Multi-AZ availability for primary databases. Data is encrypted in transit and at rest.
• Model routing. Default agent inference runs on AWS Bedrock in eu-west-1, Ireland, which does not store prompts or completions.
• Transfers. Some processing takes place outside the EEA and the UK where necessary to provide the service. Any such transfer is made under Standard Contractual Clauses or other appropriate safeguards under Chapter V of Regulation (EU) 2016/679, and sub-processors outside the EEA and UK are required to provide equivalent safeguards (DPA clauses 5.1 and 5.2).
• EU-only on request. Processing can be pinned to EU regions for customers with a data residency requirement. Scope, timeline and any commercial impact are agreed in writing and recorded as an amendment to the Data Processing Agreement before the commitment is made. A US-only equivalent exists through the same mechanism.
• Retention and deletion. On expiry of the agreement personal data is returned or deleted at your choice, and sub-processors are required to do the same. Absent a written request, all personal data is permanently deleted within 30 calendar days of termination (DPA clauses 9.1 and 9.2).
• In-product deletion. A user can delete an Eva conversation thread, which removes the thread and its stored agent state.

09Sub-processors

Four categories of sub-processor receive data, and each receives only what its function needs.

Each sub-processor is named, with its country of processing, in the sub-processor register, which Evergrowth provides on request and during a security review. Under DPA clause 4.2 the register is maintained and you are notified of material changes, with a right to object on reasoned grounds within seven calendar days. Evergrowth remains fully responsible for its sub-processors under clause 4.4.

10Certifications and compliance

11Controls your IT team retains

• Installation is admin-gated. The app package is uploaded by a Microsoft 365 or Teams administrator through the Teams admin center.
• Scope it to named users. Standard Teams app permission and setup policies apply, so the app can be limited to a pilot group rather than the whole tenant.
• Removal is immediate and complete. Removing the app from the tenant retires the workspace binding.
• Nothing to revoke in Entra. Because no Microsoft Graph application permissions and no tenant-wide consent are requested, Evergrowth holds no standing Microsoft 365 data permission.
• Evergrowth entitlements remain the control plane. Only people who already hold an Evergrowth account can use Eva in Teams, and only within their own permissions.
• Audit trail. Access and processing activities are logged and monitored, and every agent run is individually traceable.

12Technical appendix

13Available on request

• SOC 2 Type 2 report and ISO 27001:2022 certificate.
• Current sub-processor register, naming each sub-processor and its country of processing.
• Full OWASP LLM and EU AI Act control mapping, under NDA.
• A technical walkthrough of the architecture with your security team.
• Master Services Agreement and the Data Processing Agreement annexed to every customer contract.