# What problem Microsoft Finance faced Microsoft Finance needed a practical way to decide where to apply AI across many teams and functions. The goal was to get clear efficiency gains without increasing operational risk or damaging partner trust. Treasury provided a useful example because of its scale, complexity, and control needs: it manages hundreds of billions in cash flows, works with more than 100 banking partners, and uses an outsourcing partner with roughly 1,000 people supporting business processes.
# How they evaluated opportunities The Finance organization developed evaluation criteria focused on the nature of the work rather than the technology. Criteria emphasized:
- Clear, documented process flows.
- Measurable outcomes or ROI metrics.
- Realistic assessment of risk and regulatory expectations.
Kathy Brustad, director, Global Treasury and Financial Services, summed it up: "Always start with what your process looks like first, not what technology you want to use. We always have a metric, business impact, or business ROI in mind when we launch any AI-related project."
# Two practical value patterns Microsoft Finance found two recurring ways AI created clear value.
1) Productivity on repetitive tasks
2) Expanding organizational coverage AI can extend capacity to handle work that was previously unresourced. Treasury began designing AI agents to identify smaller unpaid invoices and follow up where personal attention had been reserved for larger accounts. This expands reach without reallocating staff, and the idea was already being evaluated though not yet in production.
# Sequence and maturity of adoption Microsoft Finance sequenced work to match organizational readiness. Early efforts focused on helping employees use AI assistants in day-to-day work. As governance and experience matured, teams moved to more advanced human-led agent workflows. Some teams are now evaluating more autonomous agents that gather information and generate recommendations while humans retain final decisions.
The organization found that adoption and behavior change were harder than building models: "AI adoption turns out to be the hardest part of this journey, versus just building the technology." The approach therefore included governance, measurement, and staged rollout to increase employee comfort and oversight.
# Practical steps other finance teams can apply
- Map processes and pick tasks with repeatability and measurable outcomes.
- Consolidate disparate systems to create a single source of truth before adding intelligence.
- Prioritize use cases that reduce manual effort or expand coverage where capacity was limited.
- Define ROI and risk metrics up front and sequence adoption with governance and employee training.
When teams treat AI as a tool applied to known processes and measure impact, they reduce risk and raise the chance of achieving clear business value.