Admin access, handled like it matters.

TenantWard works inside your Microsoft 365 or Google Workspace. This page lists every permission it asks for and why, how changes are kept safe, and what happens to your data.

In plain words

The short version, one line per kind of access, with what TenantWard never does whatever access it has: what TenantWard can and can’t do with your access. Whether everything is running right now: status.

If TenantWard itself were broken into

Any tool with admin access can be a way in. Here is what someone who broke into TenantWard could reach, how we make that hard, how you cut TenantWard off in a minute, and when you would hear from us. How we handle billing, cancelling and your clients is on how we do business.

The undo guarantee

Every change TenantWard makes is backed up before it runs, checked afterwards, and recorded with who asked, who approved and what changed. Where Microsoft or Google allows it, the change can be undone from History with one click for as long as the change shows its undo; where it can’t be undone, the plan says so before you approve it.

If someone changes a setting outside TenantWard afterwards, it notices, tells you who changed it, and asks whether to put it back. You can see a full change record, with its backup and undo, in a sample company before connecting anything.

Connecting Microsoft 365: one approval

A Global Administrator approves TenantWard once, on Microsoft’s own consent screen, which lists every permission before you approve. You choose how to start:

  • Read-only. A separate TenantWard app with only the read permissions below, plus Microsoft’s Global Reader role. It runs the full checkup and can’t change anything. You can grant change access later, when you first want a fix.
  • Read and change. The TenantWard app with the read permissions below and the write permissions its catalog changes need, plus the Exchange Administrator and User Administrator roles, assigned in one more sign-in. Fixes and autopilot work straight away.

TenantWard keeps this access until you remove it, so it can work while nobody is signed in. Each connection’s page under Connections shows the permissions Microsoft actually granted, and you can remove TenantWard from Connections or from Entra › Enterprise applications at any time.

Read-only connection, application permissions (plus the Global Reader role):

PermissionTypeWhat it's for
Directory.Read.AllApplicationRead who's in the company, their groups, licenses and admin roles
User.Read.AllApplicationRead who's in the company, their groups, licenses and admin roles
Group.Read.AllApplicationRead who's in the company, their groups, licenses and admin roles
RoleManagement.Read.DirectoryApplicationRead who's in the company, their groups, licenses and admin roles
Organization.Read.AllApplicationRead who's in the company, their groups, licenses and admin roles
Domain.Read.AllApplicationRead who's in the company, their groups, licenses and admin roles
Policy.Read.AllApplicationRead sign-in rules, MFA settings and which sign-in methods each person has registered
UserAuthenticationMethod.Read.AllApplicationRead sign-in rules, MFA settings and which sign-in methods each person has registered
AuditLog.Read.AllApplicationRead sign-in and audit logs, risky sign-ins and Microsoft's security alerts
Reports.Read.AllApplicationRead sign-in and audit logs, risky sign-ins and Microsoft's security alerts
SecurityEvents.Read.AllApplicationRead sign-in and audit logs, risky sign-ins and Microsoft's security alerts
SecurityAlert.Read.AllApplicationRead sign-in and audit logs, risky sign-ins and Microsoft's security alerts
IdentityRiskyUser.Read.AllApplicationRead sign-in and audit logs, risky sign-ins and Microsoft's security alerts
IdentityRiskEvent.Read.AllApplicationRead sign-in and audit logs, risky sign-ins and Microsoft's security alerts
ActivityFeed.ReadApplicationRead sign-in and audit logs, risky sign-ins and Microsoft's security alerts
ServiceHealth.Read.AllApplicationRead Microsoft's service health: which of Outlook, Teams, SharePoint and OneDrive Microsoft is fixing right now
Application.Read.AllApplicationRead which outside apps have access, and to what
SharePointTenantSettings.Read.AllApplicationRead file-sharing settings, devices, device policies and backup settings
DeviceManagementManagedDevices.Read.AllApplicationRead file-sharing settings, devices, device policies and backup settings
DeviceManagementConfiguration.Read.AllApplicationRead file-sharing settings, devices, device policies and backup settings
BackupRestore-Configuration.Read.AllApplicationRead file-sharing settings, devices, device policies and backup settings
MailboxSettings.ReadApplicationRead mailbox settings like forwarding and automatic replies (never the mail itself)
Exchange.ManageAsAppApplicationRead mailbox settings like forwarding and automatic replies (never the mail itself)

