After proving its custom silicon strategy with Maia 200, Microsoft is preparing a much larger Maia 300 push designed to support both AI training and inference.

The post Maia 300 Could Give Microsoft Azure a Major AI Infrastructure Advantage appeared first on Cloud Wars.

Microsoft is warning IT teams and software developers to prepare for major changes to Windows code signing. Organizations that rely on hardcoded certificate checks or legacy cryptographic standards could face application failures if they do not adapt before the transition begins.

Windows code-signing infrastructure is a service for digitally signing Windows components, drivers, updates, and software so that users and operating systems can verify that the code genuinely comes from a trusted source and has not been altered after it was published. It relies on trusted certificates, certificate authorities, cryptographic algorithms, and validation mechanisms built into Windows to establish trust before software is installed or executed, which helps protect systems from tampered, malicious, or counterfeit applications.

New cryptographic standards could break older applications

Microsoft is making these changes as the existing Windows Production PCA 2011 certificate is set to expire in October 2026. The company also aims to strengthen security by adopting stronger cryptographic algorithms and preparing Windows for a future in which quantum computers could potentially weaken current encryption methods.

To prepare for this change, Microsoft has already begun transitioning to a replacement certificate authority. The company warns that applications tied to the old certificate could experience compatibility issues or stop working properly after the transition.

“To support evolving security and compliance requirements, Windows is moving toward stronger configurations, including RSA-3072 and SHA-384, by the end of 2026. Applications that hard-code expected signing configurations might fail during this transition,” Microsoft explained.

In 2027, Microsoft plans to introduce post-quantum cryptography by default for Windows code signing, which enables protection against future quantum-computing threats.

How IT Teams can prepare for the Windows code-signing transition

Microsoft is encouraging IT administrators to take a close look at the software running in their environments before the upcoming Windows code-signing changes take effect. Organizations should engage with key software vendors and confirm that their products use Microsoft’s supported trust-validation mechanisms. Moreover, applications that depend on fixed certificate names, thumbprints, issuers, or outdated cryptographic settings may encounter compatibility problems when Microsoft introduces new signing certificates and stronger security standards.

Additionally, IT teams should verify that vendors have tested their applications against the new certificate hierarchy and updated signing algorithms, including SHA-384-based signatures. Companies that maintain private trust stores should also ensure they have a reliable process for recognizing and deploying legitimate Microsoft certificate updates. Going forward, Microsoft recommends preparing for the upcoming transition to post-quantum cryptography.

The post Microsoft Warns Windows Code Signing Changes Could Affect Older Applications appeared first on Petri IT Knowledgebase.

Craig Hewitt, founder of the podcast hosting platform Castos, joined this episode of Zero to Agent in 30 Minutes to show how he uses the Codex application’s voice mode to run his development environment without touching the keyboard. Craig walked through what voice mode actually is, how it differs from dictation tools, and how he uses it to control his browser and other applications on his computer.

Setting up Codex for hands-free development, step by step

1. Set up browser and computer access. Enable computer use in the Codex app and configure browser access so the agent can work with websites and other applications. Craig recommended requiring approval before the agent accesses most applications or sites.
2. Start a voice session. Launch voice mode and give the agent instructions conversationally. Craig showed that the voice interface remains available as you move among applications, allowing you to direct work across your computer without repeatedly returning to the chat.
3. Give the agent browser tasks. Craig asked the agent to open websites, search for information, and navigate pages. He also described using browser control for routine jobs such as completing forms when the agent already has the necessary context.
4. Let the agent work across applications. Computer use extends the workflow beyond the browser. In Craig’s demonstration, the agent opened Cursor, found a specific repository, reported on uncommitted changes, and later committed those changes after receiving permission.
5. Add specific page content to the conversation. Craig showed how you can select part of a web page and add it directly to the chat. That gives the agent the context needed to act on a particular element, such as a section of an interface you want to change.
6. Keep permissions narrow. Browser and computer control create real risks, including unintended actions and prompt injection from web content. Craig said he requires approval for most applications, grants broader access only to selected tools and local development sites, and avoids sites he doesn’t trust.

Voice mode let Craig direct browser, application, and coding tasks through conversation. The demo also raised a real question about delegation. Once an agent can act on your behalf, you have to decide what you’re actually comfortable handing off. Craig used permission settings, a list of trusted sites, and human review to manage that.

Coming next week

In the next episode of Zero to Agent in 30 Minutes, Jayeeta Putatunda, forward deployed AI engineering lead at Turing, will build an agent that helps financial analysts keep up with a constant stream of new information. She’ll show how the agent categorizes financial news, ranks stories against analysts’ coverage profiles, and explains why each development may deserve attention.

Scott and CJ break down Stripe's $7B acquisition of OpenRouter, the SvelteKit 3 release candidate, and their first look at TanStack Charts. Plus Zed's new Delta editor, stealing reasoning traces from proprietary LLM APIs, why dark mode toggles only need two states, and all 43 quintillion Rubik's cube states in your browser.

Show Notes

• 00:00 Welcome to Syntax!
• 02:20 SvelteKit 3 Release Candidate
• 07:43 Video editor recs
  • Casey Faris
• 09:58 TanStack Charts First Look
  • TanStack Charts
  • TanStack Charts implementations of every official shadcn/ui chart
• 14:24 Ponytail AI Tool
• 17:22 Zed Delta Editor
• Introducing Delta
• 23:44 Stripe acquires OpenRouter for $7B+
• 29:27 Stealing Reasoning Traces from Proprietary LLM APIs
• 35:03 First look at Cursor’s GitHub killer
• 42:34 Dark Mode UX Discussion
• 46:40 Brought to you by Sentry!
• 48:34 Should AI respond in plain language?
• 52:57 Swamp Club Automation
• 01:02:37 Fight AI slop with this anti-slop plugin
• 01:03:39 Rubik’s Cube Permutations
• 01:05:02 Hackweek

Hit us up on Socials!

Syntax: X Instagram Tiktok LinkedIn Threads

Wes: X Instagram Tiktok LinkedIn Threads

Scott: X Instagram Tiktok LinkedIn Threads

Randy: X Instagram YouTube Threads