Skip to main content

Managing AIPSO

Once your Platform & Security Officer has been set up, day-to-day management happens in the Platform & Security Officer section of the admin console, not the setup wizard. This article covers the Overview and Settings pages.

Overview Page​

Navigate to Governance > AIPSO in the admin nav to reach /governance/aipso. The Overview page shows:

  • Status - active, paused, terminated, or configured
  • Autonomy Dial - the current autonomy level and a short description of what it permits (read-only here; change it from Settings)
  • Next Review - the next scheduled wake-up time, and when AIPSO last ran
  • Managers - the active IT admin managers, with the primary manager flagged. Select Manage to open the Managers section of Settings.

If your tenant has the AIPSO entitlement but hasn't run the setup wizard yet, this page shows a Set up AIPSO prompt instead.

Actions​

Managers (users with the aipso:manage permission) see an Actions panel with:

  • Pause / Resume - pausing stops AIPSO from waking up on its schedule until you resume it; in-flight work is not interrupted. A confirmation dialog explains this before pausing.
  • Run Review Now - triggers an immediate review run outside the normal schedule.

This panel is hidden once AIPSO is terminated.

Review & refresh​

While AIPSO is active or paused, a manager who holds aipso:manage and is one of AIPSO's active managers also sees a Review & refresh card. It walks you through the goals, projects, and open findings AIPSO is working on now so you can keep, adjust, or close each one, then lets you tell AIPSO what has changed in your environment. Nothing changes until you confirm at the end.

Settings Page​

From the Overview page, select Settings (or navigate to /governance/aipso/settings) to reach AIPSO's settings. Settings is organized into sections, listed in a menu: Properties, Managers, Autonomy, Tools, Spending limits, Model, Mailbox, Schedule, Focus budget, Data access, Learning, and Danger zone. Opening Settings without a section, or following an older settings link, takes you to the first section you have permission to see.

Pause / Resume and Refresh sit in a command bar at the top of the page. Pausing or resuming here takes effect immediately, with no confirmation step; the Overview page's Pause still asks you to confirm first.

Properties​

AIPSO's display name and status, plus advanced execution-tuning fields that most tenants never need to change.

Managers​

The Managers section lists all active managers and lets you:

  • Add a manager - select any eligible platform-admin from the dropdown and click Add manager
  • Set primary - promote a non-primary manager to primary
  • Remove a manager - remove an active manager (audit-logged)

Adding, removing, and setting a primary manager each requires confirmation and saves immediately. The primary manager is the default contact for AIPSO alerts; held actions go to all active managers.

Each manager's row also has a Risk brief switch for their own scheduled risk brief. Changing your own switch only needs aipso:view; changing another manager's switch needs aipso:manage.

AIPSO must always have at least one active manager. The Remove control is disabled when only one manager remains, and the server enforces the same rule even if bypassed on the client.

Autonomy​

Select one of the five autonomy levels:

LevelBehavior
Investigate OnlyAIPSO can look into issues and report findings, but has no ability to make changes
Approve Every ChangeEvery change, regardless of risk, waits for a manager to approve it
Auto-Approve Low RiskLow-risk changes execute automatically; medium and high-risk changes wait for approval
Auto-Approve Low & Medium RiskOnly high-risk changes wait for manager approval
Full AutonomyAIPSO acts independently across all risk levels

Changing the dial shows a confirmation dialog stating exactly what the new level permits before it is saved. Every change is audit-logged.

Tools​

The Tools section manages the catalog tools AIPSO has been granted (for example, web search, HTTP, or SQL tools). Use it to grant or revoke tools from your general tool catalog at any time. AIPSO's built-in capabilities are always available and are not listed here.

Spending limits​

The most AIPSO may spend on AI usage in a day and in a month.

Model​

The work type and model AIPSO uses. Choose a model override if AIPSO should use a specific model instead of its work type's default.

Mailbox​

The Mailbox section manages AIPSO's own email inbox, the shared mailbox your managers use to reach AIPSO by email (see the Overview). It shows the currently bound mailbox and its email subscription health, and lets you:

  • Assign or change the mailbox - pick an existing monitored mailbox, or link/create one through the shared mailbox modal. If the mailbox is already assigned to another active agent, you must confirm the reassignment first.
  • Unassign the mailbox - AIPSO stops receiving email until you assign a mailbox again.

Managers can email AIPSO's mailbox once one is bound; mail from anyone who is not a manager is ignored. AIPSO reads inbound email today but does not yet reply conversationally.

Once a mailbox is assigned, the section also shows the health of its email subscription: Active, Expired, Disabled, or No subscription. If the subscription has expired or been disabled, AIPSO stops receiving new mail for that mailbox until it is renewed. Select Renew to re-create the subscription without unassigning and reassigning the mailbox; renewing requires aipso:manage.

Sender restrictions for the mailbox need the agents:read permission to view; without it, users who hold aipso:manage still see the mailbox binding and subscription status, but not sender restrictions.

Schedule​

The Schedule section holds AIPSO's schedule and alert-channel options, which setup fills with standard defaults, plus its workload limits:

  • Timezone - authoritative for all schedule and quiet-hours calculations
  • Working hours and days - when AIPSO's activity is considered "business hours"
  • Wake-up frequency - how many times per working day AIPSO wakes up to check the platform (1 to 4 times per day)
  • Digest cadence - how often a summary digest is sent (daily, weekly, or never)
  • Alert channels - Email (always on), plus optional Teams and/or Slack
  • After-hours policy - page managers only for critical findings, page for all findings, or queue everything until working hours resume
  • Quiet hours - optionally suppress non-critical alerts during a set window

Below the schedule fields, the Workload card and the Ambition grant card control how much open work AIPSO may hold at once.

This section requires aipso:view and the AIPSO entitlement to view, and aipso:manage to change; with aipso:view only, it is read-only. Changing any field and clicking Save saves only the fields you changed. If AIPSO's configuration is not live yet, the section shows a notice and its schedule fields stay read-only.

Focus budget​

How many outcome commitments AIPSO advances per scheduled run.

Data access​

The primary manager's Microsoft 365 data AIPSO may read, and who AIPSO may email.

Learning​

Whether AIPSO runs the weekly retrospective.

Danger zone​

Danger zone holds Terminate, which permanently stops AIPSO. This cannot be undone from the console and requires confirmation. Danger zone, including seeing that it exists, requires aipso:manage. After AIPSO is terminated, Settings shows AIPSO is not set up yet until you run the setup wizard again, so its Tools, Mailbox and other sections can no longer be viewed or changed.

Permissions​

  • aipso:view - lets a user see the Overview page and most Settings sections in read-only mode.
  • aipso:manage - required to change the autonomy dial, manage the manager roster (other than your own risk brief switch), use lifecycle actions, and open Danger zone at all.
  • Properties, Model, Tools, Spending limits, Learning, and Focus budget also require the agents:read permission to view, and are hidden from the Settings menu without it. Mailbox stays visible without agents:read for any manager, but its sender restrictions still need it.