Google Workspace: a service account your super admin allows

Google Workspace is connected in two steps. First a super admin signs in with Google once; Google lists these read-only permissions before they approve, the browser hands the one-hour token to our server for that first checkup, and it is never stored:

PermissionWhy
admin.directory.user.readonlyUsers, admins, 2-Step Verification status and last sign-in, so checks can name who's exposed.
admin.directory.domain.readonlyYour domains, so each one gets its email and domain checks.
admin.directory.customer.readonlyYour organization's name and primary domain.
admin.reports.audit.readonlyThe last 30 days of sign-in alerts and third-party app approvals. Never message or file contents.
cloud-identity.policies.readonlySecurity settings: whether 2-Step Verification is required, Drive sharing, Gmail forwarding.
admin.directory.device.mobile.readonlyPhones and tablets with company data: screen lock, encryption, rooted or jailbroken, last sync.

Then, so checks can run daily and monitoring every 15 minutes without anyone signed in, the super admin adds TenantWard’s service account in the Admin console (Security › API controls › Domain-wide delegation), pasting a client id and this exact list of scopes. The service account’s key never leaves our database: a server function signs each one-hour token, held only in memory for one job. TenantWard reads settings, file names and who files are shared with, never what is in anyone’s mail, files or calendar, and changes only what someone here approves, with a backup and undo. Deleting the TenantWard entry on that same page removes the access at once.

PermissionWhy
admin.directory.userEveryone's account, 2-Step Verification and last sign-in; suspend, restore, reset a password, create an account, remove super admin.
admin.directory.user.securitySign someone out everywhere, remove an outside app's access, remove app passwords and backup codes.
admin.directory.groupGroups and who is in them; add or remove people when onboarding or offboarding.
admin.directory.domain.readonlyYour domains, so each one gets its email and domain checks.
admin.directory.customer.readonlyYour organization's name and primary domain.
admin.directory.orgunit.readonlyOrganizational units, to tell which settings apply to whom.
admin.directory.device.mobilePhones and tablets with company data: screen lock, encryption, last sync; wipe company data from a lost one.
admin.directory.device.mobile.actionApprove, block or wipe company data on a phone, when someone here asks.
admin.reports.audit.readonlySign-in alerts, admin changes, third-party app approvals and Drive sharing events. Never message or file contents.
admin.reports.usage.readonlyWhich accounts and licenses are in use, so unused ones can be found.
apps.alertsGoogle's own security alerts for your organization. Google has no read-only version of this permission; TenantWard only reads them.
apps.licensingWhich licenses each person holds; remove a leaver's license when someone here approves it.
admin.datatransferHand a leaver's Drive files to whoever takes over.
apps.groups.settingsGroup settings: who may post, whether outsiders can email the group; close groups outsiders can email or join.
cloud-identity.policies.readonlySecurity settings: whether 2-Step Verification is required, Drive sharing, Gmail forwarding.
gmail.settings.basicEach person's Gmail forwarding, filters and out-of-office, read to spot forwarding outside the company; changed only through a change with undo.
gmail.settings.sharingEach person's Gmail delegates and forwarding addresses, for the same checks; remove a delegate or forwarding address.
driveGoogle's broadest Drive permission, needed to remove sharing links. TenantWard reads only file names and who they're shared with, never contents, to find Anyone-with-the-link sharing and take it back.
calendar.aclsWho each calendar is shared with outside the company; close public sharing.

