MSP-safe Microsoft 365 automation, built for trust

Automation only earns trust when it is safe. Avvi is built around approval controls, least-privilege access, full audit logging, and strict isolation between every client tenant.

Join the Beta Program

Aligned with SOC 2 controls

SOC 2 is an AICPA examination framework covering Security, Availability, Processing Integrity, Confidentiality, and Privacy. Avvi uses these categories to organize its control posture. Avvi is aligned with SOC 2 controls; it has not completed an independent SOC 2 examination and is not SOC 2 certified.

Security

Least-privilege access control via GDAP and fine-grained permission toggles, with no standing Global Administrator access and encrypted secrets.

Confidentiality

Strict isolation between every client tenant, with least-privilege access throughout.

Processing Integrity

Role-based approvals and controlled execution, recorded in a full audit trail.

Privacy

Every action stays bounded by MSP-controlled permissions assigned to the requester.

Availability

Durable long-term retention of action records. Uptime specifics on request.

Avvi is aligned with SOC 2 controls. This describes Avvi’s current control posture only; it is not an independent audit report, attestation, certification, or verification.

The controls behind every action

Avvi is designed so the safe outcome is the default one, across every tenant you manage.

Multi-tenant by design

Manage every client tenant from one place through GDAP, with strict isolation between them.

Four-level permission hierarchy

Granular control over who can do what, across every tenant.

least-privilege access controls

Access is verified and scoped to what each user is permitted.

Full audit logging

Every action is recorded with the confirmation and relevant action details for review and accountability.

Encrypted secrets management

Credentials and secrets are protected with industry-standard encryption, centrally managed.

Long-term retention

Audit records are retained for 400 days in the normal course and for seven years when maintained as compliance records.

How a safe request actually flows

Every request Avvi runs passes the same controls, in the same order. Nothing skips the line.

1

Ask in chat

A technician or an approved end user asks Avvi to run a Microsoft 365 task, in Teams or the web portal. No scripts to write, no admin console to open.

2

Delegated access with MSP controls

Avvi uses delegated GDAP admin access and limits each request through the permissions the MSP controls for that user.

Least privilege
3

Yes or No confirmation before every action

Actions that warrant a second set of eyes route through a role-based approval before anything executes.

Role-based approval
4

Controlled execution

Once cleared, Avvi performs exactly the requested task through Microsoft’s delegated APIs. It runs the specific task in front of it, nothing broader.

5

Logged and retained

The action is written to the audit trail with what changed, who approved it, and when, then retained as durable compliance evidence.

Full audit trail

Multi-tenant isolation is the trust story

An MSP does not manage one Microsoft 365 tenant, it manages many, each belonging to a different client. Avvi manages them through GDAP with strict isolation between them, so one login never crosses a boundary it should not.

That isolation model is what lets you answer a security questionnaire without hedging. It is not a technicality, it is the product.

Read the multi-tenant guide →
How the isolation holds
Managed through Microsoft GDAP, not standing global admin
Strict isolation between client tenants
A four-level permission hierarchy on top
Every critical action logged and retained

What Avvi can and cannot do in your tenants

Avvi does not sit above your Microsoft 365 environment with its own keys to everything. It acts through the delegated access you grant, scoped to the task in front of it, and it records what it did.

That boundary is deliberate. It keeps the answer to “what could this tool reach” short and honest.

See the security FAQ →
The access boundary
Acts through Microsoft GDAP delegated access, scoped to the task
Holds no standing global admin over your tenants
Bounds every action by MSP-controlled permissions assigned to the requester
Encrypts credentials and secrets with industry-standard encryption
Logs and retains every critical action as your compliance evidence

Microsoft 365 security, the common questions

Is it safe to let AI automate Microsoft 365 administration?
It is when the automation runs through delegated GDAP admin access, limited by MSP-controlled permissions. Avvi never acts outside MSP-controlled permissions assigned to the requester, every action requires a Yes or No confirmation before execution, and actions are logged. Avvi uses delegated GDAP admin access rather than standing Global Administrator access.
How does Avvi access client Microsoft 365 tenants?
Through Microsoft GDAP, the granular delegated admin model Microsoft built for MSPs. Access is scoped per tenant and per role, with no standing global admin, and every delegated action is auditable.
Does Avvi use Global Admin or standing admin access?
No. Avvi works with least-privilege access delegated through GDAP. It acts through delegated GDAP admin access, limited by MSP-controlled permissions, so it can never do something the person asking could not already do by hand.
Is Avvi SOC 2 certified?
No. Avvi is aligned with SOC 2 controls, but it has not completed an independent SOC 2 examination and is not SOC 2 certified. The Security page describes Avvi’s current control posture, not an audit opinion or certification.
Are Avvi’s audit logs ready for a compliance review?
Avvi records each action with its confirmation and relevant action details. Audit records are retained for 400 days in the normal course and for seven years when maintained as compliance records. Your organization should determine whether the available records meet its own contractual, regulatory, or audit requirements.
How does Avvi keep one client’s tenant separate from another?
Avvi manages each client through its own GDAP relationship with strict isolation between tenants, so one login never crosses into another client’s environment.
What Microsoft 365 data can Avvi see?
Only what the delegated access you grant allows, scoped to the task in front of it. Avvi does not hold its own keys to everything. It acts through Microsoft’s APIs within the permissions you set.
Can an end user do more through Avvi than they are allowed to?
No. Every request runs inside that user’s own permission scope, and sensitive actions still route through a role-based approval. Avvi cannot become a way around your controls.

See safe automation for yourself

Book a walkthrough and watch Avvi run real Microsoft 365 work with approval controls, isolation, and a full audit trail.

Book a Demo → Explore the platform →