The Azure Updates entry is titled "Public Preview: Azure Bastion RDP and SSH vision." When we retrieved it, the update page showed "0 Updates found" instead of the listing itself, so it adds no detail of its own. The substance comes from an Azure Networking Blog post by Ashish Jain, Microsoft's Partner Group Product Manager for Network Security, dated November 17, 2026. The same page also carries a separate "Updated Nov 15, 2026" line.
What Microsoft actually announced
Microsoft's Azure Networking Blog describes three related capabilities:
- RDP vision runs AI-assisted analysis over recorded Remote Desktop sessions. It produces session summaries and flags actions Microsoft calls "noteworthy and potentially risky." Microsoft says this helps most with desktop-based administration, where you can only understand an action by following a sequence of clicks and windows.
- SSH vision applies the same kind of review to recorded SSH terminal sessions. It produces summaries and activity insights so reviewers can decide which sessions need a closer look.
- SSH command logs keep a detailed record of the commands typed during SSH sessions. They sit alongside the visual recording and the AI summaries, so investigators can see exactly what was entered.
Microsoft frames it as a split of duties. The summary orients the reviewer, the flagged insights direct attention, and the command detail supports deeper digging. The recording remains the ground truth.
Section summary: The AI features cover both RDP and SSH. The plain, non-AI command log covers SSH only.
The workflow Microsoft is pitching
Microsoft's example is a security team looking into an unexpected configuration change. With recordings alone, the team may have to watch several long sessions just to work out which ones are relevant, even though most of that footage is routine administration.
With the preview features, Microsoft suggests this order:
- Start with the RDP vision or SSH vision summaries for the sessions in question.
- Use the flagged activity to decide what to follow up first.
- For SSH sessions, check the command logs for exact detail.
- Go back to the original recording to confirm findings and see the full sequence of events.
Microsoft's blog states that "AI-assisted insights support human judgment." Security teams still weigh the evidence, apply business context and decide what to do. That point matters. The summaries are triage aids, not verdicts. A flagged action is not proof of wrongdoing, and an unflagged session is not proof that nothing happened.
The prerequisite: Bastion Premium session recording
These capabilities build on Azure Bastion Premium session recording. According to Microsoft, recordings stay in the customer's own designated Azure Storage account. The features analyze recordings and do not change how connections are made. To understand what you need, it helps to know how the recording feature works today.
Microsoft Learn's session-recording documentation (last updated April 2026) lists these requirements:
- The Bastion host must be on the Premium SKU. You can upgrade from a lower tier in the portal under the Bastion resource's Configuration page, then enable Session Recording. Microsoft says the update takes about 10 minutes.
- Target VMs must be in the Bastion virtual network or in a directly peered network.
- Recordings go to a blob container. Microsoft recommends a container used only for recordings, with a CORS policy on the Blob service that allows origins from your Bastion's DNS name (it starts with
bst-and is case-sensitive) and the GET method. - Bastion can authenticate to storage with a managed identity, which Microsoft recommends (in preview) and which needs the Storage Blob Data Contributor role. The alternative is a SAS URL with Read, Create, Write and List permissions.
- Anyone who views or lists recordings needs the Storage Blob Data Reader role.
- When a session closes or disconnects, the recording appears under Settings > Session recordings on the Bastion host, where it plays in a built-in web player.
The same documentation also lists limitations that anyone piloting the vision features should know:
| Constraint | Why it matters |
|---|---|
| Records all sessions through a recording-enabled host | You can't record only some sessions, so plan storage and privacy accordingly |
| One container/storage account at a time | Recordings from one host all go to a single place |
| No immutable storage policies or blob versioning | Can conflict with tamper-proof retention designs |
| Changing containers mid-session may disrupt sessions | Make storage changes outside working hours |
| Not available via native client | Only browser-based sessions are recorded |
| Entra ID portal RDP can't be used concurrently with graphical recording | A real tradeoff, covered below |
The Entra ID catch
The last row in that table is the most important for Windows administrators. Microsoft's Azure Network Security Blog announced last year that Bastion previously supported Entra ID authentication (formerly AAD) for RDP and SSH connections via native client and for SSH connections via the portal, and then introduced public preview for Entra ID support for RDP connections in the portal. The selling point was that by leveraging Microsoft Entra ID, authentication becomes identity-based, eliminating the need for local credentials and reducing complexity.
But the current session-recording documentation says Entra ID support for portal RDP can't run at the same time as graphical recording. RDP vision depends on recordings. So, unless Microsoft changes this, teams moving Windows admins to Entra-based portal sign-in may find that those sessions are the ones RDP vision can't analyze. That leaves a choice between identity-based sign-in and AI-reviewed recordings. Microsoft's announcement doesn't mention the conflict, so test it in a pilot before committing.
Two other gaps follow from the same documentation. Native client connections aren't recorded, and the SKU that offers native client support is the same one where recording works only in the browser. Many administrators prefer mstsc or their own SSH client. Since only browser-based sessions are recorded, any session opened through a native client produces nothing for the vision features to analyze.
What Microsoft hasn't said yet
The blog announces the preview but leaves many basics unanswered:
- No enablement steps specific to RDP vision, SSH vision or command logs
- No pricing, and no statement on whether the preview has extra charges beyond Premium
- No list of supported regions or general-availability date
- No details on how and where recordings are processed by the AI, what model is used, or how long summaries are kept
- No accuracy figures, benchmarks or measured time savings
- No word on whether recordings made before you enable the features can be analyzed
Microsoft's Azure Updates legend defines "In preview" as available to all Azure customers for non-production use and testing. The update page itself didn't display the item, so we can't confirm any specific eligibility terms. Microsoft's claims about efficiency are aims, not measured results.
Analysis: useful, but don't skip due diligence
Microsoft has identified a real problem. Session recording became a box many teams ticked for compliance, but a recording nobody watches gives you very little security in practice. As Microsoft's blog notes, even a small or midsize company can pile up more privileged-session footage than it can realistically review. Using AI to triage that backlog is one of the more sensible uses of the technology this year.
There are fair counterpoints:
- Data governance. Privileged-session recordings can capture credentials on screen, customer data and internal systems. Before you point an AI at them, ask your Microsoft account team how the analysis handles that data.
- Over-trusting the summary. If reviewers start reading only the summaries, a skilled insider who knows what the AI flags has an obvious path to avoid it. The recording and command logs should stay part of the process.
- Coverage blind spots. Native client sessions and Entra-authenticated portal RDP aren't recorded, so a session that bypasses recording also bypasses the vision features.
Our advice: test the preview on non-production Bastion hosts where Premium recording already runs. Compare the summaries against recordings you have reviewed by hand, and note which session types never get recorded in the first place. If the summaries reliably point you to the right part of a recording, this could become one of the more practical AI additions in Azure's security tools.
References
- (In preview) Public Preview: Azure Bastion RDP and SSH vision Azure Updates · 2026-11-17T20:25:18Z
- Record Bastion sessions - Azure Bastion | Microsoft Learn learn.microsoft.com
- From recordings to insights: Azure Bastion brings AI to privileged session review | Microsoft Community Hub techcommunity.microsoft.com