Msft

Author: Tom Warren

Note: eco's all the way down

Microsoft has increasingly given CEO titles to the leaders of some of its biggest businesses, such as Microsoft Gaming CEO Phil Spencer and Microsoft AI CEO Mustafa Suleyman. Microsoft also used CEO positions with its GitHub and LinkedIn acquisitions, although the GitHub CEO position disappeared after Thomas Dohmke resigned over the summer. I wonder did the dutch India company have this problem? Everyone had to be a captain or some sort?

Author: Dan Gooding

Note: H1-B Visas and layoffs

When announcing its layoffs this year, the Redmond, Wash.-based company insisted that it was flattening its management layers, as opposed to targeting software engineers and developers at lower levels. However, the Seattle Times reported that only around 17 percent of those laid off at the Redmond campus were designated as managers. Microsoft’s cuts also come after one of its best quarters ever, with the company announcing $26 billion in profit from January through March.

Author: Tom Warren

Note: AI services are still product - models seem to fade to the background

Microsoft is bringing Anthropic’s Claude Sonnet 4 and Claude Opus 4.1 AI models to its Microsoft 365 Copilot today. … Claude Sonnet 4 and Claude Opus 4.1 will also be available as model options in Copilot Studio Well two things. 1. MSFT has long ago abandoned its MSFT first policies. I get though the sentiment of shock. but 2. for tech people the model is everything. for everyone else. its just another service.

Author: Microsoft Threat Intelligence

Note: AI Augments Finding Vulnerabilities, Not Replaces

Through a combination of static code analysis tools (such as CodeQL), fuzzing the GRUB2 emulator (grub-emu) with AFL++, manual code analysis, and using Microsoft Security Copilot, we have uncovered several vulnerabilities. … Copilot identified multiple security issues, which we refined further by requesting Copilot to identify and provide the five most pressing of these issues. In our manual review of the five identified issues, we found three were false positives, one was not exploitable, and the remaining issue, which warranted our attention and further investigation, was an integer overflow vulnerability.