Security and Privacy
At a glance
- Read-only: the Tenant Cockpit has read permissions only in your tenant. It cannot change, delete or create anything.
- Metadata only: names, owners, member counts, expiry dates, licences, last activity. No files, no emails, no chat content.
- Data in Europe: database and application run in European data centres.
- Deleted immediately: “Disconnect” immediately deletes all stored data of your tenant.
- No credentials with us: you give us neither passwords nor a client secret. Sign-in runs via Microsoft Entra ID.
Frequently asked questions
Which permissions does the Tenant Cockpit need?
The Tenant Cockpit is registered as a multi-tenant application. All Microsoft Graph permissions are read-only application permissions and form a fixed package: your Entra administrator grants them once via consent and can revoke them at any time under “Enterprise applications”. Individual permissions cannot be selected or deselected. Whether an area delivers data then depends exclusively on your Microsoft licences (column “Requirement”).
| Permission | Used for | Requirement |
|---|---|---|
Group.Read.All | Teams and Microsoft 365 groups, owners and member counts | – |
Sites.Read.All | SharePoint sites (age, size, owners), no file content | – |
User.Read.All | Guest accounts and licensed users | – |
AuditLog.Read.All | Last sign-in of guests and use of enterprise apps, sign-in security | Entra ID P1/P2 |
Reports.Read.All | Activity reports for groups, teams, sites, mailboxes and OneDrive | – |
Application.Read.All | App registrations and enterprise apps: owners, expiry dates of secrets and certificates | – |
Organization.Read.All | Tenant display name, purchased licences, verified domains | – |
ServiceHealth.Read.All, ServiceMessage.Read.All | Service health and Message Center | – |
Policy.Read.All | Read conditional access policies (MFA, blocking legacy sign-ins) | – |
RoleManagement.Read.Directory | Administrator roles, Global Administrators, PIM assignments | PIM: Entra ID P2 |
SharePointTenantSettings.Read.All | Tenant setting for external sharing | – |
IdentityRiskyUser.Read.All | Risky users | Entra ID P2 |
DeviceManagementManagedDevices.Read.All | Device inventory and compliance | Microsoft Intune |
Device.Read.All | Fallback: devices registered in Entra ID if Intune is missing | – |
SecurityEvents.Read.All | Secure Score and recommendations | – |
SecurityAlert.Read.All | Open alerts from Microsoft Defender | Microsoft Defender |
MailboxSettings.Read | Inbox rules, to find forwarding to external addresses. Never mail content. | – |
CrossTenantInformation.ReadBasic.All | Publisher tenant name for enterprise apps | – |
AuditLogsQuery.Read.All | “Last launch” of Power Apps from the Purview audit log (180 days) | Auditing enabled in Purview |
Power Platform, Power BI and Azure (without Graph permission)
| Area | What your administrator sets up |
|---|---|
| Power Apps, flows, agents, DLP | The app is registered once as a Power Platform management application (New-PowerAppManagementApp, read-only). This requires a Power Platform or Global Administrator. |
| Power BI | In the Fabric admin portal under tenant settings, enable “Service principals can use read-only admin APIs” for a security group that contains the Tenant Cockpit. No Entra permission with admin consent is granted for Power BI. |
| Azure Health | Azure role “Reader” for the Tenant Cockpit on the tenant root management group. |
The Tenant Cockpit checks domains (SPF, DKIM, DMARC) via public DNS queries and needs no permission for this.
The Tenant Cockpit needs no write, mail or file permissions in your tenant and changes nothing. Optionally you can set up your own sender: the Tenant Cockpit then receives the “Send mail” right only for a single shared mailbox of your choice (Exchange RBAC for applications), not for other mailboxes and without read access to mail. No additional Entra permission is needed for this. Guide
Which data is stored?
- Per object: type, display name, status with reason, owners (sign-in name), creation and activity date, member and guest counts, expiry date of secrets.
- Per licence: name, number purchased and assigned; for changes, user, licence and time.
- Service health and Message Center posts.
- Sign-in security: number of members with registered MFA and the sign-in names (UPN) of administrators without MFA.
- Questions to owners: object name, owner's email address, requester, time and the answer (“still needed” or “no longer needed”).
- Your settings in the Tenant Cockpit: report recipients, deferrals with justification, filters, language of emails.
Not stored: content of files, emails or chats, passwords, and access tokens of your users on our servers. The token of the optional Remediation add-on stays in the signed-in person's browser, is valid only for that area and is removed on sign-out.
Where is the data, and who processes it?
| Service provider | Task | Location |
|---|---|---|
| Microsoft Azure | Website, API, nightly scans | Europe (EU) |
| Supabase (on AWS) | Database | Europe (Zurich, Switzerland; adequacy decision of the European Commission) |
| Microsoft Exchange Online | Sending reports and notifications by email | Europe (EU) |
No processing takes place outside Europe. Data of different customers is logically separated: every query is bound to the tenant ID of your verified Microsoft token.
What happens when I disconnect?
Under “Administration”, your administrator disconnects with one click. This immediately deletes all stored objects, history, licence data, posts, deferrals, settings, administrators, page groups, company logo as well as all recipient addresses of your tenant. Only the tenant ID and tenant name with the status “disconnected”, the contract data (licence or Marketplace subscription with the licensee's user name) and the note that the 30-day trial was used remain. You can additionally revoke the permissions in Entra.
How is software quality ensured?
Changes are tested automatically, and the code is continuously checked for security patterns and outdated dependencies. Please report vulnerabilities via security.txt.
How do sign-in and access work?
- Sign-in exclusively via Microsoft Entra ID, including your multi-factor and conditional access policies.
- You control access to individual pages via Entra groups (“Administration”). Guest accounts are never allowed.
- The connection is always encrypted (HTTPS). Database access takes place only on the server side.
Contract, support and contact
- The Data Processing Agreement (DPA) with technical measures and sub-processors is available here; on request we send it signed.
- Support by email and phone, Monday to Friday 09:00 to 16:00 (CET/CEST); your contact is the operator in person. Binding response times are not promised.
- Availability: non-binding operational target of 90 % on an annual average, no public status page. There is currently no fixed deputy arrangement if the single operator is unavailable.
- Incidents: report security and data protection incidents to support@tenant-cockpit.com; we inform affected customers without undue delay, usually within 48 hours of becoming aware (Art. 33 GDPR, see DPA). See also Terms of Use §7.
- Provider: vivaXite e.U., Winkelberggasse 240, 2392 Grub im Wienerwald, Austria.
