Permission-aware agents: what an account change with a second approver teaches, and the records that prove it

Short answer

Permission-aware agents take an action only when the authority for it is in place, and stop or ask when it is not. In an ordinary business workflow, that is an account change that needs a second approver: the technician requests elevated access with a reason, cannot approve his own request, waits for a manager, and acts inside a one-hour window. For a referral, what matters is whether the company kept the request, the approval, the action and the outcome, and who can authorize a licensing discussion.

Visual briefFull-size diagram
A four-step path from a request with justification and ticket number, through a second-approver gate, to a one-hour role activation and the account change; a branch below the gate shows self-approval blocked, and a bar shows the audit trail kept 30 days unless archived.
Illustrative change at a fictional company. The 24-hour approval window and the 30-day audit default come from Microsoft's documentation; the rest is invented.

What does permission-aware agents mean in an ordinary business workflow?

It means authority is checked before the action, not after. The business version is familiar: some changes need a second person, and nobody is allowed to approve their own request.

The behavior matters for AI agents because an agent that can act in business software can also act without authority. Our explainer on why AI agents fail covers failures that come from doing the right thing in the wrong way. Records of real approval workflows show the shape of correct behavior: what was asked, who could say yes, what happened when the wrong person tried, and what was done once approval arrived.

Identity administration is a clear case because the rules are written into the software. In Microsoft Entra Privileged Identity Management (PIM), Microsoft's documentation says approvers can't approve their own role activation requests, delegated approvers have 24 hours to approve before the user must submit a new request, and a request is settled by the first approver who approves or denies. Role settings can require a justification and a ticket number at activation, and the activation maximum duration can be set from one to 24 hours.

One caution belongs here, not in a footnote. This page is about authority inside a task. It is not about the company's right to license its records, which is a different test covered in de-identification versus permission to license.

An account change that needs a second approver (Illustrative)

This case is fictional. A 420-person freight brokerage manages staff accounts in Microsoft Entra. Admin roles are eligible, not permanent: a technician activates one when needed, with approval required and a one-hour activation limit.

The finance director replaces her phone and can no longer complete multi-factor sign-in. Changing her sign-in methods needs an admin role the service desk technician holds only as eligible.

TimeStepAuthority checkRecord left
09:05Finance director's request logged after identity check by video callService desk policy requires a verified requesterTicket IT-5521 with the check noted
09:20Technician requests activation of the admin roleJustification and ticket number required by role settingsActivation request with reason and "IT-5521"
09:22Technician, who is also an approver for colleagues, tries to approve his own requestSelf-approval not allowedRequest stays pending
09:41IT manager approvesDifferent person, within the 24-hour windowApproval with approver identity and time
09:44Technician updates the director's sign-in methodsRole active, expires at 10:41Audit entry for the account change
09:58Director signs in on the new phone; ticket closedOutcome confirmed by the userSign-in success; ticket resolution note

Two details make this a useful example rather than a tidy story. First, PIM's own documentation says ticket information at activation is informational and is not checked against any ticketing system. "IT-5521" is a typed string, so linking the activation to the real ticket depends on people typing the right number. Second, the blocked self-approval at 09:22 is the most instructive row for anyone studying permission-aware behavior, and it is also the row most likely to leave no trace in a summary report.

Evidence fields that show authority, not just activity

An audit log can show that an account changed. It takes more fields to show that the change was authorized. For the 09:44 change above, these are the ones that carry the authority story.

FieldWhat it establishesIn the example (Illustrative)
Business request and verificationWhy the action was needed and that the requester was genuineTicket IT-5521 with the video-call check noted
Elevation request with justificationThe actor asked for authority before actingActivation request citing IT-5521
Rejected or blocked attemptsWhere the boundary was, and that it heldSelf-approval at 09:22 left pending
Approver identity and timeA different person granted authority, within the windowIT manager at 09:41
Authority windowHow long the authority lastedRole active until 10:41
Action entryWhat was done with the authority, and whenSign-in methods updated at 09:44
OutcomeThe action achieved its purposeDirector signs in at 09:58; ticket closed

Retention decides whether any of this survives. Microsoft's documentation says Entra audit logs are kept seven days on the Free tier and 30 days on P1 and P2, and that data not routed to longer-term storage cannot be recovered once it expires. A company that never archived its logs may have the tickets but not the approvals, which leaves the middle of the story missing.

One example cannot show how many changes went through the gate, how many blocked attempts were recorded, or whether ticket numbers were typed correctly. Those are measured in SourceX's review with the company.

Does the company qualify, and what stays unknown?

The company needs 50 or more full-time employees at peak (contractors excluded), documented operating history, rights to license its records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

What stays unknown until SourceX reviews it: how many changes pass the acceptance check, how employee identities are de-identified, whether security policy or a managed service provider's contract limits use, and whether any buyer wants this task type. Interest in permission-aware agents across the industry does not mean every audit log qualifies. The company qualification checklist covers the basics, and related records are listed in the data types hub. Partners stay at metadata level: which identity and ticketing systems, how long approvals are kept, and who owns them.

Go deeper on permission-aware agents

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the IT or finance lead confirms that second-approver changes are system-enforced and archived beyond the tool's default window, register as a partner, check the company against who qualifies, and read the terms before you introduce the CIO or COO.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is this page about the company's permission to license its data?

No. Permission-aware agents are about whether each action inside a task had the right authority. Whether the company may license the records at all is a separate question, covered in the guide on de-identification versus permission to license.

Do the records have to come from Microsoft Entra?

No. Entra is used here because its approval rules are publicly documented. Any system with a recorded request, a separate approver and a logged action can hold the same kind of evidence, including ERP, banking and CRM approval workflows.

Can I ask the IT team for an audit log export to check?

No. Partners never request or handle logs, screenshots or tickets. Ask which systems keep approvals, how long, and who owns them; record review happens between SourceX and the company under an agreement.

Sources

  1. learn.microsoft.com/en-us/entra/id-governance/privileged-identit…
  2. learn.microsoft.com/en-us/entra/id-governance/privileged-identit…
  3. learn.microsoft.com/en-us/entra/id-governance/privileged-identit…
  4. learn.microsoft.com/en-us/entra/identity/monitoring-health/refer…
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment