Everything-PR followed 30 AI announcements made between April 1 and June 30, 2025. It checked dated records for 90 days after each one and found a separate dated record backing the tracked access promise in 16 of 30 cases (53%). One release was late and one timetable was revised. The rest were launch-post-only, unverified, untestable, or not yet due.
What the study actually measured
This is a documentary audit, not an activation test. The researchers did not log into accounts to see whether features appeared. "Corroborated" means a second dated record matched the promise. It does not mean every plan, tenant or region had access.
The sample was purposive: eight enterprise AI, eight developer tool, seven cybersecurity and seven marketing software milestones. Google supplied 8 of the 30 cases and AWS 5. The authors say plainly that the rates describe these cases only and are not a market estimate. Treat it as a structured look at 30 launches, not a vendor reliability ranking.
Two caveats are worth keeping in mind:
- A second coder has not yet reviewed the clarity ratings.
- The study's publisher discloses overlapping ownership with another PR firm, and the page carries a sponsored promotion for a PR agency. The method is documented in detail, but the study comes from a PR shop with a commercial interest in announcement quality.
The Microsoft cases
Both Microsoft milestones were announced on May 19, 2025, and both were rated "Clear" and "Corroborated."
Azure AI Foundry Agent Service GA. Microsoft Learn's what's-new history lists "Agent Service GA" under May 2025. The same entry lists the Foundry Visual Studio Code extension, connected agents, trace agents and triggering agents through Azure Logic Apps as accompanying features. The page shows a month, not an exact day. Treat the GA as a May 2025 milestone.
That page now carries a deprecation notice for the classic agents experience, with retirement set for March 31, 2027. The notice points customers to the newer Microsoft Foundry Agents Service. A GA label has a shelf life, which is a good reason to check lifecycle pages as well as launch dates.
Microsoft Entra Agent ID initial inventory preview. Microsoft's Entra blog post of May 19, 2025 describes a public preview. It was an inventory-first release: a unified directory of agent identities created across Copilot Studio and Azure AI Foundry. The post said more capabilities would follow over six months, including richer access controls and lifecycle management. Those were roadmap items, not preview features. The post also gives a concrete way to find the preview: in the Entra admin center, go to Enterprise applications and set the Application type filter to Agent ID (Preview).
The comments on that post show what the study's documentary method cannot see. One reader reported that only Copilot agents appeared in the Agent ID category, and Foundry agents did not. Another suggested the project-level managed identity was what showed up instead. These are anecdotal reader comments, not Microsoft statements. Still, they illustrate the gap between a corroborated launch and what a given tenant sees.
GitHub's date: a correction worth knowing
The study lists GitHub's Copilot coding agent as a Microsoft-owned developer milestone. It says the preview opened to Copilot Business customers in a June 19, 2025 changelog entry. That date looks off. GitHub's changelog dated June 24, 2025 says the agent was opened to Copilot Business subscribers. The June 19 entry I found is a different post. It made the agent available in all repositories by default for users who already had access.
The study's conclusion holds either way: access widened inside the 90-day window. For anyone building a rollout timeline, though, the Business date is June 24.
The eligibility details matter more to admins than the date:
- The May 19 preview covered Copilot Pro+ and Copilot Enterprise, and Enterprise administrators had to enable a policy first.
- On Business, an administrator must enable the "Copilot coding agent" policy before users can assign issues to Copilot.
- Using the agent consumes GitHub Actions minutes and Copilot premium requests, starting from the entitlements included in the plan.
Later changes also moved the status. A GitHub community discussion, updated in September 2025, says the agent became generally available for all paid Copilot subscribers. A study frozen at day 90 won't capture that.
What the broader results say
- Clear announcements verified more often. 13 of 19 "Clear" announcements were corroborated, against 3 of 10 "Partial." The authors caution that this mostly reflects measurability. Missing dates or access details make a claim hard to match to a second record. It does not show that clear wording makes launches succeed.
- Late and revised cases. Google's Gemini 2.5 Flash was the one late release. Production availability was promised for early June and dated to June 17. Salesforce's Agent Health Monitoring planned August GA, showed none in the reviewed records by day 90, and had a later update moving the target to spring 2026. That later update records a revised timetable. It does not prove when release happened.
- Missing regions. Geography went unstated in 21 of 30 launch records (70%).
- Conditions that decide access. The study cites a Google Agentspace allowlist, OpenAI deep research connectors that need administrator enablement, and Cursor Background Agent access that required Privacy Mode to be disabled.
- Thin records. Five launches had only the launch post. Three of those were AWS milestones. "Launch record only" does not mean access failed.
By sector, corroboration was 5 of 8 for enterprise AI, 6 of 8 for developer tools, 2 of 7 for cybersecurity and 3 of 7 for marketing software. The groups are small, and the authors attribute the lower counts mostly to thin public records.
A checklist for admins
The study's four-point advice works well as an IT pre-flight check. Here it is with the Microsoft examples applied:
- Pin down the stage. Is it a preview, public preview, GA, or "coming soon"? Entra Agent ID was a preview focused on inventory. Foundry Agent Service was GA.
- Check eligibility. Look at the plan, allowlist or admin policy. For Copilot coding agent, that was a policy toggle for Enterprise and Business.
- Look for a region list. Seven in ten launch posts in this sample didn't give one. Check the product's documentation for regional availability before promising a date internally.
- Find the second record. A changelog entry, Microsoft Learn what's-new page or release note is what turns a promise into something you can plan around. Then check whether the date it gives matches the headline.
Bottom line
Don't read the 53% figure as "AI vendors keep half their promises." It means that in this hand-picked, Google-heavy sample, a second dated record could be found for about half of the tracked commitments. The most useful result is the pattern. Launch posts are often silent on region, plan and admin prerequisites, and secondary coverage sometimes misdates things, as the GitHub Business date shows. Read the changelog and the Learn page, and check your own tenant before you schedule the rollout.
References
- AI Launch Availability: 16 of 30 Access Promises Verified - Everything-PR Everything-PR · 2026-11-21T04:51:34.742000+00:00
- Copilot coding agent is now generally available! 🚀 · community · Discussion #159068 · GitHub github.com
- GitHub Copilot coding agent is available for Copilot Pro users in public preview - GitHub Changelog github.blog