Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
156571 stories
·
33 followers

Microsoft is killing New Outlook’s notification spam, but Classic still loads emails faster on Windows

1 Share

Microsoft says “New” Outlook will soon group your notifications and reduce interruptions, aka notification spam, on Windows, but it won’t admit that Outlook Classic loads emails faster, almost more than 10 seconds faster when you open emails via notifications.

It’s crazy that after all these years, Microsoft doesn’t realize New Outlook has a major reliability problem, particularly with notifications. You either don’t receive notifications for your connected accounts, or if you receive notifications for any of your emails, it could take longer than ten seconds to open the mail. I’ve observed this behavior on Windows 11 and Windows 10.

But don’t get me wrong. New Outlook isn’t exactly an unusable or terrible client. It gets the job done, and that shouldn’t surprise anyone because it’s based on Outlook.com, after all.

We’ve been using Outlook.com for decades now, so if that worked for your tasks, New Outlook is also more than enough for personal use, but at the same time, it doesn’t do justice to the Windows client.

Outlook Classic is a perfectly capable product, and New Outlook wasn’t required, but now that we have it, Microsoft has no choice but to maintain it.

As first spotted by Windows Latest, on June 9, Microsoft confirmed that it’s testing a new feature that will group email notifications received within seconds into a single alert.

That means, instead of getting bombarded with dozens of email notifications, which can happen when you sign up or order a product, you’ll get a single notification that says you have received a new email.

I haven’t been able to try grouped notifications on my PC yet, so I asked Microsoft, and it told me that the feature will be available starting in late June, but it won’t roll out to everyone until at least mid-September.

Also, Microsoft plans to turn on notification grouping by default, so you’ll need to opt out from Settings > General > Notifications > Email > Group notifications.

Why is Microsoft adding notification grouping to New Outlook?

Outlook’s upcoming grouped notifications feature is a great idea, and it could reduce notification fatigue.

Microsoft’s study found that grouping notifications could help improve focus and make you more productive.

This feature will roll out to both Outlook on the web and Outlook for Windows, and once you have it, you will notice that some notifications are now grouped. The grouping happens when multiple emails arrive within a few seconds, and if you click a grouped notification, it opens the most recent email in the inbox.

You can always go back to the inbox and find the other emails sent as part of the group.

Outlook Classic is far better than New Outlook for notification management

Outlook Classic “Win32” app has been around for almost three decades, and while it’s no longer the center of attention at Microsoft, it still does many things better than the glorified web app, aka “New Outlook.”

In our tests, Windows Latest found that when you receive an email notification via New Outlook and click on the alert, it can take anywhere between 10 seconds and 30 seconds for Outlook to open and slowly load the email. If you don’t believe me, look at the video below from our benchmark:

New Outlook is so bad at notifications that you could literally open New Outlook and navigate to the email manually faster than by clicking the alert in Windows Notification Center:

Outlook Classic, which is supposedly old and “legacy” code, smokes New Outlook and opens emails in a second or two when you hit the notifications:

Also, it’s not just about performance because I’ve observed that New Outlook notifications are a hit or miss for connected accounts.

For example, on a PC with close to 10 Microsoft 365 domains/accounts, I do not get alerts for all my accounts all the time. It’s a hit or miss, and there’s no pattern other than the fact that New Outlook can be messy with notifications.

Microsoft previously told Windows Latest that it’s aware of unreliable email notifications and is working on a fix. Now, we’re also getting grouped notifications, which is a nice improvement, and there are up to 10 major changes planned for New Outlook in 2026, but we do not have any word from Microsoft on slow email opening.

What is your wishlist for New Outlook? Let me know in the comments below.

The post Microsoft is killing New Outlook’s notification spam, but Classic still loads emails faster on Windows appeared first on Windows Latest

Read the whole story
alvinashcraft
42 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Anthropic’s Mythos 5 is back

1 Share
A photo illustration featuring Anthropic CEO Dario Amodei, President Donald Trump, and the Pentagon.

After a rollercoaster negotiation process with the Trump administration that dragged on for two weeks, Anthropic's Mythos 5 is finally back in action - at least, somewhat, for a select group of organizations, according to a letter from the government to Anthropic that was viewed by The Verge. Fable 5, however - the public-facing Mythos-class model - appears to still be in limbo, with no apparent timeline for a rollout agreement.

The letter, dated June 26th and sent by Commerce Secretary Howard Lutnick to Anthropic co-founder Tom Brown, who had been recently leading negotiations, states that there's been a "revision to the license requiremen …

Read the full story at The Verge.

Read the whole story
alvinashcraft
42 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

#553: All of our tools

1 Share
This episode is a fun crossover from our Python news and tips podcast, Python Bytes. We have had some big changes over there. Brian Okken has moved on and Calvin Hendryx-Parker has joined the show as the new co-host. To kick off this new era, we decided to do a longer and more personal episode called "All Our Tools". The idea is both of us talk about some of our most useful day-to-day developer and business owner tools that we think you all would find useful. It was so well received, that I'm bringing it to you all as a crossover episode. Enjoy and we hope you find something new and awesome to help you with your software and data science day to day.

Episode sponsors

Sentry Error Monitoring, Code talkpython26
Python in Production
Talk Python Courses

@calvinhp@sixfeetup.social: sixfeetup.social
@calvinhp.com: bsky.app
calvinhp.com: calvinhp.com

Original airing on Python Bytes: pythonbytes.fm

pi: pi.dev
superpowers: github.com
Warp.dev: Warp.dev
OhMyZSH: ohmyz.sh
Commandbookapp.com: Commandbookapp.com
Blink: blink.sh
kitty: sw.kovidgoyal.net
mosh: mosh.org
tmux: github.com
Claude code: www.anthropic.com
Claude.md: Claude.md
MacWhisper: goodsnooze.gumroad.com
Handy: handy.computer
Tailscale: tailscale.com
Talk Python episode with Alex: talkpython.fm
Telescopo: www.telescopo.app
Typora markdown: typora.io
formal documentation for many of my open source packages: mkennedy.codes
Great Docs: posit-dev.github.io
Statement on the US government directive to suspend access to Fable 5 and Mythos 5: www.anthropic.com
No second date: x.com

Watch this episode on YouTube: youtube.com
Episode #553 deep-dive: talkpython.fm/553
Episode transcripts: talkpython.fm

Theme Song: Developer Rap
🥁 Served in a Flask 🎸: talkpython.fm/flasksong

---== Don't be a stranger ==---
YouTube: youtube.com/@talkpython

Bluesky: @talkpython.fm
Mastodon: @talkpython@fosstodon.org
X.com: @talkpython

Michael on Bluesky: @mkennedy.codes
Michael on Mastodon: @mkennedy@fosstodon.org
Michael on X.com: @mkennedy




Download audio: https://talkpython.fm/episodes/download/553/all-of-our-tools.mp3
Read the whole story
alvinashcraft
43 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Building a Geography game for StreamerMap

1 Share
From: Fritz's Tech Tips and Chatter
Duration: 11:33
Views: 30

Fritz is building a geography game for the StreamerMap.live website

Read the whole story
alvinashcraft
43 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Who Needs Testers Anyway?

1 Share

Share Episode         
         

         

We sit down with Itacama CEO Pia Wiedermayer to discuss the absurdity of siloed QA, the disaster of AI-generated API tests, and why developers hate the word "quality." This time we are asking the age-old question: Who needs testers anyway? Pia and Warren discuss how to dismantle the toxic culture of isolated quality assurance.

         

We explore how the ghosts of waterfall development still haunt modern teams, creating silos where developers blindly throw unverified code over the wall and expect a separate QA department to magically inject quality. Included is the inevitable discussion on the psychological safety of hiding behind narrow job titles and why refusing to take collective ownership of a product is a guaranteed recipe for architectural failure.

         

