Verified AI Launch Profile
MAI-Code-1-Flash for Copilot Business and Enterprise
GitHub made Microsoft's MAI-Code-1-Flash coding model generally available to Copilot Business and Copilot Enterprise on June 26, 2026.
At a glance
Launch Snapshot
- Company
- Microsoft
- Launch date
- June 26, 2026
- Launch type
- Major Update
- Category
- AI Models
- Pricing
- The model is generally available for Copilot Business and Enterprise and is billed at provider list pricing under GitHub's usage-based billing. Access depends on plan, administrator policy, supported Copilot surfaces, and current model availability; GitHub's model and pricing documentation should be checked before rollout.
- Free plan
- No
- API
- No
- Open weights/source
- No
Launch Context
Use these links to move from this record into the broader Launch Intelligence database.
Verification & Sources
- Status
- Verified
- Source links
- 4
- Freshness
- Verified July 9, 2026
- Last verified
- July 9, 2026
- Last updated
- July 9, 2026
Key source checks
Suggest a correction
Creator Coverage Next Steps
This launch has signals that may support demos, reviews, creator education, founder storytelling, or practical product explainers.
Launching an AI product that needs clear demos, creator education, and buyer trust? Sponsor a Kingy AI video or launch feature.
Kingy AI Take
MAI-Code-1-Flash gives Copilot Business and Enterprise customers a Microsoft-owned coding model tuned for fast, iterative work inside the Copilot harness. Administrators should enable it deliberately and compare its output quality and provider-list usage cost with existing models before making it a broad default.
Who it is for
Developers, engineering teams, Copilot administrators, and enterprise users comparing fast coding models for iterative or high-volume workflows.
What feels promising
Microsoft trained the model around the GitHub Copilot harness and designed its reasoning length to adapt to task complexity, which may suit fast interactive work.
What feels unproven
Model behavior can change with new checkpoints, Microsoft and GitHub publish the performance claims, and teams still need to compare quality, latency, usage cost, security, and repository fit on their own tasks.
Source-backed record