Policies and auto-approval
Policies decide what happens to an integration or sharing request before a person sees it. Routine, low-risk requests are approved instantly; anything outside what IT allows is refused with the reason; everything else goes to an approver.
Order of evaluation
- Max scopes. If any requested scope is outside the integration's max scopes (Admin › Integrations), the request is refused, naming the scopes and the limit.
- "Require the requester's manager" rules. If one matches, the request goes to approvers and the requester's manager. These rules win over auto-approval.
- Auto-approve rules. If one matches, a grant is created at once (audited as
grant.auto). - Otherwise a request goes to the integration's approvers (plus the requester's manager when the request is to show file data to the app audience).
Built-in rules
| Rule | Effect | On by default |
|---|---|---|
| Graph read of the user's own files: auto | Auto-approve Microsoft 365 user:read, files:read, lists:read as the user | ✓ |
| Salesforce read for Sales: auto | Auto-approve read-only Salesforce for the Sales department | ✓ |
| Share within own department: auto | Auto-approve sharing an app within the owner's department (only matters when the manager rule below is on) | ✓ |
| Teams messages to people who can open the app: auto | Auto-approve Teams recipients who can all already open the app | ✓ |
| Mail from an app to its owner: auto | Auto-approve Microsoft 365 mail.send:owner as the project | ✓ |
| Sharing beyond the owner's department needs their manager | Widening app access past the owner's department waits for the manager |
Built-in rules can be edited or turned off, but not deleted.
Add or edit a rule
- Open Admin › Policies (Org Admins; Auditors read only).
- Select an existing rule, or add one under Auto-approve rules.
- Fill in the form:
| Field | Meaning |
|---|---|
| Name | Shown on requests and in the audit log |
| Effect | Auto-approve, or Require the requester's manager |
| Kind | Integration access, Show data to the app audience, or Sharing the app |
| Integration | One integration, or any |
| Runs as | The user, The project, or any |
| Access | Read (the request must be read-only), Write (must include a write), or any |
| Scopes (all must match; * wildcards) | Every requested scope must be covered, e.g. files:read, user:read |
| Requester departments | e.g. Sales, Finance |
| Requester groups | e.g. Support Leads (names or ids) |
| Audience | Within the owner's department, People who can open the app, or Only the project owner |
- Save. The console shows a plain-English summary of each rule, for example "salesforce · read-only · requester in Sales → auto-approve".
You can also edit the raw Match (JSON):
{
"integration": "salesforce",
"access": "read",
"departments": ["Sales"]
}
Integration settings that act as policy
For each integration in Admin › Integrations:
| Setting | Effect |
|---|---|
| Enabled | Turned off, every call answers INTEGRATION_DISABLED (existing grants are kept) |
| Max scopes | The hard ceiling; requests outside it are refused |
| Approvers | Who reviews requests (users or groups). With none, Org Admins decide. |
| Data sensitivity | Low, medium or high; shown on every request |
tip
Start strict: turn off auto-approve rules you're unsure about and watch the Requests inbox for a few weeks. Add rules for the requests you approve every time.
Availability
Guest policies, runtime limits and expiry defaults in Admin › Policies are in the design but not built yet. Project expiry is set on Admin › Roles; see Project lifecycle.
Was this page helpful?