PCC Learning Center · AI Governance
Review What Connected Applications Can Access Before You Approve Them
A third-party application can gain ongoing access to Microsoft 365 data through OAuth consent. Review the business purpose, publisher, permissions, users, identities and removal plan before access becomes permanent.
The Core Rule
Do not approve an application because the sign-in screen looks familiar or the vendor is well known. Approve the minimum permissions required for a defined use, assign an owner and record how access will be reviewed and removed.
Why OAuth App Review Belongs in AI Governance
AI tools increasingly connect to mail, calendars, files, meetings, customer systems and other applications. The connection—not only the model—often determines what information the tool can reach and what actions it can take.
Delegated Access
The application acts with a signed-in user and may inherit that person’s existing reach. Broad employee access can become broad application access.
Application Access
The application can act without a signed-in user. These permissions deserve strong justification, a technical owner and careful monitoring.
Tenant-Wide Consent
Administrator approval can grant permissions across the organization. Record why organization-wide access is necessary rather than treating admin consent as a routine click.
Eight Questions Before Approval
What Business Use Is Approved?
Name the workflow, users and expected benefit. “Productivity” is too broad to justify access.
Who Owns the Decision?
Assign a business owner and a technical owner. A vendor or department name is not an accountable owner.
Who Published the Application?
Verify the publisher, exact application identity and expected sign-in flow. Similar names and logos do not establish trust.
Which Permissions Are Requested?
Review each delegated and application permission in plain English. Ask what data and actions each scope enables.
Is the Scope Necessary?
Reject convenience permissions. Prefer narrower, read-only and user-scoped access when it supports the use case.
What Data and Systems Are Reachable?
Consider mailboxes, files, sites, calendars, chats, users, groups and connected downstream services.
How Will Activity Be Observed?
Identify available sign-in, consent, audit and vendor logs. Decide what unusual behavior should be investigated.
How Will Access End?
Record the review date, removal owner, token-revocation steps and business alternative if the integration is disabled.
Decision Outcomes
| Decision | Use when | Required record |
|---|---|---|
| Approve | The use, publisher, permissions, ownership and controls are acceptable. | Owners, scopes, users, decision date and next review. |
| Approve with conditions | Access is acceptable only with restrictions such as a pilot group, narrower scope or stronger monitoring. | Conditions, enforcement owner and completion date. |
| Pilot only | Evidence is incomplete but exposure can be bounded in a test environment or limited group. | Pilot boundary, test criteria, end date and rollback plan. |
| Do not approve | The permissions are excessive, ownership is unclear or risk cannot be bounded. | Reason, blocked use and safer alternative when available. |
| Retire | The application is unused, duplicated, unsupported or no longer justified. | Removal owner, revocation date and replacement workflow. |
Review the Lifecycle, Not Just Installation
- Review the application inventory at least quarterly.
- Reassess when permissions or consent scope change.
- Reassess when the vendor adds an agent, connector or action capability.
- Remove access when the owner leaves or the business use ends.
- Investigate applications with no current owner or recent activity.
- Revoke grants and refresh tokens when an application is retired or compromised.
- Preserve approval and review records.
- Connect suspicious app activity to the existing incident-response process.
Admin Consent Is a Security Decision
Tenant-wide consent can authorize access across the organization. Use a defined request and review workflow instead of approving applications directly from an unexpected prompt.
Record the Review in the AI Tool Inventory
Capture the application type, permission model, consent scope, granted permissions, service or agent identity, owners, approval status, last permission review and next review date.
Make Connected-App Access Visible and Reviewable
PCC helps Bay Area businesses strengthen Microsoft 365 identity, permissions, application access and security foundations for responsible AI use.