Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Teams and leaders have 8 accounts; GILD prints their sentiment from 20.
Teams and technical leaders
10 sources. These accounts come from teams and companies building on Foundry and focus on data terms and on running agents in production.
Individual builders
35 sources. These accounts focus on the model catalog and on Foundry Agent Service, from developers building on Foundry on their own.
All practitioners
45 sources. This gives the broadest read, but combines solo projects with production teams that can reach different conclusions.
45 sources from practitioners, by the context they work in. Filled rows count for this group.
- Individual builderDevelopers building on the platform on their own35 sources, counted here
Emphasizes Catalog breadth and Agent Service bugs
- Small product team2 to 10 engineers, or an unnamed startup team2 sources, counted here
Emphasizes Reliability and unexpected bills
- Product or platform team11 to 50 engineers, or a named company's team4 sources, counted here
Emphasizes Agent tools and publishing in production
- Technical leadershipLeaders setting model and platform choices across teams2 sources, counted here
Emphasizes Platform choice by committed spend, and missing model features
- Organization-wideEnterprise or company-wide AI platform2 sources, counted here
Emphasizes Keyless access and model policy at scale
What changes with scale. Individual builders focus on which models the catalog carries and on Agent Service bugs. Team and company accounts focus on data terms under existing Microsoft agreements and on features that block production use.