Microsoft 365 operations for MSPs
How an MSP uses TenantVigil to move between customer tenants, own service work, plan changes and report what happened.
TenantVigil only reads your Microsoft 365 tenant. It never changes a setting: you apply each fix yourself.
Need a hands-on starting point?
Start with one tenant or talk to the team if you want help evaluating fit, permissions, or rollout approach.
One console for customer work
TenantVigil reads each customer's Microsoft 365 configuration and reports which of the security checks pass, which fail, and which it could not read. Findings stay with the customer and the people allowed to reach that customer.
From one portal home, you move between the customer tenants your current access allows. You can search and filter the customers you may reach, pick up assigned work from your own queue, and open a customer without another login.
Control access and changes
Partner admins see every customer the MSP owns. Members see only the customers assigned to them. A customer sees a plain-English explanation of the access it has granted.
Changes are staged as exact plans with safety checks and scoped approval. After the required Microsoft setup, an approved change runs through a customer-bound broker and records what was attempted and what Microsoft returned.
Some Microsoft changes have no supported API. Mail forwarding, FullAccess, SendAs, distribution-list membership and an unsupported organisation setting are made manually by a technician and reported back.
Show the work
You can produce branded recurring service reports and a stored security evidence pack with a freshness receipt. Customers sign in with Microsoft to view and reply to their support requests.
Findings map to 7 framework families: CIS Microsoft 365 Benchmark, CISA SCuBA, SOC 2, ISO 27001, HIPAA, NIS2, GDPR. These are mapping targets, not certifications TenantVigil holds.
Start here
Start with the MSP setup guide, then connect a customer tenant. The other articles follow the work: staff access, daily scans and incidents, planned changes, drift, reports and integrations.
The sentence at the top of each article states the current default for approved fixes. Native changes also need their Microsoft permissions and registered callbacks before use.
- Start your MSP account
- Connect a customer tenant
- Assign staff to customers
- Plan a change and read its receipt