Share via

In Azure portal, the just-in-time policy "request access" has gone from VM Connect blade

Graham B 0 Reputation points
2025-08-12T11:58:41.87+00:00

The just-in-time policy "request access" has gone from VM Connect blade. Previously we could hit connect, request access (for "just-in-time" access), then "go to Bastion", and enter port, user credentials to RDP onto VM. Now we simply cannot connect to our VMs! This is in Azure East-US region.

We have been using this method (of RDP via Bastion) since March 2024 without issue, but the "request access" function disappeared on/around 28th July 2025.

Can anyone help with an explanation or workaround?

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Divyesh Govaerdhanan 8,345 Reputation points
    2025-08-12T20:07:56.55+00:00

    Hello,

    Welcome to Microsoft Q&A,

    Microsoft has made a UI change that affects how Just-In-Time (JIT) VM access is requested in the portal.

    Before (pre-July 28, 2025): On a VM’s Connect blade, if JIT was enabled via Defender for Cloud, you’d see a Request access option inline before choosing Bastion/RDP.

    After late July 2025, that button has been removed from the Connect blade in many regions, including East US. Instead, JIT access must be initiated from Microsoft Defender for Cloud → Just-in-time VM access or from the VM’s Configuration → JIT tab.

    The goal is to make JIT initiation consistent across VM types and connection methods, but it’s removed the “inline” experience in the VM Connect pane.

    Please upvote and accept the answer if it helps!!

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.