Overview

Octiga gives your MSP one place to secure and manage Microsoft 365 for every client you look after. Set the security standard you want once and Octiga keeps every tenant on it. It watches what happens in each tenant and tells you when something needs a look, and when an account or a mailbox is at risk, you fix it from the same screen. If you’re new, this page covers what Octiga does and where to start.

What Octiga does

Keeping dozens of client tenants secure by hand means checking the same settings again and again, reading the same audit logs, and hoping nothing changed quietly in between. Octiga does that work for you across every tenant at once, in four ways.

Keep every tenant on your standard

Choose the security settings that matter to you, such as MFA enforced by Conditional Access or legacy authentication blocked. Each one is a baseline, and a named bundle of them is a scheme. Deploy the scheme to as many tenants as you like, and set it as your default so each newly connected tenant gets it without anyone having to remember. Octiga checks each tenant against its baselines continuously. When a setting changes, Octiga either puts it back for you or raises an alert, and you choose which per baseline. Start with Schemes, browse the full list in Baselines, and see Deviations and Remediation for what happens when a tenant stops matching.

See what’s happening in every tenant

Octiga collects each tenant’s Microsoft 365 audit events (sign-ins, admin actions, mailbox rule changes) and grades them by how much attention they deserve. Anything graded warning or worse shows up as an alert, as does a baseline that stops passing, and Alerts lists every alert across every tenant in one place. Alerts reach your team where they already work: by email, as a ticket in ConnectWise Manage, Datto/Autotask or HaloPSA, or in the app itself. When a source turns out to be safe, an event rule quietens it so the list stays worth reading. See Events, Event rules, Alert recipients and PSA integrations.

Find and fix the accounts and mailboxes at risk

Some risks belong to one account or one mailbox rather than to a tenant-wide setting: an admin with no second factor, an account nobody has signed into for months, an inbox rule forwarding mail outside the organisation, a legacy protocol still allowed on a mailbox. Account risk and Mail flow list these findings for a tenant so you can work through them, and the remedies sit beside each one: block sign-in, reset the password, or let Octiga lock an account automatically after a serious risk event. User remedies covers the three.

Fit it to your MSP

Your administrators decide who on your team can sign in, which tenants they can reach and what they can do there, through access groups and four roles. A scheduled security report for each tenant, emailed on the cadence you choose, shows the client where they stand. See Roles and permissions, Access controls and Reports.

Two levels: MSP and tenant

Octiga works at two levels. An MSP is the service provider: you, your colleagues and the account you share. A tenant is one client’s Microsoft 365 directory, connected to Octiga. Every screen is either MSP-level, spanning all the tenants you manage, or scoped to a single tenant.

Octiga is used only by your team. Your clients never sign in, and your administrators decide who on your side has access.

Where to go next

Setting up Octiga

For administrators, in the order the work usually happens:

1. Connect each client tenant: Connect a tenant. What the client approves is listed in What Octiga needs from your tenant.
2. Give your team access with groups in Access controls.
3. Author your standard as a scheme and set it as the default, so every tenant gets it on connection (Schemes). Deploy it to the tenants you already have (Deploying a scheme).
4. Route alerts to the right people and systems in Alert recipients and PSA integrations.
5. Schedule each tenant’s report in Reports.

Working in Octiga day to day

• Each session starts on Tenants and dashboard: find a tenant, check its connection at a glance and open its screens.
• Alerts is the fleet-wide list of what needs attention. Open an alert to see where it came from and act on the user behind it.
• For one tenant, investigate its activity in Events and work through its findings in Account risk and Mail flow.
• When a baseline stops passing, Remediation puts it right, automatically or when you choose.

If you’d like to know what happens behind the scenes, How Octiga works is a good next read, and Glossary defines the terms these docs use.