Tech Noir • Workplace Procedural

The Single Pane of Glass

Sunday night, Frankfurt. Anjali Naidu has ninety-one days until the AI Act audit and a Monday-morning sign-off on a control plane that ships in twelve hours. The marketing said unified. The schema said something else. The question was whether to stop the train, or board it and keep reading.

by Michael EakinsMay 3, 20268 min read1,820 words
Mood: Quiet, procedural, late-night clarity
Tech NoirWorkplace DramaAI AgentsEU AI ActIT DirectorFrankfurtComplianceControl Plane

The kitchen smelled like cardamom and stale coffee, which was Anjali Naidu's fault on both counts. She had brewed the second pot at seven and the third at nine and had not eaten since the second piece of leftover pizza at four. The clock on the oven said 23:14. Through the window the Mainzer Landstrasse was empty in that specific Sunday-night way that always made the building feel more like a borrowed room than a home.

The laptop was open on the kitchen table because the kitchen table had the best light, and because if she went to her desk she would also see the laundry basket, and the laundry basket would win.

On the screen was a Microsoft Learn page on a topic she had been pretending not to need to read for three weeks. Microsoft Agent 365 — Identity and Lifecycle Reference, GA Build, May 1 2026. The page had been published fourteen hours earlier. She had bookmarked it during the kindergarten pickup and had been postponing it ever since.

In the morning she would walk into a conference room on the seventh floor and her CISO, Kasper Linde, would ask her whether the bank could sign off on Agent 365 as the control plane for what their compliance brief called the non-human workforce — eighty-six agents that had appeared inside the tenant in the last fourteen months, sometimes through Copilot Studio, sometimes through a vendor's free tier, twice through a developer who had left in February and had never had his service principal cleaned up.

The deadline was the second of August. Annex III, high-risk systems, employment, credit, and the bank had agents touching all three. Ninety-one days. She had counted again on the way home from her sister's because she did not trust the calendar app to do it the same way Brussels was going to.

She drank the cold coffee anyway.


The Learn page opened with a diagram. Three rings. Observe. Govern. Secure. She had read the marketing two months ago and the schema reference two weeks ago and the partner briefing on Friday. The diagram was the same diagram every time. What she wanted to know was what was not on the diagram.

She found it on the third subpage. Cross-tenant agent telemetry for non-Microsoft federated identity providers — Preview. Preview meant Q4 at the earliest. Preview meant we have not built this yet. Their identity provider for the asset-management subsidiary in Luxembourg was Okta. Their identity provider for the trade-finance team in Singapore was Ping. Both of them had been unifying onto Entra for nine quarters, and at quarter-end nine the answer was still not yet.

She tabbed to her notes. Question one for Kasper: how does Agent 365 audit-log a workflow that crosses an Okta tenant? She wrote Preview, Q4 estimate, no commitment in the column next to it. Then she wrote no commitment again because the second time was the one she would say out loud.

The cat came in and sat on the printout of the AI Act compliance brief that she had been reading by hand because she did not trust herself to read it on a screen at midnight. The cat was not interested in the brief. The cat was interested in the warm spot that the laptop fan was making on the table. She moved the brief out and let the cat have the warm spot. The cat had earned it.


She went back to the diagram and forced herself to read what was there.

Per-agent identity. Lifecycle automation. Risk-based access. Conditional access policies. Defender integration. A single audit log that rolled up from Entra, Defender, Purview, and the Microsoft 365 Admin Center into one queryable surface that compliance could screenshot for the auditor.

The marketing called it a single pane of glass. She had heard single pane of glass three thousand times in nineteen years and had stopped believing in it the second time. The single pane was always a window into the room the vendor controlled. Whatever was outside the room was its own problem.

But — and she made herself sit with this — it was the right room.

Eighty-six agents inside one tenant, governed by one identity layer, audited through one log. That was a defensible answer in August. That was a thing she could stand in front of a regulator and explain. That was a thing she could put in a slide that her board would read without lawyering up.