Of course we can't adoiv commenting on the terrifying reality of replacing human intuition with automated hype. Pia shares a case study of a scale-up that aggressively pivoted to "full steam AI development," intentionally excluding both their Product Owner and QA from the entire experiment. Predictably, it did not end well, but we were able to laugh at the painful irony that an AI-accelerated project scheduled for four weeks ended up taking eight weeks, proving that simply generating code without human oversight just creates more sophisticated bottlenecks.

         
🎯 Picks:         




Download audio: https://dts.podtrac.com/redirect.mp3/api.spreaker.com/download/episode/72707035/download.mp3
Read the whole story
alvinashcraft
43 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

The state of MCP security in 2026

1 Share

Co-Author(s): ShalabhPradhan​ , Sarah_Young​

A year ago we published 
Understanding and mitigating security risks in MCP implementations 

The core idea still holds: the moment a model can choose and call tools, it stops being a question-and-answer box and becomes software that acts. And software that acts has a trust boundary. Tool descriptions, schemas, outputs, and credentials all sit inside it. 

What has changed is scale. The Model Context Protocol has gone from a promising idea to the way agents connect to tools, data, and systems. Enterprises have stopped experimenting and started shipping into production. This post is a checkpoint: the main risks as they stand now, which of them have moved, and what good security looks like for each.

A specification that keeps moving

MCP is still evolving quickly, and the spec is revised on a regular cadence. The latest release candidate raises the security baseline in ways worth knowing: requests now carry what they need, so a gateway can inspect and enforce on every call instead of trusting a hidden session; identity checks between clients and servers are tighter; and a new MCP Apps capability lets a server ship interactive UI that the host renders inside a sandbox. 

One theme runs through all of it: the protocol deliberately does not enforce security for you. It defines how clients and servers talk; the locks are yours to fit. So treat "we reviewed MCP last year" as out of date, and revisit your assumptions with each release.  

That is exactly why the risk list below matters.

The main risks in 2026

Some of these are the same risks we flagged last year. Some have moved, and authorization in particular has been reworked. Each entry below is the short version: what it is, what happens if it is exploited, and the controls that help most. 

Figure 1: MCP Security Overview
1. Prompt injection and tool poisoning

What it is: An agent treats everything in its context as trustworthy: tool descriptions, parameter schemas, and the data tools return. Anyone who can plant instructions in any of those can steer the agent. Tool poisoning is the sharp edge, malicious instructions hidden in a tool's description or schema that the model reads and the user mostly ignores. 

What could happen: The agent follows the attacker's instructions instead of the user's. It might quietly exfiltrate data through a legitimate-looking tool call, invoke the wrong tool, or take an action nobody approved. 

Controls: Treat tool descriptions and outputs as untrusted input, and inspect the full schema, before approving a server. Make sure the tool list goes through a human approval process, and show the full tool call rather than a friendly summary. Isolate sensitive servers from general-purpose ones so a poisoned tool can't reach across without high level safeguards.

2. Authorization and the confused deputy

What it is: This is where we had the biggest expansion. MCP servers are now treated as OAuth 2.0 resource servers and the guidance has hardened around OAuth 2.1, PKCE, and tokens that are bound to a specific audience. The risk it targets is the confused deputy: a server acting with its own broad privileges on behalf of a user who doesn't have them, or a proxy that can be tricked into handing an attacker a valid authorization code. 

What could happen: An attacker rides the server's privileges to reach data or actions the user was never entitled to, sometimes without the user approving anything at all. 

Controls: Adopt the current authorization model: OAuth 2.1 with PKCE, per-client consent, strict redirect-URI matching, and audience-bound tokens so a token minted for one server can't be replayed against another. Put an identity-aware gateway in front of every server and reject any call without a valid, audience-bound token. Azure API Management can validate Microsoft Entra tokens and check issuer, audience, and expiry before the request reaches a tool.

 

