Installation
Choose the deployment model that fits your security and compliance needs.
1Security offers flexible deployment options to meet your organization's compliance, data residency, and operational requirements. You can choose to run 1Security as a fully managed SaaS (Cloud), deploy it within your own Azure environment (BYOC), or host it fully On-Premise.
Prerequisites
Regardless of your chosen deployment method, you will need:
- A Microsoft 365 tenant with at least one license that includes SharePoint Online (Business Basic upwards - no E5 required)
- Global Administrator access (for the initial OAuth consent)
- Modern browser (Chrome, Edge, Firefox, Safari - last two major versions)
Full detail - which license SKUs qualify, which admin roles are used and when, every permission each module requests, and the four features that need a premium Microsoft SKU - is in Requirements.
Deployment Models
Recommended for most teams.
1Security manages the infrastructure, updates, and maintenance. You simply log in and connect your tenant.
- Zero infrastructure to manage.
- Continuous updates with no downtime.
- Setup takes less than 5 minutes.
- Hosted in secure, SOC 2 Type II compliant environments.
Getting Started
Create your account
Go to 1security.ai and sign up using your Microsoft work account. We use OAuth - your password never leaves Microsoft.
Grant tenant permissions
During the consent dialog, an admin in your tenant approves the permissions 1Security needs to read your Microsoft 365 metadata. We never request write access to user data without an explicit per-action prompt.
Run your first scan
Once connected, the platform automatically queues an initial scan. You'll see results stream in over the next few minutes.
Granting consent requires Global Administrator privileges. If you're not a global admin, ask one to complete the consent flow - you can still own day-to-day operations afterwards.
Verifying the install
After the consent flow and environment setup finish, you should land on the dashboard with at least the following populated:
- Tenant card showing your tenant ID and domain
- Scan status showing "Running" or "Queued"
- Users count matching what you see in the Microsoft 365 admin centre (give it a minute to sync)
If any of these are missing, see connecting tenants for troubleshooting.