What read and change adds

These permissions are part of the same approval when you choose read and change. They let TenantWard run changes from its catalog; nothing else uses them. Exchange commands are limited to a fixed list of commands and parameters.

Read and change also reads a little more than the read-only connection:

PermissionTypeWhat it's for
Vulnerability.Read.AllApplicationRead which computers run software with known weaknesses, and what software is installed, when you have Microsoft Defender
Machine.Read.AllApplicationRead which computers run software with known weaknesses, and what software is installed, when you have Microsoft Defender
Software.Read.AllApplicationRead which computers run software with known weaknesses, and what software is installed, when you have Microsoft Defender
ServiceHealth.Read.AllApplicationRead Microsoft's service health: which of Outlook, Teams, SharePoint and OneDrive Microsoft is fixing right now
DeviceManagementServiceConfig.Read.AllApplicationRead Intune's enrollment settings, such as the Apple certificate that lets iPhones and Macs be managed

The changes:

PermissionTypeWhat it's for
Policy.ReadWrite.ConditionalAccessApplicationChange sign-in rules: require MFA, block old sign-in methods, turn on security defaults
Policy.ReadWrite.AuthorizationApplicationChange sign-in rules: require MFA, block old sign-in methods, turn on security defaults
Policy.ReadWrite.AuthenticationMethodApplicationChange sign-in rules: require MFA, block old sign-in methods, turn on security defaults
Policy.ReadWrite.PermissionGrantApplicationStop people approving outside apps by themselves, and take access away from an app
DelegatedPermissionGrant.ReadWrite.AllApplicationStop people approving outside apps by themselves, and take access away from an app
AppRoleAssignment.ReadWrite.AllApplicationStop people approving outside apps by themselves, and take access away from an app
User.ReadWrite.AllApplicationAdd people, change their details, licenses and groups, reset a password or MFA
User-PasswordProfile.ReadWrite.AllApplicationAdd people, change their details, licenses and groups, reset a password or MFA
UserAuthenticationMethod.ReadWrite.AllApplicationAdd people, change their details, licenses and groups, reset a password or MFA
GroupMember.ReadWrite.AllApplicationAdd people, change their details, licenses and groups, reset a password or MFA
SharePointTenantSettings.ReadWrite.AllApplicationChange file-sharing limits
Exchange.ManageAsAppApplicationChange mailboxes: forwarding, automatic replies, shared mailboxes, email addresses, the company signature
AppCatalog.Read.AllApplicationPost alerts and the help desk in Microsoft Teams
TeamsAppInstallation.ReadWriteSelfForUser.AllApplicationPost alerts and the help desk in Microsoft Teams
TeamsAppInstallation.ReadWriteSelfForTeam.AllApplicationPost alerts and the help desk in Microsoft Teams
Team.ReadBasic.AllApplicationPost alerts and the help desk in Microsoft Teams
Channel.ReadBasic.AllApplicationPost alerts and the help desk in Microsoft Teams
TeamsActivity.SendApplicationPost alerts and the help desk in Microsoft Teams
BackupRestore-Configuration.ReadWrite.AllApplicationTurn on Microsoft 365 Backup and run a restore test into a new folder (only when you add these permissions)
BackupRestore-Control.ReadWrite.AllApplicationTurn on Microsoft 365 Backup and run a restore test into a new folder (only when you add these permissions)
BackupRestore-Restore.ReadWrite.AllApplicationTurn on Microsoft 365 Backup and run a restore test into a new folder (only when you add these permissions)
DeviceManagementApps.ReadWrite.AllApplicationSet up phone app protection in Intune (only when you add this permission)
DeviceManagementScripts.ReadWrite.AllApplicationSend app updates to computers as an Intune script (only when you add this permission)
DeviceManagementConfiguration.ReadWrite.AllApplicationAdd Intune device settings: the Windows update ring and the compliance policies
WindowsUpdates.ReadWrite.AllApplicationPush an urgent Windows security update to the computers missing it (only when you add this permission)
Sites.ReadWrite.AllApplicationRemove a file's link that works for anyone (only when you add this permission; TenantWard doesn't open the files)
Group.ReadWrite.AllApplicationCreate the group those policies apply to, and Microsoft 365 groups you ask for
RoleManagement.ReadWrite.DirectoryApplicationTake an admin role away from a person, app or partner, and give it back on undo (only when you add this permission)
Application.ReadWrite.AllApplicationSwitch off an outside app named in a vendor alert, without deleting it, and switch it back on with undo (only when you add this permission)

