Microsoft to Engineers: Don't Go Crazy With the AI Use. It's Not Cheap
Tokens are like AI credits; the more words you use when prompting an AI, the more tokens you eat up. For a time, tech employees were encouraged to use AI as much as possible, but that activity, or tokenmaxxing, resulted in huge bills for the companies using it. Tokenmaxxing is not what we are optimizing for."Instead, "I want all of us focused on maximizing outcomes that move the needle for our customers and our business," Parikh said.
- ▪Tokens are like AI credits; the more words you use when prompting an AI, the more tokens you eat up.
- ▪For a time, tech employees were encouraged to use AI as much as possible, but that activity, or tokenmaxxing, resulted in huge bills for the companies using it.
- ▪Tokenmaxxing is not what we are optimizing for."Instead, "I want all of us focused on maximizing outcomes that move the needle for our customers and our business," Parikh said.
PCMag files mainly under tech. We currently carry 402 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | PCMag |
| Canonical URL | https://www.pcmag.com/news/microsoft-to-engineers-dont-go-crazy-with-the-ai-use-its-not-cheap |
| Publication time | Tue, 04 Aug 26 20:39:18 +0000 |
| Retrieval time | 2026-08-04T20:45:45.436Z |
| Last seen | 2026-08-04T20:45:45.436Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 4rDP5NhCtIer · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
As the cost of AI continues to skyrocket, Microsoft engineers are getting new limits on their AI use in the workplace.According to a company email obtained by 404 Media, Microsoft is making the more affordable OpenAI GPT-5.6 its default model for internal use to “get greater value from our token investment.” Additionally, Microsoft divisions will soon have an “AI token budget target" that employees can individually track. Tokens are like AI credits; the more words you use when prompting an AI, the more tokens you eat up. For a time, tech employees were encouraged to use AI as much as possible, but that activity, or tokenmaxxing, resulted in huge bills for the companies using it.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at PCMag.
Discussion
0 commentsMore from PCMag
