Installed
The application object exists. That alone does not prove access or use.
OAUTH APPLICATION GOVERNANCE
Know what was approved, who owns it, and what still needs investigation.
OAuth application governance connects application identity, publisher, permissions, consent, owners, users, activity, credentials, risk, and history when Microsoft 365 exposes those fields. SCOUTz keeps installed, consented, assigned, and active states separate.
What is OAuth application governance?
It is the ongoing work of inventorying connected applications, understanding permission scope and consent, assigning accountable owners, reviewing evidence of use, monitoring credentials and publisher context, and removing or constraining access only after the environment and business need are validated.
APPLICATION GOVERNANCE
READ-ONLYConnected application review
PUBLISHERVerified publisher
OWNERNeeds review
CONSENTOrganization
ACTIVITYObserved recently
PermissionTypeState
User.ReadDelegatedExpected
Directory.Read.AllApplicationReview
offline_accessDelegatedObserved
Installed · consented · assigned · active remain separate states
KEEP THE STATES SEPARATE
Consented
A permission grant exists. Scope, consent type, and business owner still matter.
Assigned
A user or group relationship is present. Assignment does not always prove activity.
Active
A supported source exposes recent use. Absence of activity evidence can still be unknown.
SCOUTz OPEN BETA
Point SCOUTz at the question. Walk in with a defensible answer.
Bring a real MSP workflow and see how SCOUTz turns evidence into the next defensible action. The review runs without an agent or install and never changes configuration automatically.
SCOUTz prepares the conversation. The relationship and the sale stay yours.