Microsoft’s agent controls change the AI investment case

An AI agent governance strategy belongs in the investment plan

An AI agent that prepares a report and an agent that changes a business record create different management responsibilities. Your investment plan should reflect that difference. We recommend making an AI agent governance strategy part of the next funding decision, with explicit limits on what each workflow may do and who remains accountable.

On 19 October, Microsoft announced an expansion of Project Perception to supervise agents operating inside enterprises. This extends a programme introduced in July, adding an internal-agent focus to its security direction. For executive leaders, the significant change is the growing emphasis on controlling agents continuously as they work. Microsoft’s announcement.

Our position is clear: fund useful automation alongside the ability to contain it. A convincing demonstration of task completion should earn further testing. Authority to change records, communicate externally or commit resources should require separate evidence.

What Microsoft has announced

Microsoft describes three new controls: Dynamic Permissions, Dynamic Agent Risk and Dynamic Conditional Access. Together, they are intended to scope authority to a task, reassess risk during execution and adjust what an agent can do. Responses can include preserving reads while blocking changes, requiring human approval or stopping execution. Microsoft also describes Guardian Agents that help investigate and contain changing risks. Microsoft Security’s explanation.

Project Perception remains an invitation-only limited public preview in Microsoft’s documentation, while the October announcement gives no feature-specific rollout dates. You should therefore confirm access to the particular controls before making them a dependency for a production programme. Microsoft Learn.

The strategic implication is broader than one release. We would now ask every funded agent initiative to demonstrate how its authority can be reduced while it is running. That creates a practical middle ground between unrestricted execution and abandoning an otherwise useful workflow.

Give business authority its own investment gate

Consider a hypothetical MENA distribution group testing an agent that investigates delayed customer orders. Initially, it reads shipment records and drafts an explanation. A later phase might let it change delivery priorities or send customers revised commitments.

Those phases need different investment decisions. Reading and drafting can be evaluated through accuracy, turnaround time and reviewer effort. Changing delivery priorities also requires an agreed commercial policy, an accountable manager and a way to reverse an inappropriate action. Sending a commitment introduces another consequence: someone outside your organisation may rely on it.

We would separate the funding gates accordingly. First establish whether the agent produces useful work. Then establish whether the organisation can safely delegate a defined action. This gives your enterprise AI roadmap a clearer sequence and prevents a successful drafting trial from becoming an informal mandate for broader autonomy.

A business sponsor should be able to explain the proposed delegation in ordinary language: which decision is being transferred, within what boundary, and under whose responsibility. If that explanation remains vague, expanding access is premature.

Make the economics include supervision

The agent automation business case should include the cost of keeping work under control. We recommend counting integration, monitoring, human review, exception handling and recovery alongside usage charges. Time saved in preparing an output can be absorbed by time spent investigating uncertain actions.

Measure cost per accepted business outcome. For an order investigation, that could mean a complete, accurate explanation accepted by the responsible employee. Also record how often staff must intervene, how long they spend correcting work and whether the workflow can resume after an interruption.

These measures change the executive conversation. A slower workflow with predictable review effort may deserve expansion before a faster workflow that creates difficult exceptions. The relevant comparison is the operating result you can sustain within your budget and risk appetite.

Avoid assuming that an agent-security announcement establishes coverage across your entire application estate. Ask your team to demonstrate the actual path from a risk signal to a restricted business action in the workflow you intend to fund.

Keep the MENA scope concrete

Regional groups should start with one legal entity and one bounded process. A shared corporate platform should still be assessed against each entity’s responsibilities, data and operating arrangements before expansion.

For a UAE mainland project involving personal data, ask counsel to check the UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data and current applicable instruments. Include the proposed handling of agent activity records and processing locations in that review. This identifies the framework to examine without assuming that a security control establishes legal compliance. Official US International Trade Administration overview.

Where your workflow uses Arabic and English material, include both in acceptance testing. Test the complete business task, including corrections and escalation. A polished English demonstration provides limited evidence about how your own documents, terminology and handoffs will behave.

What to do in the next quarter

During the first month, bring the business sponsor, finance leader and security leader together around one proposed delegation. Agree on the outcome, the actions allowed and the point at which a person must decide. Assign one executive owner for the resulting operating process.

During the second month, run a bounded evaluation using representative work and controlled exceptions. Your AI governance implementation should demonstrate that the organisation can withdraw authority, preserve evidence and return unfinished work to a person. Include the cost of those interventions in the evaluation.

During the third month, make an explicit expansion decision. Increase scope only where accepted outcomes, supervision effort and recovery behaviour support the investment. If they do not, retain a narrower role for the agent and resolve the operating weakness before adding authority.

At DeepSolve, our DeepStrategy division works with leadership on AI investment and transformation strategy. Our process begins with understanding infrastructure, opportunities and team readiness, then defining a roadmap and success measures.

Talk with us about a specific workflow you are considering delegating and the investment decision you need to make next quarter.

Sources

1. Microsoft: Securing the agentic insider (2026-10-19)
2. Microsoft: Agents are your newest insiders. Security must move at their speed. (2026-10-19)
3. Microsoft Learn: Use the Project Perception overview and navigation (2026-08-05)
4. United Arab Emirates Allows Cross Border Data Flows of Personal Data (2024-01-22)
5. DeepSolve Our Divisions; undated, accessed 22 October 2026 (2026-10-22)
6. DeepSolve Process and Tech Stack; undated, accessed 22 October 2026 (2026-10-22)
7. DeepSolve homepage and contact form; undated, accessed 22 October 2026 (2026-10-22)

Prepared with AI assistance. DeepSolve is responsible for the published content. Illustrations are conceptual.