Scenario Description:

Some businesses need to configure VNET to support security and private connectivity. This topic is closely tied to both regional and sub-regional behavior. In one of my cases, the customer’s clients are primarily based in Sydney (Australia East - EAU), so this region became the main focus when setting up the VNET. However, some environments were created in a different sub-region, Melbourne (SEAU), which caused conflicts when performing VNET injection.

Walkthrough:

After reviewing the relevant documentation, the business team understood that it is recommended to cover all sub-regions within the broader OCE region. However, since multiple sub-regions are involved, it would be very helpful if the datacenter location could be clearly displayed for reference.

Clarification:

During the support case, the customer raised the following points:

• Datacenter move operations are available as a service from the engineering side. Therefore, it raises the question of why the datacenter or Azure region cannot be displayed for customer visibility.
• The region selection logic within OCE has been confirmed by the Product Group to be system-driven. While this is understood and accepted, having the datacenter location displayed after environment creation would provide useful reference information for the business team.
• Currently, instead of showing the Azure Region (which is the key information), cloud flow outputs display an Azure Region Hint. This has caused confusion, as Azure Region and Azure Region Hint are different. In some cases, the purpose of Azure Region Hint is not clearly understood, which leads to further questions on why the Azure Region itself is not shown.

Customer Expectation:

For VNET configuration, cloud flows, and region-related scenarios, the customer expects the datacenter location (Azure Region) to be clearly visible in the Power Platform Admin Center. This would support reference, validation, and development activities. At present, the absence of this information, combined with the presence of Azure Region Hint, creates confusion.

Observed Behavior:

Each time the customer needs to confirm the datacenter location, they must raise a support request to obtain this information.

Request:

Kindly consider displaying the datacenter location (Azure Region) directly in the Power Platform Admin Center.

Alternatively, even if it is not exposed in PPAC, cloud flows could serve as a workaround. However, it would be more useful to display the Azure Region rather than Azure Region Hint, as the latter does not meet the current requirement.

The customer understands that more detailed information may be available from the engineering side. Therefore, they would also like to know if there is any way to check the datacenter location (Azure Region) of environments without relying on support engineers and support tickets, especially since their organization manages more than 20 environments.