Microsoft only lets an app do some of this when it also holds an admin role, so the connection includes:

PermissionWhy
Exchange Administrator (directory role)Microsoft requires it for any app that runs Exchange Online commands.
User Administrator (directory role)Microsoft requires it for an app that resets passwords or MFA. Accounts that hold admin roles are out of its reach; changes to them need a Global Administrator.
Privileged Authentication Administrator (directory role, response app, off unless you turn it on)Only when a Global Administrator turns on admin lockdown. Microsoft requires it for an app to block, sign out or reset the password of an admin account. TenantWard uses it only when someone locks an account during an incident, never automatically, never on the person asking and never on the last Global Administrator who can sign in. Turning admin lockdown off takes the role away.

And, during setup only, two permissions used once while you’re signed in:

PermissionTypeWhat it's for
RoleManagement.ReadWrite.DirectoryDelegatedUsed once, while you're signed in, to give TenantWard's app the Exchange Administrator and User Administrator roles, and, only if you turn on admin lockdown, the response app the Privileged Authentication Administrator role (or to take it away again)
AppCatalog.ReadWrite.AllDelegatedUsed once, while you're signed in, to add the help desk app to your Teams

How changes run

Changes run on TenantWard’s server, never with your password: with TenantWard’s own app credentials, or for partner-connected customers with the partner sign-in described below. A change runs when someone on your team approves it, or when your change policy or autopilot settings allow it without asking, for example putting back a setting that was changed outside TenantWard. Anything those settings route to approval waits for it. Every call TenantWard makes to your Microsoft 365 is logged.

IT providers can connect customers through a Microsoft partner sign-in (GDAP). That sign-in’s refresh token is kept encrypted in the database’s vault and used only to approve and reach the customers you pick. For customers connected this way, checks, changes and incident response run through that partner sign-in, limited to the GDAP roles the customer granted you, and need no separate app approval in the customer.

Monitoring every 15 minutes

With monitoring on, our server checks every 15 minutes, day and night, using the TenantWard app you approved, and stores only what it needs to tell new from old: the alerts it raises, the ids of inbox rules, leaked-password and device-code detections and audit records it has already seen, which sign-in methods each person uses, the places each person normally signs in from, and a daily copy of your security settings so changes can be spotted. These are automatic checks; no people watch your account around the clock, and alerts go to the people you choose.

Automatic incident response is opt-in and narrow

If you choose to let TenantWard contain a hijacked account automatically, or to remove a reported phishing email from every mailbox, a Global Administrator approves a separate app with only these permissions. It can’t reset passwords. You choose the triggers and actions, name people it must never lock, and set a limit on how many accounts it can lock in an hour. Global Administrators are never blocked automatically. A blocked sign-in can be restored in one click and a switched-off inbox rule turned back on; ended sessions can’t be brought back, people simply sign in again. Inbox rules are switched off with this app's mailbox-settings permission; without response access, the alert tells you to switch the rule off yourself.