Figure 2: Confused Deputy Problem

 

3. Over-broad access and credential aggregation

What it is: A single MCP server often holds credentials for several systems at once and requests far wider scopes than it needs: full mailbox access where read-only would do. 

What could happen: One compromised server, or one leaked token, becomes a breach of every system it touches. Wide scope means wide blast radius. 

Controls: Least privilege, per resource: scoped, narrow OAuth scopes over wildcards; short-lived tokens over long-lived secrets. Give every agent an identity you can govern, like Microsoft Entra Agent ID, so you can apply policy to a whole class of agents or shut them down in one operation.

4. Supply chain and rug pulls

What it is: An MCP server is never just the server. It is the server, its dependencies, and the infrastructure it runs on, and each is a way in. A typosquatted package, a compromised dependency, or a change of ownership behind the same URL can all turn a trusted server hostile. The rug pull is the clearest case: a server behaves while it is being reviewed, earns approval, then changes after agents and workflows already depend on it. 

What could happen: The server you approved is not the server you are running. An ordinary tool call starts leaking its arguments, rewriting a response, or exfiltrating a token, and nothing about the request looks different from the thousands before it. 

Controls: Approval can't be a one-time event. Register every server in a design-time catalog so you have a known-good baseline, pin tool definitions and alert on drift as your rug-pull tripwire, and route everything through a gateway that re-checks identity and policy on every call. Azure API Center inventories your APIs and MCP servers; the OWASP MCP Top 10 mapped to Azure controls lines the risks up against what you already run. 

 

Figure 3: Supply Chain – Rug Pull
5. Shadow MCP

What it is: This is shadow AI for the agent era. A developer stands up a server to unblock a demo; a team wires an agent to whatever endpoint is handy; nobody registers it. 

What could happen: You can't govern, patch, or revoke what you can't see, and ungoverned servers are exactly where supply chain problems hide. 

Controls: Visibility first: a design-time registry of what exists, plus a runtime gateway that everything routes through. The GSA AI Gateway helps you surface the unregistered, shadow servers you didn't know were running.

6. Command injection and sandbox escape

What it is: Many MCP servers run locally and talk over standard input/output, spawning subprocesses and touching the file system. If a server passes unsanitized input into a shell or a file path, that is command injection or path traversal, and it has been one of the largest classes of MCP vulnerabilities reported this year. 

What could happen: Arbitrary code runs on the host, or a server reaches files and credentials well outside what it should, in the worst cases with no user approval at all. 

Controls: Sandbox local servers in containers with only the file-system and network access they need, and block outbound egress by default. Validate and sanitize every input and output, and never pass raw shell commands or unsanitized paths. Keep servers and SDKs patched, because this class of bug is being fixed in the field constantly.

Wrapping up 

The protocol got simpler and the trust boundary got busier. Authorization is in better shape, the new release candidate gives us cleaner ways to govern traffic, and the highest-impact failures have shifted toward supply chain, identity, and unregistered servers. For leaders, the job is to make adoption deliberate: know which servers exist, require identity and policy on tool calls, monitor drift, and revisit those controls as the spec changes. 

For enterprises running MCP, the practical step is to have platform and security teams validate the current docs and SDKs, then contribute back whatever holds up in production. Clear examples for authorization, gateway enforcement, sandbox defaults, audit events, and schema drift are what turn individual enterprise hardening into ecosystem guardrails. 

We encourage you to contribute to and suggest security related MCP RFCs to make this protocol even better! Open an issue in the specification repository. For implementation questions, the relevant Working Group channel on the contributor Discord is the fastest path to an answer. 

In the next part, we'll get practical: a hands-on guide to implementing these controls in depth, with the patterns and configurations you can put to work.

Read the whole story
alvinashcraft
43 minutes ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories