Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
This is our high level architecture for Microsoft Autopilot and where @openclaw fits in
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
If you attending #MSIgnite in San Francisco this coming week, I'll be giving a talk about Microsoft Autopilot!
Autopilot is our autonomous digital teammate that is powered by @openclaw and runs securely in the Microsoft 365 Cloud.
Hope to see you there!
Automate the Follow-Through with Autopilot ignite.microsoft.com/en-US/sโฆ
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
Agents are the new service principals, only more dangerous. At #MSIgnite, I'll share four controls every production agent needs. #Agents #Governance ignite.microsoft.com/en-US/hโฆ
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
Microsoft Threat Intelligence has observed threat actors using agentic AI tools to search public GitHub repositories for exposed secrets and then using stolen secrets for further malicious activity against the compromised organization. msft.it/6017aA1bS
Searching open code repositories for exposed credentials, secrets, keys, and other authentication material is a well-documented technique, but agentic tooling like ARTEX allows threat actors to scale and accelerate scanning for secrets, analyzing the output, and conducting follow-on attacks.
Microsoft has also investigated follow-on activity related to successful service principal sign-ins involving multiple application IDs, including cases where a single multitenant application credential was used across multiple tenants. The threat actor used the compromised credentials for cloud resource discovery, and credential and data exfiltration.
Microsoft encourages organizations to scan their code for secrets. In addition to removing the secrets from the code base, affected organizations should immediately rotate any exposed keys or credentials. Read our blog for more details, detections, and guidance for public monitoring and reducing exposure.
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
Update.
Microsoft is offering buyouts to 60,000 employees.
Thatโs 27% of the company.
I called our rep to ask who would support E7 now.
He said his team is excluded. Some sales, marketing and data center teams are.
So the people who sell the product stay. The people who built it get a package. The agents stay too. Theyโre in the data center.
I asked what the program is called. He said โVoluntary Exit Offer.โ
I asked whose exit. He said โYours.โ
I said Iโm a customer.
He said โDifferent SKU.โ
Microsoft expects fewer takers than July, when over 30% accepted. They have a forecast for free will. Iโd like that dashboard.
They also said they may try to retain top talent after they accept. You take the buyout and get asked to stay. I told Finance thatโs called a renewal.
Agent 365 governs agents with the same protections used to manage people. This week theyโre managing 60,000 people. The agents werenโt consulted. They arenโt eligible.
Claude is now inside Copilot. A Claude Code laptop is why my senior developer was contained. His risk score is green now. His PIP is not.
The Guardian Agent flagged the memo announcing the buyouts. I approved it. 100%.
My risk score dropped. Iโm number two.
Number one is a sentence about helping employees โshape their next chapter.โ
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.
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
Microsoft offers buyouts to 60,000 employees. This latest exit offer is available to far more employees than the previous retirement one, and comes just months after Microsoft laid off 4,800 employees. Full details here ๐theverge.com/tech/1018666/miโฆ
UPDATE: Specific mitigation guidance for the recently identified PHP critical vulnerabilities is now available. Secure your servers today. Guidance and technical steps here: nsa.gov/Press-Room/Press-Relโฆ
Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
Microsoft Threat Intelligence is tracking an active supply chain attack in which a threat actor compromised the trusted OAuth App of the backup application ConnectWise Cloud Backup (AppId: 506e08f9-6e9a-4da4-942b-a099a03644ae), formerly SkyKick Backup, to obtain access tokens across customer tenants.
ConnectWise Cloud Backup is a multitenant vendor application; customers grant consent for the application to operate in their tenants. We assess that the threat actor likely abused permissions previously granted by customers to the application, including highly elevated permissions like Directory.ReadWrite.All.
On October 15, 2026, we observed broad successful service principal authentication originating from the IP address 144.172.64[.]128. Follow-on activity included Microsoft Graph API reconnaissance and attempts to add additional credentials on the related service principal in target tenants to maintain direct access as a backdoor.
Microsoft Defender detects post-exploitation activity with the following alerts:
- Any alert related to "Suspicious sign-in"
- Graph API activity from a Microsoft threat intelligence IP address
- Verified Threat Actor IP
Defenders should review service principal sign-ins from unrecognized IP addresses, app credential changes, and OAuth grant activity associated with this specific OAuth AppId. In addition, we recommend looking for Threat Intelligence alerts on matching of IP against the Graph API activity and service principal activities.
We will continue to monitor this incident and will share updates as they become available. We encourage customers to check ConnectWise advisory for more information and additional guidance: msft.it/6013aQBvV.
Indicators of compromise (IOCs):
- App name: ConnectWise Cloud Backup
- AppId: 506e08f9-6e9a-4da4-942b-a099a03644ae
- Publisher name: SkyKick
- Source IP: 144.172.64[.]128
- User agents: Python-urllib/3.12, python-requests/2.31, python-requests/2.34.2
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
Microsoft shipped a really compelling product on top of @OpenClaw today. We worked with them since March to make the codebase ready for large-scale deployments, they are a great partner and open-source contributor. ๐๐ฆ
Today we announced the preview of Microsoft Autopilot is rolling out to our first customers - "Autopilot is a persistent, proactive and personal agent that keeps working even when youโre not"
It's been a while since I updated you all on what we are building. First Scout is now Autopilot, and my team leads building this personal agent.
We are building Autopilot on @openclaw, working with @steipete and the OpenClaw Foundation to make it a fantastic enterprise grade runtime.
blogs.microsoft.com/blog/202โฆ
Re-introducing Sebastian, my Autopilot - and he is as excited as I am!
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
Copilot Apps go far beyond chat - UX in Copilot ๐คฉ
This video showcases an HR agent combining AI, trusted business data and rich UX, including forms, charts and actions, directly inside the Copilot canvas.
See the art of possible โ msft.it/6010aOfXa
#Copilot #Agents
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
Someone asked me for a high-level map of Copilot governance and compliance.
So I mapped the whole stack.
> Inventory + control: M365 admin center + Agent 365 registry
> Identity + access: Microsoft Entra
> Data + compliance: Microsoft Purview
> Runtime security: Microsoft Defender
> Build + release: Power Platform admin center + Copilot Studio
> Content readiness: SharePoint Advanced Management
Microsoft Security Dashboard for AI adds the cross-stack risk view in public preview.
Then governance continues inside Foundry, Fabric, GitHub Copilot, Microsoft Security Copilot and Dynamics 365.
Purview handles one critical layer. Enterprise Copilot governance needs the full control-plane picture.
Save this one.
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
watch me how i work with coding agents like a caveman.
youtu.be/DPgJjRdQWrg?is=uYFNโฆ
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
Hereโs your monthly reminder that you shouldnโt be prompting coding agents anymore.
You should be designing loops that prompt your agents.
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
I built a public MCP storefront. One receipt URL satisfies both your security audit AND your finance billing.
Same endpoint, same six checks, two runs: hosted Claude + fully-local Qwen3.6 27B.
Try it from any MCP client:
go.fabswill.com/receipt2buyeโฆ
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
Azure Skills looks like Microsoftโs capability layer for coding agents in Azure.
25 skills across deploy, diagnostics, cost, RBAC, AI, AKS, etc. โ paired with MCP tooling for live Azure context/actions.
github.com/microsoft/azure-sโฆ
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
GitHub folks are amazing while we melt their servers.
To @github team and @ashleywolf on a weekend coming to our rescue at @openclaw. Upgraded the entire maintainer team to Enterprise so we can keep doing gods work without hard rate limits. We love you ๐ซถ
Martina Grom โ๏ธ ๐โโ๏ธ ๎จ๐ฆ#bekind #msignite retweeted
#developers workshop time! Snapshot at #m365conf. @theChrisKent @DavidWarnerII @bernierh and the gang. ๐





























