Can Kagemori change anything in our Microsoft 365 tenant?
No. Kagemori only receives read-only permissions, listed in the Security section above. It cannot isolate devices, change settings, read mailboxes or files, or alter users. An optional, separate add-on can close alerts from inside Kagemori, but it is off by default, needs its own approval and asks for a two-factor code for every action.
Which Microsoft licences do our customers need?
Kagemori works with any Microsoft 365 business or enterprise plan and shows what each tenant's licences allow. Device and vulnerability data needs Microsoft Defender for Endpoint (included in Microsoft 365 Business Premium and E5). Incidents need Microsoft Defender XDR, and sign-in monitoring needs Entra ID P1. When a licence is missing, Kagemori says so plainly instead of showing an error.
Do we need to install anything on devices?
No. Kagemori reads from Microsoft's cloud APIs. If your devices are already onboarded to Microsoft Defender, there is nothing else to deploy.
How is this different from the Microsoft Defender portal?
Defender is where analysts investigate and respond, one tenant at a time. Kagemori sits above it: one ranked view across all your tenants, zero-day matching against CISA KEV, partner hierarchy and white-labelling, and management reports mapped to NIST CSF 2.0. Every item links straight back to Defender for response.
Can our partners resell Kagemori under their own brand?
Yes. Each partner can have its own logo, colours and product name. Their customers see the partner's brand in the console, in onboarding emails and on every report. Partners manage their own customers and users, and they cannot see anyone else's.
How do we stop using Kagemori?
Delete the customer in Kagemori and remove the Kagemori app under Enterprise applications in Microsoft Entra. Access ends immediately. On request we delete the customer's archived data.