# Include the Virtual WAN global P2S profile in remote-user recovery testing

> Verify the endpoint choices available to the actual remote client.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-185-include-the-virtual-wan-global-p2s-profile-in-remote-user-recovery-testing/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:31:55+00:00
- Modified: 2026-09-17T16:46:29+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Verify the endpoint choices available to the actual remote client.

## Potentially affected

Use this review for a remote-access recovery design with multiple P2S hubs. Identify the profile actually installed on the client, listed endpoints, intended applications and the user's access path. Keep the design's expected behavior separate from an observed recovery result.

## DSE recommendation

DSE recommends including profile distribution and client configuration in the recovery plan.

## Article

## Source facts

Microsoft’s Virtual WAN recovery guidance describes a global profile listing point-to-site endpoints when multiple hubs have P2S gateways. Devices using that profile can connect through an available hub, with Virtual WAN’s traffic manager selecting the best hub for remote-user connectivity. The guidance separately identifies redundancy of the user’s access network as a recovery consideration. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-wan/disaster-recovery-design).

## Applicability

Use this review for a remote-access recovery design with multiple P2S hubs. Identify the profile actually installed on the client, listed endpoints, intended applications and the user’s access path. Keep the design’s expected behavior separate from an observed recovery result.

## DSE recommendation

DSE recommends including profile distribution and client configuration in the recovery plan. Ask the remote-access owner to define which hubs and applications a representative user must reach during an outage. Identify dependencies that remain outside the Azure hubs, including the user’s connection. Preserve the approved profile and instructions for returning to normal operation.

## Verification

In an authorized rehearsal, confirm the client has the intended global profile and can reach the approved application through the available recovery endpoint. Record the selected hub, connection sequence and actual interruption. Test restoration separately. Do not declare remote access resilient solely because two hubs exist; retain evidence from the client and application path that users will rely on.

## Official references

[Microsoft Learn: Disaster recovery design for Azure Virtual WAN](https://learn.microsoft.com/en-us/azure/virtual-wan/disaster-recovery-design).

## Primary reference

- Name: Disaster recovery design for Azure Virtual WAN | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-wan/disaster-recovery-design
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Include the Virtual WAN global P2S profile in remote-user recovery testing,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-185-include-the-virtual-wan-global-p2s-profile-in-remote-user-recovery-testing/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.