Microsoft’s November 5 roundup of October Foundry changes distinguishes several release stages: the Microsoft Copilot harness is in public preview, while Browser Automation and long-running resilience for hosted agents are generally available. The roundup also introduces the Decisions API in Foundry. These are Microsoft’s product announcements, not independent evidence of performance in a particular business. Read Microsoft’s release roundup.
Availability is not a deployment decision
An owner considering an agent should start with one bounded workflow. For example, an assistant might collect documents for a staff member to review. That is a different responsibility from approving a payment, changing a customer record or submitting a binding order. The test plan should reflect the actual consequence of each action.
Preview features deserve a separate evaluation path. Keep an inventory of the components being tested, the release stage and the fallback if the service changes. Even a generally available feature still needs to be tested against the organization’s permissions, data and error conditions.
Test interruptions and repeated actions
A convincing demonstration is not just a successful first attempt. Stop the workflow midway and inspect what happens when it resumes. Check whether it recognizes a completed step or performs the action twice. Test an expired session, a missing document and a response that cannot be interpreted safely.
Use synthetic or appropriately sanitized records while establishing these boundaries. Define which actions require staff approval, and retain enough information for a reviewer to reconstruct what the system attempted. An agent that cannot explain its operational history is difficult to support when a customer disputes the result.
Measure the finished task
For a small business, the most useful evaluation may be a simple comparison: how many cases were completed correctly, how many needed correction, how much staff time remained and what the full run cost. Faster text generation is not the same as faster resolution.
Set a limited pilot and a clear stop condition. If the workflow makes duplicate changes or loses track of approval, reduce its permissions until the problem is understood. Product releases can expand what is possible; a business still has to decide what it is prepared to rely on.
Related: autonomy with clear operational boundaries. Photo: Yan Krukau / Pexels, illustrative business meeting; not Microsoft personnel. No vendor endorsement or independently measured performance claim is implied.
Eric Kuvykin
Publisher and editorial director covering payments, fintech, merchant services, banking, AI, technology and operating strategy for small and medium-sized businesses.
