Azure Bastion Developer — NSG source restrictions, RDP connectivity and session termination

Rex 0 Reputation points
2026-11-05T05:17:37.6733333+00:00

Hello Microsoft Azure Team,

We are evaluating Azure Bastion Developer for temporary administrative access to a disposable Windows Server 2022 Datacenter Gen2 virtual machine in Australia East, under an Azure Free Trial subscription.

Our intended configuration is:

Private VM IP address only; no public VM IP.

Dedicated virtual network, subnet and network security group (NSG).

Browser-based RDP through Bastion Developer.

Explicit deny-all inbound and outbound NSG rules, with only narrowly scoped, temporary preparation-access allowances.

No dedicated paid Bastion deployment.

The purpose is to establish temporary guest access for environment preparation and then withdraw that access before conducting separately controlled security verification.

We would appreciate clarification on the following six points.

1. Bastion Developer NSG source restrictions

What exact source IP address, CIDR range or service tag should be permitted for Bastion Developer to connect to the private VM over TCP 3389?

Can the source be restricted specifically to Bastion Developer, or does the service require a broader VirtualNetwork allowance?

2. Connectivity prerequisites

What inbound and outbound NSG rules are required specifically for Bastion Developer?

Are there Azure platform communications or guest-agent dependencies that must remain accessible?

We want to avoid applying network rules intended for dedicated paid Bastion deployments to the Developer shared-service tier.

3. Session termination and access withdrawal

Does Bastion Developer support administrator-initiated termination of active RDP sessions?

What supported procedure would allow us to terminate existing sessions and prevent reconnection after removing temporary preparation access?

4. Clipboard and file-transfer restrictions

Can clipboard copying and pasting be disabled for Bastion Developer using supported Azure, browser or Windows guest controls?

Does the Developer tier support any other file-transfer or redirection capabilities?

5. Free Trial subscription eligibility

Is Bastion Developer supported under Azure Free Trial subscriptions in Australia East, without upgrading the subscription or activating a paid Bastion tier?

6. Pricing and incidental charges

Is Bastion Developer itself free of hourly usage charges?

Are there additional connection, data-transfer or other charges beyond the underlying VM, storage and networking resources?

We would particularly appreciate references to official Microsoft documentation or an example of a supported least-privilege configuration.

Thank you for your assistance.

Azure Bastion
Azure Bastion

An Azure service that provides private and fully managed Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines.

0 comments No comments

1 answer

Sort by: Newest
  1. Andriy Bilous 12,676 Reputation points MVP
    2026-11-06T05:39:42.06+00:00

    Hello Rex

    Azure Bastion Developer supports browser-based RDP to private Windows VMs in Australia East, including development/testing scenarios using an Azure Free Trial subscription.

    Here are the important distinctions from the paid Bastion SKUs.

    1. NSG source restrictions

    Bastion Developer uses shared infrastructure and does not deploy an AzureBastionSubnet.

    I recommend VirtualNetwork as the source for inbound TCP 3389 and Microsoft documents 168.63.129.16 primarily for Azure platform services.

    For an initial connectivity test, use:

    NSG
    Direction Source Destination Port
    Inbound VirtualNetwork VM private IP TCP 3389
    Inbound Any Any Deny all other
    Outbound Any Any Deny all, except required services

    Place the RDP allow rule at a higher priority than the explicit deny rule. VirtualNetwork is broader than Bastion-only access, so this does not provide a strictly Bastion-exclusive security boundary.

    2. Connectivity prerequisites

    • No public IP is required on the VM.
    • No dedicated Bastion subnet or dedicated Bastion NSG rules are required.
    • Allow TCP 3389 in the VM's NSG and Windows Defender Firewall.
    • No Bastion-specific guest agent is needed for browser-based RDP.

    NSGs are stateful, so separate outbound rules for established RDP responses are unnecessary. However, preserve required Azure VM Agent, DNS, and other platform connectivity.

    3. Session termination and access withdrawal

    For a reliable guest-side procedure:

    Identify active Windows sessions with quser.

    Terminate the appropriate session using logoff <sessionID>.

    Remove the temporary TCP 3389 allow rule or disable RDP.

    Revoke temporary guest credentials/access where appropriate.

    Changing an NSG rule does not necessarily terminate existing connections because Azure NSGs maintain connection state.

    4. Clipboard and file transfers

    Developer supports browser-based text copy/paste but does not support the Bastion configuration option to disable clipboard access. That feature requires Standard SKU or higher.

    For Windows Server 2022, enable the guest Group Policy:

    Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Device and Resource Redirection → Do not allow Clipboard redirection

    Developer does not support native-client file upload/download. Browser-based clipboard transfer supports text, not files.

    5. Free Trial eligibility

    Australia East is explicitly listed as a supported Developer region. Microsoft's deployment quickstart includes free Azure accounts as eligible subscription prerequisites. Availability remains subject to subscription restrictions.

    6. Pricing

    According to Microsoft's Bastion SKU comparison:

    • Developer SKU: Free hourly usage
    • Bastion outbound data transfer: Free
    • VM, managed disks, and other Azure resources: Standard applicable charges

    Developer is suitable for temporary development access. However, if strict Bastion-only network isolation, guaranteed administrative session revocation, or centrally enforced clipboard restrictions are mandatory, a dedicated Bastion SKU and additional guest-level controls would be more appropriate.

    Documentation:

    Was this answer helpful?

    0 comments No comments

Your answer

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