Deployment & IT FAQ
How Arivu deploys inside enterprise environments — covering installation, permissions, governance, and common IT questions.
Deployment Model
Arivu is deployed as an in-tenant Legal AI service that integrates directly with Microsoft 365. There is no data migration, re-indexing, or external content storage required.
- Deployed within the customer’s Microsoft 365 tenant
- Uses Microsoft Graph APIs and Entra ID for authentication
- No persistent storage of customer documents or prompts
- No background crawling or scheduled ingestion jobs
- Supports phased rollout by department or matter
IT & Security FAQ
Does Arivu copy or index our SharePoint data?
No. Arivu queries documents just-in-time using existing permissions. Nothing is copied, indexed, or stored outside your tenant.
What permissions does Arivu require?
Arivu uses delegated user access via Entra ID. It operates only within the permissions of the signed-in user.
Is customer data used to train AI models?
No. Customer data is never used for training. AI inference is performed with ephemeral context only.
Can Arivu be restricted to specific SharePoint sites or folders?
Yes. Arivu fully honors SharePoint permissions and ethical walls. If a user lacks access, Arivu cannot surface that content.
How does Arivu support audits and compliance?
All AI interactions can be logged for audit purposes without storing underlying document content.
How long does deployment take?
Most deployments complete within days, not months. No data migration or model training is required.
Can IT disable or revoke access?
Yes. Access is governed entirely through Microsoft 365 identity and permission controls.
Designed for Enterprise IT
Arivu aligns with existing enterprise controls, enabling Legal AI adoption without introducing new governance or security risks.
IT-Approved Legal AI
Arivu deploys cleanly into Microsoft 365 environments with security, auditability, and control as first principles.