There is a Windows 11 desktop. Across it sits a perfectly organised grid of translucent QR codes: top, middle, bottom, left, right, and several places where your eyes were probably hoping to find the actual work.
This is not a parody of enterprise security. It is Microsoft’s own example of watermarking in Azure Virtual Desktop.
The screenshot above comes from Microsoft’s Azure Virtual Desktop watermarking documentation. Microsoft explains that each QR code can contain a connection ID or device ID. If a marked desktop appears somewhere it should not, an administrator can scan the code and search for the associated session through Azure Virtual Desktop Insights or Log Analytics.
In other words, the idea is sensible: make a captured desktop traceable to the session that displayed it.
The execution has all the subtlety of a fire drill.
What Azure’s approach gets right
Before we laugh too hard at the QR-code wallpaper, it is worth being fair about the problem Microsoft is solving.
Azure Virtual Desktop covers an entire remote Windows environment rather than one application or document. The watermark must be added consistently by the remote-desktop stack, work across whatever appears on screen, and provide an identifier that an enterprise administrator can recover using tools they already have.
The visible grid delivers a few genuine benefits:
- It is an immediate deterrent. Nobody can plausibly claim they did not realise the session was marked.
- A complete, readable QR code offers a direct route back to a connection or device record.
- It can still appear in a photograph taken with an external camera, where blocking the operating system’s screenshot tools is not enough.
- Administrators can deploy it through Intune or Group Policy and investigate it through Azure’s existing monitoring stack.
Microsoft also positions watermarking alongside its separate screen-capture protection. That matters. Screen-capture protection can block supported local capture paths, while the visible watermark is intended to discourage or trace other methods, including photographing the display.
As one layer in a wider defence, it makes sense.
Where the QR-code grid becomes awkward
The obvious problem is that the security control is now competing with the content it is supposed to protect.
Nothing says “please concentrate on these financial figures” quite like a matrix barcode floating over every available patch of the spreadsheet.
Microsoft lets administrators adjust QR scale, opacity and spacing. That flexibility exists because the implementation has an unavoidable trade-off: make the codes quieter and they become harder to recover; make them clearer and the desktop starts to resemble a particularly security-conscious restaurant menu.
There is also a more fundamental weakness in any visible, tiled marker: the marker tells you exactly where it is.
The example image contains large spaces between complete QR codes. A full-screen photograph is likely to include several markers, which is the design’s strongest case. A tightly cropped screenshot, however, may contain the sensitive content without preserving one complete, readable code. Increasing the density reduces those gaps, but adds even more visual interference.
It is less “hidden forensic layer” and more “the QR department has redecorated”.
That does not make Azure’s feature useless. It means its recovery depends heavily on a visible object surviving inside the leaked crop. Once the person handling the image can see the marker, they can also try to exclude, cover or damage it.
Visible deterrence and covert attribution are different jobs
A visible watermark primarily changes behaviour. It tells the viewer that the material is controlled and may be traceable. That can be valuable on its own.
A covert attribution signal has a different goal: remain unobtrusive during normal use and become useful only after content surfaces somewhere it should not.
The strongest protection can use both ideas, but they should not be confused:
- Visible marks deter. They make the warning unmistakable.
- Covert marks attribute. They avoid advertising precisely what must be removed.
- Capture controls restrict. They block supported technical routes but cannot stop every camera, export or human action.
The mistake is treating one loud grid as though it performs all three jobs equally well.
Put the signal through the content
ExactMark takes a different approach for private Web Apps, images and PDFs. Instead of placing a handful of obvious identifiers on top of the content, it distributes a covert, session- or recipient-linked signal through the rendered material itself.
That distinction matters when evidence is incomplete. A screenshot can be cropped, resized or recompressed and may still retain enough of the distributed signal for a confidence-scored attribution. There is no single visible square that must remain untouched and no convenient sign showing where the forensic layer begins and ends.
For signed-in Web Apps, ExactMark links the rendered page to the viewer session without asking the viewer to scan anything or covering their interface in codes. For shared images and PDFs, ExactMark Imprint creates a separately marked copy for each recipient. If one of those copies surfaces later, Evidence Lab can analyse it against the retained attribution records.
This does not make attribution magical or guaranteed. Severe transformation can destroy signal, and a match should always be considered alongside access records, timing and organisational context. The difference is that the protection is designed around the messy evidence organisations actually receive, rather than assuming a pristine QR code will politely arrive with the leak.
The useful lesson behind the funny screenshot
Microsoft’s implementation is memorable because it makes the trade-off impossible to ignore. It proves that enterprises want session-level accountability even after information leaves the controlled environment. It also shows what happens when the attribution mechanism becomes louder than the information itself.
The goal should not be to make people work underneath a ceiling of QR codes.
The goal should be to give every sensitive view or recipient copy its own recoverable identity—quietly, redundantly and without turning the desktop into security wallpaper.
Azure has the QR department.
We prefer the pixels.