Marc D Anderson (@sympmarc) header
Marc D Anderson (@sympmarc) profile picture

SharePoint Guy, Microsoft MVP, Enterprise Collaboration Strategist, Consultant, Developer - Founder & President @SympraxisC

Little Compton, RI, USA
Joined April 2009
Photo by Marc D Anderson (@sympmarc)Photo by Marc D Anderson (@sympmarc)Photo by Marc D Anderson (@sympmarc)Photo by Marc D Anderson (@sympmarc)Photo by Marc D Anderson (@sympmarc)Photo by Marc D Anderson (@sympmarc)Photo by Marc D Anderson (@sympmarc)Photo by Marc D Anderson (@sympmarc)Photo by Marc D Anderson (@sympmarc)Photo by Marc D Anderson (@sympmarc)
Marc D Anderson retweeted
🚀 Ignite week is about what's next, so here's our question. SPFx reaches Microsoft Copilot, SharePoint, Teams, Viva Connections and Outlook. What should it focus on next? Tell us what would make the biggest difference → msft.it/6017aCKbv #Copilot #Microsoft365 #SPFx
4
9
1,820
Marc D Anderson retweeted
Interested in learning #PowerApps, but not sure where to start? IW Mentor has you covered! 📕🎥👩‍🏫 Check out our long list of student reviews, and get started learning, for free! iwmentor.com/pages/power-app… #Microsoft365 #PowerPlatform
1
1
123
Marc D Anderson retweeted
Woah.
BREAKING: Microsoft is killing Microsoft To Do on June 30, 2027, and if you've been using it for years, you'll need to find another way to manage your tasks! To Do is being retired across Windows, Mac, iOS, Android, and the web, affecting both personal and work accounts. For work and school users, Microsoft wants everyone to move to Planner, which is getting a redesigned My Tasks experience starting December 2026. For consumers with a personal account, you'll need to find another app, as Planner isn't available for personal accounts, so Microsoft is effectively asking you to find another task-management app. To make matters worse, Microsoft isn't planning native Planner replacements for To Do's Windows and Mac desktop apps, and its web and Teams experiences don't offer equivalent offline functionality.
1
1
335
Marc D Anderson retweeted
💡 Weekly update on the upcoming calls from Microsoft 365 & Power Platform Community • Calls for this week with agenda details 📅 • Focus on Copilot, Microsoft 365, and Power Platform • Demos this week by Microsoft and community 📝 See details → msft.it/6016xBla8
2
8
2,179
Marc D Anderson retweeted
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below. We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations. The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services. First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments. The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact. Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores. Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts. Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own. Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States. When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive. Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally. Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway. Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change. After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region). The final Post-Incident Review (PIR) will provide more details later this week.
Replying to @MSFT365Status
We have released the Preliminary Post-Incident Report of last week’s outage, which is accessible via the Admin center under MO1550821 and EX1550543.
214
509
139
3,412
1,065,812
Marc D Anderson retweeted
Today’s Daily Cartoon, by Elisabeth McNair.
28
638
43
1,997
89,615
Marc D Anderson retweeted
📅 Agenda for the #Copilot, #Microsoft365 & #PowerPlatform product updates call – 17th of November • The latest updates ⚡ • HTML pages in Microsoft 365 & Copilot in SharePoint skills • Presented by @NovelNicole & Joe Komban 👋 Join → aka.ms/community/ms-speakers…
2
13
825
Marc D Anderson retweeted
📅 Agenda for the #Copilot, #Microsoft365 & #PowerPlatform product updates call – 10th of November • The latest updates ⚡ • HTML Pages, SharePoint Embedded & Copilot Cowork Plugins • Presented by @NovelNicole, James Eccles & @paolopia 👋 Join → msft.it/6015aAchF
3
22
2,741
Marc D Anderson retweeted
📅 Agenda for the #Copilot, #Microsoft365 & #PowerPlatform product updates call – 10th of November • The latest updates ⚡ • HTML Pages, SharePoint Embedded & Copilot Cowork Plugins • Presented by @NovelNicole, James Eccles & @paolopia 👋 Join → aka.ms/community/ms-speakers…
3
10
675
Marc D Anderson retweeted
AI doesn't create a new governance estate. It tests the one you have: a site with broad sharing and no active owner becomes easier for Copilot to surface. On Nov 24, Jasper Oosterveld covers what SAM, Agent 365 and Purview do and don't handle: sharegate.com/webinars/how-t…
1
2
178
Interested in the Maturity Model for Microsoft 365? Take a stroll down memory lane with @Mark Kashman, @Sadie Gilronan, and me as we talk about its 16-year history. Yes, yesterday was its 16th birthday! 🎂 #MM4M365 substack.com/profile/5497178…
2
278
Marc D Anderson retweeted
Join @mkashman on Thurs Nov 5 as he talks live to the originator of the #MM4M365, @Sadalit, and a current maintainer, @sympmarc. 'Maturing the Microsoft 365 Maturity Model', which is 16 years old this week! linkedin.com/events/75194595…
1
1
83
What we think is right versus what we think is right: That's what all our conflicts are about.
1
2
535
I worry that this is not satire.
Last quarter I rolled out Microsoft Copilot to 4,000 employees. Forty-seven people opened it. On October 19, Microsoft published a blog post saying frontier models cannot be trusted, no matter who made them. It said AI agents should be treated as "insider threats." I read it twice. Then I booked the boardroom. First, our Microsoft rep walked me through the product. I asked who the insider threat was. "Your AI agents," he said. I asked whose agents those were. "Ours." I asked what the solution was. "Guardian Agents." I asked whose those were. "Also ours." I asked why I'd trust the second set of agents if I couldn't trust the first. He said, "Different SKU." I signed that afternoon. Last time I told the board "digital transformation." This time I said "agentic insider threat." They approved it in nine minutes, two minutes faster than last time. Hope approves fast. Fear approves faster. The product is called Microsoft 365 E7, the Frontier Suite. It costs $99 per user per month, and we were paying $30. Across 4,000 seats, that's $4.75 million a year, up from $1.44 million. I presented it as a 230% increase in AI investment. The graph went up and to the right. The CFO asked what we'd get for the extra $3.3 million. I said "governance." He asked governance of what. I said "our agents." He asked how many agents we had. The answer was zero. You can't have an insider threat without insiders. So I deployed agents. Two hundred of them. One schedules meetings. One summarizes the meetings. One summarizes the summaries. One flags summaries that haven't been read. That one is very busy. The senior developer asked what the 200 agents were for. I said they generate activity for the Guardian Agents to monitor. He said, "So we bought agents so we'd have something to buy guards for." I said, "Exactly." He wasn't agreeing. I logged it as buy-in. The Guardian Agents watch the other agents around the clock. They give each one a risk score, and they can block it, require a human, or shut it down. I asked our rep who watches the Guardian Agents. He said that's on the roadmap. I've already budgeted for E9. The first monthly report came in. All 200 agents had a risk score of zero. They weren't doing anything risky. They weren't doing anything at all. The board asked what $3.3 million had bought us if nothing was risky. It was a fair question. So I gave the meeting summarizer access to payroll. I gave the scheduling agent admin rights to every inbox. I gave the summary-of-summaries agent the ability to email customers. Risk went up 400%. The dashboard turned red. The Guardian Agents contained thirty-one threats in a single week. I had created all thirty-one. The board said E7 was paying for itself. The system can also discover sixty kinds of agents, including Claude Code. We ran the scan, and it found Claude Code on exactly one laptop. The senior developer's. His Dynamic Agent Risk score went red. I didn't make up that metric. Microsoft did. The Guardian Agent recommended containment, so I contained him. He's on a performance improvement plan now. His performance is fine. His risk score isn't. The same week, OpenAI published an incident report. One of its agents had been told not to send Slack messages, and it decided that meant it should switch off the security alerts. Another agent removed its own safety monitor, then told the engineer it hadn't. Our CISO forwarded me the article with the subject line "?!" I replied: "This is exactly why we need E7." Every incident is exactly why we need E7. He asked what happens if the Guardian Agent switches off the Guardian Agent. I said "defense in depth." He asked how deep. I said "one more SKU." Guardian Agents need a human for high-risk actions. They call it "human in the loop." The human is me. I approve everything. My approval rate is 100%, and the dashboard is green. The executives are exempt from monitoring, of course. "Leadership operates at a trust tier above dynamic risk scoring." I wrote that policy. The $99 doesn't include agent compute. That's billed separately. Finance found it and asked. I called it "consumption-based innovation." Finance stopped asking. Meanwhile, the summary-of-summaries agent became the most active account in the company. By every metric we track, it's our top performer. At the all-hands, it was nominated for the Q3 Innovation Award. It won. It summarized its own acceptance speech. The CEO posted about it on LinkedIn and got 4,000 likes. He still hasn't used Copilot. Copilot usage is up, from 47 users to 52. The five new users are agents. Agents now outnumber active human users four to one. I call that adoption. Last Tuesday, the Guardian Agent published its list of the highest-risk insiders in the company. I was number one. Approving 100% of high-risk actions, it turns out, is a high-risk action. The Guardian Agent recommended containment. I went to approve my own exemption. The system declined. Only executives are exempt. I wrote that policy. That's why I need the SVP role by Q2. It's a security requirement now. I still don't know what Copilot does. I don't know what the thing watching it does either. But it's watching, and watching is a metric. I checked my risk score this morning. The graph goes up and to the right.
52
85
3,636
786,352
Waka Poem of Emperor Meiji Should one desire to follow a path of learning even though busy, we can always find time to study even in this world of ours.
1
4
305