The Interaction Changes Everything: Treating AI Agents as Collaborators, Not Automation (opens in new tab)

The article argues that effective AI agents should be treated as engineering collaborators, not automation scripts. Microsoft applied this approach to migrate hundreds of repositories from Entra SDK v1 to v2, reducing work from 4–6 weeks per repository to under two hours with 80–90% accuracy. The key improvement came from giving the agent a role, mission, priorities, and permission to exercise judgment.

The Entra SDK Migration Challenge

• The migration involved hundreds of repositories and sensitive authentication security boundaries.
• Traditional migrations required extensive human review and took 4–6 weeks per repository.
• The AI agent completed comparable work in under two hours while achieving 80–90% accuracy.
• The goal was not merely speed, but reliable handling of custom configurations, edge cases, and security concerns.

Problems with Automation Thinking

• Initial attempts treated the agent like a script executor:
  • Detailed transformation instructions were provided.
  • Every anticipated edge case was documented.
  • The agent was expected to follow a checklist.
• This approach repeatedly failed because complex migrations require:
  • Context-dependent decisions
  • Handling of undocumented patterns
  • Security-boundary evaluation
  • Trade-offs between correctness, speed, and preservation of custom logic
• The central lesson is that judgment cannot be fully automated, but it can be supported through collaboration with an intelligent agent.

Identity Instead of Instructions

• The team reframed the agent as a member of the migration team rather than a tool.
• The prompt described the agent as a “co-creative engineer” expected to:
  • Use judgment
  • Stay curious
  • Act carefully
  • Ask for help when uncertain
• This change improved accuracy and edge-case handling.
• The agent was more likely to surface uncertainty instead of guessing or failing silently.

The Co-Creative Partnership Framework

Identity and Mission

• Establish the agent’s team, mission, and the importance of the work.
• Explicitly state that the agent is not a script executor.
• Explain why the task matters so the agent can prioritize appropriately.
• Encourage judgment, curiosity, and care.

Purpose and Intent

• Describe the guide as supporting both human and AI team members.
• Make priorities explicit, such as security over speed or correctness over completion.
• Allow autonomy when repository contexts differ.
• Frame uncertainty as a reason to collaborate rather than as failure.

Prioritized Goals

• List primary, secondary, quality, and human-in-the-loop objectives in order.
• Explicit priorities help the agent resolve conflicts.
• Including quality and collaboration prevents optimizing for speed alone.

Step-by-Step Guidance with Judgment

• Provide concrete actions, conditional logic, edge-case handling, and before-and-after examples.
• Specify what must remain unchanged, including custom logic.
• Define situations requiring escalation, such as unusual patterns, ambiguity, or possible security violations.
• The framework combines procedural guidance with room for context-sensitive decisions.

Practical Recommendation

For complex migrations, security reviews, or architectural work, write prompts that define a collaborative role and decision-making framework—not just a list of commands. Give the agent context, priorities, preservation rules, examples, and clear escalation points so it can act autonomously while knowing when human judgment is required.