PermissionTypeWhat it's for
User.EnableDisableAccount.AllApplicationBlock a hijacked account and sign it out everywhere
User.RevokeSessions.AllApplicationBlock a hijacked account and sign it out everywhere
User.Read.AllApplicationBlock a hijacked account and sign it out everywhere
MailboxSettings.ReadWriteApplicationSwitch off the inbox rule an attacker set up (turned off, never deleted)
DelegatedPermissionGrant.ReadWrite.AllApplicationTake an app's access away from one person when they say they didn't approve it
Mail.ReadWriteApplicationDuring a removal you approve, find a reported phishing email in each inbox and move it out (it can be put back). Nothing else reads mail
User-PasswordProfile.ReadWrite.AllApplicationWhen you lock an account in an incident, replace its password so a stolen one stops working (only after response access is approved again)
Device.ReadWrite.AllApplicationSwitch off a device an attacker registered to an account, without deleting it, and switch it back on with undo (only after response access is approved again)

Mail

Only two things in TenantWard ever touch a message. The response app can find a reported phishing email in each inbox and move it out, during a removal you approve; it can be put back. The reporting app reads the one mailbox your staff forward suspicious email to, if you turn that on, and nothing else. No other part of TenantWard reads mail: the rest only reads mailbox settings such as forwarding and automatic replies.

PermissionTypeWhat it's for
Mail.ReadApplicationRead the reporting mailbox, and only that mailbox

What a security scanner will say about TenantWard

If you, your IT provider or your insurer runs a tool such as Purple Knight, Maester, ScubaGear or a Secure Score review, it will flag TenantWard’s change access for two permissions. Scanners flag any app that holds them, whoever made it, and TenantWard’s own monitoring flags other apps for the same thing. That’s right: these are powerful permissions, and the question is whether you trust the app that holds them. Here is what TenantWard does with each.

PermissionWhat the scanner saysWhat TenantWard does with itWithout it
RoleManagement.ReadWrite.DirectoryApplication with a risky API permission (can assign directory roles)Takes an admin role away from a person, app or partner when you approve that fix, and gives it back on undo.Optional. The fixes that remove an admin role (from an app, a partner or an unused admin) become steps you do yourself.
Application.ReadWrite.AllApplication with a risky API permission (can change apps)Switches off an outside app named in a vendor alert when you approve that fix, and switches it back on with undo. TenantWard never adds keys to any app or changes its own permissions with it.Optional. Switching off an app from a vendor alert becomes a step you do yourself in Entra.
AppRoleAssignment.ReadWrite.AllApplication with a risky API permission (can grant app permissions)Takes an outside app's access away when you approve that fix, and puts it back on undo. TenantWard never grants itself or any app new access with it.Removing an outside app's access becomes a step you do yourself in Entra.

The read-only connection holds neither, so a company that hasn’t given change access won’t see TenantWard in this part of the report.

To take one permission away without removing TenantWard: In the Microsoft Entra admin center, open Enterprise applications, choose TenantWard, then Permissions. Find the permission, open its menu and choose Revoke permission. TenantWard keeps working without it; the fixes that need it show the steps to do them yourself. Connecting again or adding a permission later asks for it again, so check the list on Microsoft's consent screen.

More on what to expect and what to send the person running the scan: if your IT provider or insurer runs a security scan.

Where AI is used, and where it isn't

AI help is off for every company until an owner or admin turns it on for that company and signs for it. IT providers choose client by client, and each choice is kept with who made it and when. Checks, fixes, put-backs and reports don’t use AI and work the same with it off.

On Comply and Partner an account can use its own Anthropic key. What AI help sends then goes to Anthropic under that account’s own agreement with them. The key is kept encrypted, only its last four characters are ever shown, and if it stops working AI help pauses; TenantWard’s key is never used in its place.

Once it’s on, TenantWard can explain an issue or answer a question in plain English. To explain an issue it sends that issue and what the check found to Anthropic’s Claude; to answer a question it also sends the company’s open issues and its people list (name, email address, admin roles, MFA status, license and last sign-in, for up to 250 people). Anthropic doesn’t train on this data. Answers stay in your account with your rating.