Whatever was outside the room — the Okta-federated subsidiary in Luxembourg, the Ping-federated team in Singapore, the LangChain code two analysts had written without asking — was its own problem and would be a problem with or without Agent 365. The honest version was that Agent 365 made the inside of the room better and did not yet make the outside of the room worse.

She wrote that down too. Not for Kasper. For herself. Better inside, not worse outside, governance increases monotonically from here. If she was going to sign off on something at 09:30 she wanted to know which sentence she would still believe at 17:30.


Her phone buzzed. It was her counterpart in Singapore, Beatrice Tan, who ran identity for the trade-finance team and who never slept on Mondays. The message read: Have you read the Ping interop note? p4.

She had not read the Ping interop note. She found it in her inbox under a subject line that the Ping reseller had clearly written at the airport. Page four said that Ping was on the partnership roadmap and that production support for federated agent identities was targeted for early 2027.

Targeted. She wrote targeted in the column next to no commitment.

She replied to Beatrice: Read it. We sign off on Agent 365 for Entra-native agents only and we keep Ping out of scope until they ship the federation. Three production zones, one of them out of scope, documented as such for the Annex III file.

The three dots appeared. They went away. They came back. Agreed. Tell Kasper that's also my answer.

She did not put the phone down for a moment after that. Beatrice was not a person who agreed at 23:31 on a Sunday unless she had spent her own evening looking at the same page.


The cat got up and moved to the window because the radiator was warmer than the laptop. The kitchen made the small night noises that an old building made in May — the heating clicking off, the pipes contracting, the neighbour's washing machine ending its cycle two floors below. Anjali opened a fresh document and began to write the email she would send Kasper at 06:30 so that he would read it in the cab and not in the meeting.

The email was three paragraphs. The first paragraph said that Agent 365 should be the bank's control plane for Entra-native agents starting Monday. The second paragraph said that the Luxembourg and Singapore subsidiaries would remain out of scope until the federation reached general availability and that the compliance brief would document those subsidiaries as managed under separate plane, August 2 readiness gap explicitly logged. The third paragraph said that the bank should pause every new agent project at the seventh floor and below for fourteen days while the inventory team ran the Entra Agent ID rollout for the agents already in production, and that any agent that could not be assigned an Entra Agent ID by July 1 should be sunsetted by July 15 or migrated to a vendor that could.

She did not soften any of it. Kasper preferred the version that did not make him guess what she meant.

She read the email twice. The first time for accuracy. The second time as if she were the regulator reading it during discovery in 2027. It read the same both times, which was the only test she had ever fully trusted.

She added one final line. We are not going to be perfect by August 2. We are going to be defensible. The difference is the documentation, and the documentation is what we are starting tomorrow.

She scheduled the send for 06:30. She closed the laptop. She told the cat that they were going to bed and the cat ignored her.


Standing at the window with the last of the bad coffee, she thought about the diagram on the Learn page. The three rings. Observe. Govern. Secure. She thought about how many vendors had drawn the same diagram in nineteen years. Active Directory had drawn it. Office 365 had drawn it. Intune had drawn it. The diagrams had been the same and the rooms had got bigger and the rooms outside the diagram had got smaller, year over year, until the room outside was the part you ran into trouble at and the room inside was the part the auditor accepted.

The window into the room would be a Microsoft window. That was a choice she did not love, exactly, but it was the choice that produced the slide she could put in front of the board on Tuesday morning. The other choices produced slides she did not have ninety-one days to defend.

She thought about Beatrice in Singapore, awake at the same hour for the same reasons. She thought about the eighty-six agents already inside the tenant, none of which had asked anyone's permission to exist, and the kindergarten pickup tomorrow, and the laundry basket she had successfully avoided, and the way the second of August was a Saturday this year, which meant the auditor would call on the Monday after.

The street outside was still empty. The kitchen light made a soft yellow square on the wall opposite. She rinsed the cup and put it on the rack upside down and the building made another small night noise and she went, finally, to bed.

In the morning the train would already be moving. She had decided to board it.