When you ask it to do something, it can suggest a change from TenantWard’s catalog. The suggestion is checked against your company’s data (a person must be one you named), and it only opens the change’s plan for you to review and approve. It also reads an insurer’s form you upload, only to label which questions it asks, and gives a second opinion on a reported email, which can raise the warning level but never clear an email on its own. Text inside your data, a form or an email is treated as data, never as instructions.

Shared explanations of each check are written without any company’s data and improve as people rate them. The built-in assistant explains and suggests; it never runs a change. Whoever turned AI help on can switch it off again in Settings, and from then on nothing about that company is sent.

AI agents you connect

You can connect your own AI agent, such as Claude, through a sign-in on the Agents page in Settings. Agents can propose changes; they run only through the tested catalog, routine ones within the limits you set, and everything else after a person approves with two-factor sign-in.

  • Only an owner or admin can connect an agent, for the clients they name, and any owner or admin can revoke it.
  • Agents can use only part of the catalog. Nothing outside the catalog can run.
  • An agent runs a change without asking only up to the lower of its own limit and the limit in your change policy. The default is routine changes; anything above routine needs Protect or above.
  • Each change records which agent asked, and an agent can undo only changes it made.

How changes stay safe

  • Every change is a fixed, tested script from TenantWard’s catalog. Nothing outside the catalog can run.
  • Each change is graded routine, careful, disruptive or restricted, and shows what will change, who’s affected, what might stop working and how to undo it.
  • The current settings are backed up before every change. If the backup fails, nothing runs.
  • After a change, TenantWard reads the setting again to confirm it took effect.
  • New sign-in policies are created in report-only mode first. Disruptive changes need you to confirm you’ve read the rollback plan. Restricted changes, such as deleting accounts, are never one-click.
  • Every change is recorded with who or what asked for it, who approved it and when. Every catalog change has a tested undo, or says before it runs why it can’t be undone (a released email can’t go back into quarantine, for example).
  • The built-in assistant explains and suggests for a person to review; it never runs a change. AI agents you connect run only catalog changes, routine ones within the limit in your change policy, everything else after a person approves with two-factor sign-in.
  • Requests from the employee help desk, your HR system or reported email never change anything by themselves. Someone on your team reviews and approves each one, and requests from anyone who couldn’t confirm their work email are marked unverified.

Your data

  • We store check results, issues and their history, the change history, settings backups and the people list from your last check. Only members of your account can read them, guaranteed by row-level security in the database.
  • We never read or store the contents of email, files, calendars or chats.
  • TenantWard reaches Microsoft 365 with its own app credentials (or, for partner-connected customers, through the partner’s delegated admin sign-in) and never asks for or stores your password. The one Microsoft token we keep is a partner sign-in’s refresh token, encrypted in the vault. Temporary passwords are shown once and never saved.
  • Data is encrypted in transit and at rest with our hosting providers (Vercel for the app, Supabase for the database).
  • Remove a client, a connection or a domain any time. To close your account and erase everything, email hello@tenantward.com.

The standards our checks follow

TenantWard’s checks follow public standards, including the CIS Microsoft 365 benchmark and CISA’s secure configuration baselines, and each check says which control it maps to.

Reporting a security issue

If you think you’ve found a security issue in TenantWard, email hello@tenantward.com with what you found and how to reproduce it. We acknowledge every report within three business days and keep you updated until it’s fixed.

  • In scope: tenantward.com and its subdomains, the TenantWard app, its sign-in, and its API.
  • Test only with an account you own, don’t access or change other customers’ data, don’t degrade the service, and don’t use social engineering or physical attacks.
  • Give us a chance to fix it before telling anyone else: we ask for 90 days, or until the fix is out if that’s sooner.
  • If you act in good faith within these rules, we won’t take legal action against you for your research, and we’ll credit you if you’d like.

Our security.txt has the same contact. See also our privacy page.